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

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.

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.

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.

Wow, toxic.

Someone could make WikiHow out of this.

This is so OOC. Make more.

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

Yes, Granny.

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.

I dunno: laws, other consequences?

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.