False. Browsers can announce themselves as desktop or mobile, or even advertise pre-determined fake window and screen sizes for this purpose (in Firefox it’s called “letterboxed” in the hidden settings). There is no need for a server to have any of this information anyway - either the design of the webpage should be responsive by default, or the server can send specifically whichever files for styles the browser specifically asks for, perhaps falling back to a “all.css” or something.

To be fair, when it comes to both physical and digital fascism, every time the slippery slopers have been told they are sloping and exaggerating, they are actually proven right.

Unless you use xdg-desktop-portal, the field that systemd added does absolutely nothing.

Yet. it’s a foot-on-the-door to demand more stuff, and some distros have already shown they are going to merrily open up their arses and ours.

This statement is so banger for 2026 that I’m asking for permission to quote it.

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 mean, from that perspective, sure. But if the main concern is lack of storage, SSDs currently are of no help with that compared to HDDs (let alone with production being shifted over to serve AIs and datacenters).

Perhaps a dual SSD solution, but still would have to be planned with the potential outcome of either upgrading one of the SSDs or add a third one.

Any decent native client (Pidgin, Conversations, Gajim, etc) will cover most of the important stuff, so it might be worth checking who among those might be willing (+ people contributing) to track development after Movim.

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

I’m guessing a dual disk setup (SSD for the OS, HDD with lots of room for service data) wasn’t an option then? If there’s any nook for such a deal I’d get my cat ready to snatch. It’s sad to hear that this situation hits their instance in the current internet contingency of all things.

Making big companies pony up is always good.

Doesn’t have to be profitable. Can also be punishable, either via adequate state violence, or via People violence. Could be interesting to see something like what the EU has made as a threat of removing all copyright safeguards for the US in case the US presents more as a threat, so I guess the equivalent would be removing all patent safeguards for tinkering with phone manufacturer firmwares if the manufacturers won’t provide a solution for the People themselves.

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.

Hello world!

DokuWiki

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

Disclaimer

I’ve used MediaWiki for 6 years and DokuWiki for [*checks notes*] about 18.

Technically the correct first thing to do is to make the manufacturers release the relock keys for relocking the bootloaders of extant hardware (say, the Moto G6 for an example). Having MicroG or whatever is not much useful if there’s not going to be a feasible phone on which to install, so getting extant phones to become relockable with AOSP distros would be priority. And the way the economy si going and the RAM chips are not, forcing everyone interested to have to buy a whole new phone is not a smart choice.

Once the relock keys are out, fund All the Things. Lineage, Calyx, MicroG, what have you.

Fake journalists not even bothering to google that XMPP exists #10496839485.

Let us all hope Servo does not go down the same path.