I write English / Escribo en Español.
Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.
This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.
It being unenforceable is part of the ploy. It means moneyful entities, like say Microslop or a Christofascist national church, can harass developers aligned with non-rightwing principles via lawsuits. They don’t have to prosper, they just have to cause a cost in money and quality-of-life.
Terms of Use / Terms of Service are different from Licenses. That said, even if it was compatible that would be a good thing, as the impression I’ve got is that the “hard-liner” Free Software licenses are becoming a thing of the past now that what is needed is “Ethical Source” licenses, that eg.: restrict usage in AI.
“I use LibreOffice Writer and other Linux apps”. There, simple as that.
If they ask why and show a more actual concerned interest, I usually mention Microslop history of privacy invasions and history of deliberate incompatibilities in Office, and recommend a few links documenting that stuff as well as some legal hot waters Microslop has gotten into.
XMPP, hands down.
Not only for me, but for other people. XMPP is leaner, more robust, easier to administer and overall not a nu-protocol, so it’s easier on the staff of the instance operating as well, leaving them more of their allotted time to tend to the community. And with client utilities like Gakim, Conversations and Movim, focusing on the service proper is even easier.
Making big companies pony up is always good.
Could you build an interface on top of it to look exactly like discord with all of it’s functions?
In theory yes, and Movim is movim’ in that direction (yeah I invented that pun, blame me). That’s part of the trick with XMPP, it’s quite extensible.
He’s already talking to that machine of his that censors his drunken ramblings with cute little asterisks. I wonder what does that do to someone’s psyque tho.
Yeah there’s a lot of stuff like that. If moving a page requires updating the history of every page that links to it, that’s a whole mess that’s much easier to handle when your wiki is a database.
Heck, it’s even worse. What happens if you move a page that has translations (with the Translate plugin) pages associated to it? Translated pages are not necessarily linked to each other, and even if they were, the semantics of trying to move each one can cause issues.
In the end, IMO, it’s not worth the effort to automatize. Just use something like implement “move” as “make a copy and leave a redirect behind”… which IIRC MediaWiki also does, and leave manual operators to decide what to do with the moved-from redirects after the fact.
The table syntax at least is miles better [than MediaWiki]
For simple tables or for calculation tables, yes. It’s relatively close to Markdown, even.
Unfortunately it does not play nicely with any sort of advanced syntax on table cells themselves, such as lists inside tables. For that, I prefer the MediaWiki syntax even if it’s ugly (a DW plugin called exttab3 provides near 1:1 MW table syntax).
Some stuff like tags and moving pages have to be achieved via plugins. Seriously you can’t even rename a page?
IMO it’s one of its strengths, and you can do most stuff with plugins. You can even render your pages as web slides with one plugin, and in fact I used to use DW as my “PowerPoint” for quickie presentations for over a decade.
All that said, there are DW “bundles” that incorporate some good and cool things together from the get-go. Anything that incorporates the Include, Indexmenu and Wrap plugins should be golden for getting started.
As for moving, I’ve asked around for a couple of years (more like 8) and seen how things have changed (or not), and it turns out it’s half a consequence of documents being plain text files (there had to be some sort of disadvantage to that!). While it might (actually, is) possible to just move a file, there is no cheap, simple and fast way to also update all links that point to that page across the wiki, as those might be not normal links or even be dynamically generated by plugins. So most implementers are at the philosophical stage of “what even is a ‘move’?” ATM.
I hear there are improvements with some plugins that advance some of the work, but I haven’t tested myself. Don’t need to, since I just use the Page Redirect plugin if I want to mark stuff as “moved”.
Mutilates article titles. Makes everything lowercase and replaces non alphanumeric chars with underscores (or something else configurable)
Mutilates file names and mutilates article titles, separately.
The former is one of the PITAs in the design I feel. There are good, stable patches that allow uppercase filenames in the filesystem (as well as Unicode and even emojis) bu no core config option to enable them. The closest option is “safe filename encode” I think, which allows most accented letters, diacritics and stuff, but no punctuation signs, and still replaces into underscores.
I get the why (it’s very useful for making sure article and section IDs are unique) but, like, still. It’s 2026, I can name my second video card like the poop emoji and my system won’t complain.
The latter is a configurable option actually. Just set the “use heading” preference to “always” and articles will always be titled the way the first heading available does it (so, technically, the same behaviour as MediaWiki).
I’ve used MediaWiki for 6 years and DokuWiki for [*checks notes*] about 18.
Let us all hope Servo does not go down the same path.
Thanks!
It’s not so much about wholly removing webgl contrasted to at least having some sort of fallback that allows the site to be experienced, but thanks again for at least tackling the change.
It’s 2026, being vibecoded is a self-explanatory problem.
You mean why does the site for a forum software need webgl, by which the only reason I can think of is tracking visitors somehow. It’s not like the background landscape on the site is dynamic or something.
Mind, seems to be vibecoded.
I certainly hope so! But still, that’s useless for Flatpak if they themselves don’t also make the change.
It’s quite telling that a system intended to make apps usable everywhere on Linux, does not use the audio backend that works everywhere on Linux.
Potter the same lamepotterycrap of systemd? I can feel where this is going.
It does mean a form of provider lock-in, which is or can be its own issue. Also, while PostgreSQL is one of the best database engines out there among the FOSS stuff, it is verifiably and vastly overblown for stuff like “store a name and a email”, and I at least am not aware of any sort of “Postgres Lite” engines else I’d be using them at work.
To think there was a time when Amerikkkan adults actually knew some History, that the developers could trust to use as an age check! Quite the surprise, I imagine in part it was thanks to Carmen Sandiego.