Having only programming background, it is impossible to develop software in some areas.

I’d say except for software development tooling itself you’ll never develop anything useful if you don’t have or acquire at least a basic understanding and knowledge in the domain of your software, whether it is music scoring, aerospace engineering or photo manipulation.

That is why developers sometimes save on code quality.

I thin the examples in the article are mostly oversights or the result of inexperience and inadequate code quality assurance, not because of the domain knowledge needed. Those errors are also present in life-critical software, but will be discovered before coming close to anything like a release because of rigid automatic quality metrics like the static code analysis done in this article.

OK, makes sense. I don’t envy you keeping track of all those edge cases…

Thanks for working on Lemmy and taking time to answer questions!

Edit: to answer your specific quesion, no there is no chaining, it is an all-connects-to-all type of network (with the allow-list as the limiting factor). Other Fediverse (ActivityPub) software operates similarly, except that you can subscribe to any other instance (Unless on the block-list) and then that instance gets added to the instance wide allow-list of your instance automatically.

Thanks for calrifying this! now I understand :)

What I haven’t understood and found an answer yet: Are Lemmy instance federation transitive, i.e. A follows C through B? Or are federations only exactly affecting the 2 involved parties?