Someone could make WikiHow out of this.

Previous owner of Godot Community Forums got burned out and didn't curate the first month of co-owning this platform - here we have a clear-cut case study against prematurely transferring ownership. One could look at it and think that Cybereality took over the forums only to sabotage them in a few weeks. But it might be a rather spontaneous product of zir heated discussion and disagreement with Juan, so I'd write this off to a "happy" coincidence. Cybereality already explained it's about confusion around allegedly broken promises with W4 and Godot Foundation.

Looking at the bigger picture, it's a case study of problems with centralization of community in confines of something close to walled garden, around the project that is supposed to be as open as a vocabulary. More the reason to raise awareness of Lemmy communities, Matrix Public Archive, etc.

With the way it's going now, and considering that Friday didn't end up to be the best day for our community to start the event, the extension time is really desired.

I look at the latest release date. At leisure time, I would also go and check repository and issue tracker to see whether something serious is being ignored. If it's crucial for business, I would spare time investigating the source code itself.

I would not necessarily say that many apps uploaded to F-Droid and other repositories are unsafe, because I don't have all that energy to audit anything I use. What helps me to stay on the safe side is reading into things - enclosed descriptions and names may look like a small factor to some, once they tread the sources, but it saves me both the time and trouble. Sloppily written stuff usually implies a sloppy code, a lax attention to details on the developer's side.

Wherever the app's code is on. I usually go around finding the link in the store page or through the search engine. Most of the time, they end up on GitHub and GitLab, sometimes on Codeberg or other instance.

Paranoid section ahead: Don't blindly trust the issues list, closed or open, because there are still ways to permanently delete those, hence giving bad actor a way to hide evidence of the on-going security problem.

Is it meant to show that the bird is mercilessly murdered?

Meanwhile I read the feed and get stressed by people (un)consciously installing Threads cr-app on their primary devices w/ stock Android and iOS, despite them having a normal time with literally any other interface to Fediverse.

Yes, Granny.

It is rare that everything app like this has a source code available to public. I'm immediately hooked, as someone who can't wrap his head around making custom views in Obsidian and its open source alternatives. (For the love of Pete, frontmatters are just too demanding on syntax department!) Fork, stat! 😃

License doesn't seem to step on your toes as long as you don't distribute Anytype in exchange for something (w/ or w/o modifications).

Wow, toxic.

Sending a tinsy-winsy appreciation to how you handle this dialog. Smooth. 🎩

This is so OOC. Make more.

Sure, just find a way to self-host Conduit or Construct for Matrix and don't federate with outliers - it would work like a charm for internal communication (disclaimer: these light-weight servers are in beta stage, unlike the resource-hungry Synapse). Wait, NextCloud and Revolt have implemented chats, which are encrypted and open source already? As such, I don't observe any special benefits of Matrix for your use case (unless you're gonna do bots and stuff). 🤔 You have a lot of choices! 😉

I dunno: laws, other consequences?

I agree about the "evolution" part of the designs. People really need some sweet time, at least 10 days (starting Friday, finishing at the next Sunday).

Because you went south 🥁

Newcomers to Lemmy, I ask you- to not scale images just to upload them in bad quality to make someone's eyes sore.

Take an advantage of the confusion - take the largest.

I like it with sauce, pretty please.

I definitely remember seeing someone on YouTube sewing after using some built-in Inkscape extension to optimize route and color switches. It was pretty surprising to find such tutorials.