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.

Wow, that’s quite useful.

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.

In my case, xdg-desktop-portal-gnome is required by xdg-desktop-portal, which in turn is required by flatpak. I wonder what effect will removing have on apps?

I don’t if, but soooo much crashes surely should trigger some response in people, especially when they go out of their way to work on some “real time” codebase, tasks requiring even a pinch of synchronization.

If you have strategically real time collaboration, I would advise against pushing to GitHub and find a way to self-host or use another instance.

Sometimes, I can’t help but to put GitHub to the side when we speak open source. Not saying that it’s a wrong place to ask, it’s just that with GitHub, as with many centralized platforms with many users to catch up to, outages are not all that nuanced. We’ve been through much of them: GitHub, GitLab, almost the same difference.

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).

Thom Zane has pointed out that Anytype’s license has a non-commercial clause. Well, I think it’s only natural for an EVERYTHING app. Just the thought of it being sublicensed and changed in many ways to being sold as an “exclusive” app, it doesn’t leave my mind. There’s just a problem with differentiating if something is commercial or not sometimes.

Obviously, it doesn’t fit the “open source” criteria, but it doesn’t need to be - if you only want to change source code in few places and not offer it in exchange for something.