I work at the biggest software company in the world.
Sure there is projects with security flaws, but at the company I work, there is zero tolerance to big security flaws in the code, we have many automated checks, as-well as manual checks.

In all seriousness, no one is talking about this, but this is the one disadvantage of open source software being developed by volunteers, we don't know exactly how the admin accounts were hacked but the XSS stuff is really basic stuff, none of those fields were sanatised at all, and it makes me concerned what else has been missed, obviously the advantage of open source is in time this stuff can get fixed, but this is what happens when loads of people who aren't experts contribute to a site.

In comparison to sites where there is a fully hired developer team the quality of the code is significantly better. I really hope the passwords were hashed on these instances and the hackers didn't get plain text passwords or anything really bad like this.

One thing and credit to Ernest, as I've contributed there he does very thorough code reviews and his quality of code is very good, its why im confident kbin won't be hacked.

• Excessive grinding or padding in a game just for the sake of it or for microtransaction reasons.
• Microtransaction and pay-to-win models in full price $70 games...
• Overuse of Quick time events Press E to dodge etc etc
• Escort missions when developers want to pad their game out
• Terrible stealth mechanics when an enemey spots me when im standing still in a bush from the other side of the map

I think even better, you should be able to sign into any instance via some type of centralised federated login, though I guess the argument is you can't do that in multiple email clients as email is the most popular federated example.

I like the concept
But it feels very much like its been designed by nerdy developers and has had little to no-input on user friendly design.

The federated idea can work but it needs to be more seemless than this.

1. Communities with the same name should be merged when viewing it from any instance, so you can see all the posts from these communities, they can be moderated seperatley and for advanced users you should be able to select which communities make up the merged community.
2. By default you should see all of the merged communities in a central place and be able to subscribe to them easily, at the moment its handled different per instance but you have to seek out these communities to subscribe or follow them.
3. I strongly believe there should be a centralised log-in system, so you can log into any instance with an account from another instance, this means if your instance goes down your account is centralised and is safe.