@dominik False. Readonly properties can be set outside the constructor. In 8.3 they can only be set within the class (private scope). In 8.4, they’re protected set by default, but you can change it, even make them public write.

The “only in the constructor” thing was invented by PHPstan and Psalm. It’s not part of the language. It’s a stupid add-on that 2 dudes came up with for their tools and refuse to change.

@ramsey @jetbrains That’s what I do! But there’s no CLion equivalent plugins that I can find.

@zdl @thenexusofprivacy @fediverse @fediversenews

1. Protecting the users of your service and fostering the culture you want is a responsibility. If you’re not up for that responsibility, you should not be a moderator.

cf: https://peakd.com/community/@crell/why-you-can-t-just-ignore-them

2. Do we want ActivityPub to go the way of XMPP? Neither ignoring Threads nor outright blocking will help to avoid that fate. Getting a different outcome takes work.

@thenexusofprivacy @fediverse @fediversenews Simply blocking Threads won’t actually accomplish anything, except leave people stuck on Threads. If we want to actually help people, we need to take active actions beyond boycotts. We need to bleed users off of Threads, and we cannot do that if we block them outright.

https://peakd.com/mastodon/@crell/tangled-threads