Well, you can disable window controls in gnome and KDE afaik if you want. Then you’ll only have the various app-specific buttons that are necessary for functionality.

If you’re looking for every app to have a vim-like interface or something, well, that seems a bit unrelated to CSDs.

Honestly, I don’t really understand the hate that client-side decorations get. I find that they’re generally pretty useful and good.

I think a lot of it comes from people who want to ‘rice’ and theme their desktops but I personally think that dream has sailed. The kind of theming people want on Linux systems is simply not possible without massive amounts of work and downgrades to accessibility, security and usability.

Maybe I’m misunderstanding but for clarification, the fact they’re drawn by the client actually means they can always be the same across different environments. This is in opposition to server-side decorations which are drawn by the desktop environment and should match the environment as a result. That said, server-side decorations are largely much less extensible than client side ones.

The DMA (Digital Markets Act) has clauses that force big companies that are considered “gatekeepers” to allow interoperability with other services.

Images aren’t federated through ActivityPub so I don’t really see how deleting media is supposed to work.

Yes, they are. Every instance downloads everyone’s images for a “cached” version that is currently never used. This is what makes this problem especially insidious and straight up dangerous in cases like CSAM.

It’s a basic curl command, that shouldn’t be “arcane” if you’re setting up a server.

This is the equivalent of saying that any instance admin needs to know how to use curl while most people have never used a commandline. Not only that but you need machine access to know the api key which I would wager instance admins do not necessarily have.

I think this is the result of not prioritising work that makes moderation possible by non-technically inclined people and it is genuinely a failure of the system.

The priorities of development on Lemmy are decided by developers and the people who are not are simply pushed away. Most community leaders and moderators are not developers. The mental gymnastics to justify this lack of tooling is tiring.

They can, if they read the manual. Mods can’t, but instance admins can.

Yes. If you use arcane commands using the docs that are in a pull request that is not yet merged. This is not accessible to many instance admins and it is only “technically supported” which is the worst kind of support from my point of view.

Bad faith or not - Fascists are not accepted.

I mean, I essentially proposed to do this myself in private conversations with Dessalines but there was no willingness for a shared roadmap so it felt pretty pointless.

If you can point me to any comments like these, I’d love to remove them fwiw.

The codebase is remarkably not fun to work with according to everyone I’ve talked to. The language (rust) is also not common for web services so many have no experience with it. These things made people want to start from scratch.

It’s like this on beehaw as well!

Community managers - sometimes just talking about your issue with someone will help tremendously in figuring out how to put it and they often can just do it for you. That said, Lemmy devs do not value work being put in the issue tracker - they have admitted to not reading it. People who cannot contribute code are just entirely ignored and have no power in the project’s direction.

Stract and SearXNG are two entirely different projects. SearXNG is just using other search engines to power itself - it’s known as a meta search engine. Stract has its own index that does not use other search engines to power itself.

I will say I’m pretty glad to see a search engine which actually is not just a meta search engine. I wish Kagi would attempt this rather than partnerning with Brave.

One thing I find odd though is why these engines trying to make their own index don’t do the adversarial strategy that Brave Search has done : while using other indexes, collect what people actually click on and use it in your own index. I will note that I do not support Brave.

For most of its history, journalism has been locked behind a paywall. I think it’s a bit disingeneous to claim that this principle is against the idea of journalism. Journalism and especially good journalism is expensive - under a capitalist system, it’s entirely normal to ask for your work to be valued through monetary means.

That said, I’m most annoyed because no one is actually talking about Stract, just about how 404media decided to lock the article.

For everyone complaining about 404media needing an account for the posts, they explain their reasoning here : https://www.404media.co/why-404-media-needs-your-email-address/

I remember hearing this story a long time ago, It’s still so shocking that this happened.

I personally think it’s likely. Facebook is one of the companies that will be targeted by EU’s DMA and since they co-authored this standard, it seems likely they’d want to use it to respect the DMA. If Facebook uses it, others will adopt it because of their sheer control over messaging services.