NaN

Do xsnow and xpenguins next!

My only real problem is I still use windows more than full screen, barely ever use workspaces, and those are two workflows they really want someone to use.

I really like Fedora, but the release cycle is too fast for my tastes. Also I find Gnome distracting these days.

That’s why after 20+ years I use Mint or LMDE. I don’t have the time or interest to tinker the way I used to unless I’m getting paid for it. Mint was the thing that got me to leave Fedora.

That’s what all of the analysis is pointing to.

Since the analysis is not complete, the other thing people need to remember is that nobody knows if ssh was the only target or just the only one that was noticed. A ton of stuff uses lzma, including web browsers and password safes.

There are probably BSD derivatives that act that way.

Because many people are also fans of free software. https://www.gnu.org/philosophy/selling.html

The blog says specifically that FireDragon is not an issue. I am also curious about these forks.

Ablaze was high school students making random hobby projects. This one got popular and it has obviously had a negative effect on the dev (who is likely in university by now). Sounds like they are also feeling a sense of responsibility for things they aren’t responsible for.

It also sounds like they don’t really understand open source.

Their Twitter makes it seem like they aren’t having much fun.

It may be. The person saying that has contributed artwork but is not the maintainer. It is a bad look though. It sounds like they want to build the next release in secret so the fork can’t release features first.

It’s an open source browser based on Firefox with additional features and configuration tweaks.

Except they recently made part of it proprietary and hid the source code for that, so most other people cannot actually build the same one.

They claim they will make that part open source too, eventually, and it is due to behavior of another browser: https://github.com/Floorp-Projects/Floorp-core/issues/62

That’s why I was tongue-in-cheek mocking mastodon users who accidentally post to Lemmy. OP wasn’t trying to start conversation, they were posting a random thought into the ether.

Every time a mastodon user uses @ instead of # and tags a Lemmy community, an angel loses its wings.

It hasn’t had an impact since he is still very active. Also presumably he isn’t the only one with the update keys this time around.

I went looking for reviews and stumbled into that video too, very disappointing. Note that he is still listed as a director in the Foundation and active in the repo, so it sounds more like he has stepped away from a public facing role, which seems like a good change either way.

Although I also saw what he did when he left CopperheadOS, deleting the update keys. That kind of made me question if I should skip this one.

Apps can tell if they are not running on an official, Google blessed OS. Most don’t care, but for something like that they may have locked it down (contactless payment apps like Google Pay also won’t work). Generic NFC can still work for other uses.

Best to look around the GrapheneOS community and see if there are workarounds.

Very helpful! I’ve been on the fence for a while, the recent addition of Android Auto makes it somewhat easier though.

The special use list for use by individuals and business is actually very small and hasn’t been updated in a long time, which is a big part of the problem with people inventing their own.

Reserved TLDs are documented. The issue is they prioritized all the crazy ones before they added what people at home and businesses were actually using. ICANN won’t sell .lan because it is used too much. They haven’t tried so there is no official decision, but they won’t - they did try .corp and .home and abandoned it.

.local is reserved in RFC 6762, but for multicast DNS.

It’s such a shitty situation. ICANN is not going to sell .home or .corp as they found a crapton of traffic when they checked for it, but IETF never finished an RFC for them - however people easily stumble into the draft RFC that lists what they were thinking of, and assume stuff like .lan is good to go too. They’re safe by ICANN policy, but unsanctioned.

.home.arpa is safe, per RFC, but user unfriendly to normal people. There are a few others but none a corporation would realistically use. I’ve used . internal for lab testing stuff for ages, so this is extra good news for me I guess.

Really I wish they’d have just reserved the most common ones rather than getting caught in some bureaucratic black hole.

Simplenote, Notesnook, Obsidian.

Obsidian sync isn’t free, and it’s easy to violate their license if you mix work and personal notes.

I think Joplin tends to be better than most. If Obsidian was licensed and charged differently I might change my mind.