Someone could make WikiHow out of this.

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.

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

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

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

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

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.

Take an advantage of the confusion - take the largest.

How do you people make the screenshots of popups in Firefox? Every time I press Print Screen they just keep fading away.

Dio + Giorno 😅

Because you went south 🥁

Decades of browser engineering have failed us... This day came.

Tfw you catch 'em doing bad with CSS.

I don't think OP needed to give a damn while posting this, plus it was pointed out already.

I observed the same segmentized silos problem a little while ago. Initial reach is SOOOO much harder when federation doesn't work.

Reach is there only when some popular tech vblogger appears, like The Linux Experiment on TILvids - and that's it. Most people are there for that channel and that channel only (Nick's done a good job at promoting it, as we see), which must mean the impression other parts leave on a viewer is considerably worse.

Wait, there is such a button? 😳 It must be so useless to me that my brain is rePRESSing it, huh. 🤭

The matter of perspective, amirite? 🥁

Wait, NPCs have a power to go through the props. It's something I learned from Half-Life 2.

Wow, that's quite useful.

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.

Wait, so, it's supposed to be time-limited?

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.

Yeah, well, it will be unsolved again and again, because that's the nature of servers - they experience downtime. I'm just looking ahead of myself and how badly this tag will age for some, haha.

It's never "[Solved]", LOL.

Mastodon, an alternative social network to Twitter

Not reading what's next. Probably, some bull.

It's not like the person taking this photo left their bike for a while.

Either are awful parking spots for bikes, but serves them right.

TILvids is like your average overprotective uncle...