Both are great projects really, and big projects at that - big stacks, lots of moving parts.

Whereas GNOME tries to be more uniform, Plasma tries to be more bespoke.

I don’t care which one you use, really. I just love GNOME design principles and it’s desktop paradigm.

Is GNOME a perfect project? No. But when these troglodytes crawl out of their discord servers, I just can’t help but be infuriated by their pure malice and ignorance.

So fuck em. I’m done with this thread.

You have a nice day now, y’hear?

“16 years of paving the way for Plasma”.

There, fixed that for you.

Huh, I guess you’re getting to them then with your massive winging. Guess you’ll get your Rube Goldberg desktop you want and still complain.

“most very useful”.

List. Tell me which ones.

Gotta respect boycotting Cloudflare on principle… but also, why?

Oh noes! Design spec?!? :( STANDARDS AND ETHICS?!?! No! I Want you to install my halfass, broken solution instead of waiting for a proper solution to come along! I’m such a special boy and know coding better than you! HOW DARE YOU HAVE PLANS!! /s

Like some of you are buffoons and need to go use something like Plasma instead. I love Plasma, not pushing that down, it’s just that if you don’t know the modus operandi of GNOME in 2024 already, you might as well give up trying.

At the very least give up complaining. You wouldn’t have Wayland if it weren’t for WONTFIX, ya daft cunts.

Also known as catching up to Discord, until they reach feature parity and some people actually use it, and then BAM: service discontinued.

No, but as someone who just dumped Nova after realising I’ve been given some company free reign of my device (because I’ve had it so long) I feel Neo is closer to being a more comparable feature set… though still not as much as Nova

In short, it’s a backend/frontend combination that can be shaped using standards compliant web technology, i.e HTMX and JSON, to make it easier in prototyping federated platforms.

Prototyping frontend and backends in tandem is an undertaking to say the least. By creating a framework specifically designed to bridge that gap it will allow developers to more effectively develop, test and publish social media platforms.

…also, they coupled the decoupling… because of course they did. But yeah, if this makes it easier to create federated platforms, I’m all for it.

I.e being more reliant upon Google Play services so you’ll have to accept their predatory EULA.

Now if they released a new driver update system independent of Google Play, that would be better.

I’ve had nothing but good experiences with Flatpaks/Flathub and bad experiences with AUR/nixpkgs.

Fedora also has it’s own Flatpak repo now with it’s own runtime.

In my day, son, a WYSIWYG spat out HTML and CSS. It was up to you to integrate it.

Did you read the new features? CSS and HTML component testing, complete with web scalability (I.e media-query). Sounds very WYSIWYG to me.

But yeah, I know it’s an open source Figma, because Figma can ligma balls.

Is… is this the comeback of WYSIWYGs?

I’m assuming this may be a Flatpak issue. Have you turned on fractional scaling?

haha also nix… because I horde dependencies.

My biggest problem is how people refuse to integrate monetization into federated platforms. Some standard transactional system of sorts that could allow small platforms to create revenue streams for creators.

Not having that means Threads will be the only platform that makes such functions available, and you know they’ll have a quota based incentive system much like YouTube to get all the creators their side of things.

This is bad for musicians, film makers, animators, etc. And if you’re idea is that “you can just link to someone’s Patreon account or their PayPal wallet”, then we’re right back to the same problem again.

Believing that in 2024 you can just ignore monetization within platforms means you’re just leaving a hole in the fence for which nefarious actors can sneak in. It’s better if we standardise and normalise ethical payment models and have them readily available across platforms.

We need a federated, decentralised SWIFT for the fediverse - believe it or not.

haha but using a FLOSS system is… change my mind.

This is my problem, perhaps not with nixpkgs, but nixpkgs:nixos-stableunstable. Throughout history the call to fame for distribution is not all the fancy bells and whistles, but the cohesiveness and stability of the stack - the entire stack.

I’m not saying this is a flaw of nixpkgs, but rather a fair amount of technical debt on the of part NixOS maintainers and developers. It’s a vast movable system of modules, while being immutable at the same time. It ain’t easy. So more contribution is needed.

I’m happy that people join and help with that. I’ll still use NixOS and nixpkgs for embedded, specialised cases, even as servers, but I’m not going to run it on a workstation. But, I’m hopeful for the future. I’d like to run it, but not yet.

It’s not really necessary anyways, nix can run on any system… now onto my adventures of bringing nix to an immutable Fedora system without a container or VM lol

I like this definition and will steal it as well as claim it as my idea for perpetuity, until someone checks me - because I am stupid.

Or, instead, I’ll just misremember it when quoting it in conversation - because am dumb.

Ladies and gentlemen, the real good vs evil metric. We’ve finally found it. It wasn’t good vs evil, but dumb vs stupid.