Proton is in the bad, or at least in the wrong, for keeping PII about a client to identify via payment option (and did extra wrong by not securing it enough). Honestly, this could all have been avoided if Proton offered a one-time payment service, like SDF does, so that once the payment is received the connecting information can be deleted or expired (or even better: never collected). But a rent-seeking grift model such as subscriptions likely precludes this capability.

Half of internet drops dead when developer of npm package age_pad makes a typo

Which gives away the whole birthday because applications requesting the age bracket can memorize values and notice what day they change.

It’s not even requiring a date, just a number of years.

Several posts in the mailing list thread specifically mention adding Y, M, D fields for DOB.

On the other hand, it’s one of the least intrusive proposals I’ve heard in this round of debate.

It matters not, it’s still intrusive, and it’s the foot-in-the-door to demand more.

If you let a nazi peek into your bar and stay, it’s a nazi bar.

Canonical: “let’s make age verification a DBUS requirement!”

Omg, how can they suck so much! Next time I open that thread, I’m gonna surely find a proposal for systemd-ageverificationd!

I think the obvious problem that those mailing list proposals are missing is that even implementing the minutest part of this law is little more than a “foot in the door” thing. Once the law is passed and a compliant vendor publishes, that sets jurisprudence so that Christofascists can update the law strengthening the requirements, such as adding a user photo (which IIRC account service already supports via $HOME/.face!), LGBTQ+ status, National ID Document, etc.

The correct option in Linuxland is simply to WONTFIX, and if any California and Colorado corporate users whine about it, well, that’s what they voted for. Wanna fix it? Kick your bad leaders out of office.

My message to Ubuntu and all Linux distros is simple:

DON’T OBEY FASCISM IN ADVANCE!

Sending thlose lunatics to Mars costs resources we don’t have and cause pollution. IMO, running them through with a machinegun is easier.

My ulcer’s stroke had an aneurysm when I read this.

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.

Hmmm this would have sounded interesting if it didn’t require releasing new phones. I don’t think Motorola is going to release their next phone within a $200-$300 price range. As it stands, this is marginally better than yet another “ponzi your VS funding on the privacy community” scheme.

What would be useful, if they now have a partnership going, would be to convince Motorola to release the relock keys / firmware fixes for the bootloaders of some models that are no longer in production but are affordable and useful in the secondhand market. In particular, models that see good support from eg.: Lineage. Much easier to start a road towards better privacy and freer systems if it’s feasible on hardware you already have, after all.

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.

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.

Hmmm I can’t think of any single Linux distro that is racist and colonialist enough… but perhaps the connections to Israel coudl suggest something like Hannah Montana Linux?

But at least we know it can’t be any RedHat derivative since all that is strongly US bound, like in a BDSM kind of situation. Back in the time I even left Fedora because they were incredibly racist and even their community channels would refuse to attend to common questions from Latin American users unless they somehow doxxed themselves into verifying themselves as Not-From-Cuba or smth.

That’s it then? cachefs will never make it into / will be removed from the kernel?

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

Heck if I know, but at least we know of the ones who are (eg.: feddit.org are “good German soldiers”).

You can’t leave us hanging by not sharing the posters! At least the article doesnt’t show them, not on direct link.

It’s been on the public fediverse eye enough that I don’t need to do your homework for you, but just look for mentions to piefed in this same sub. One of the exemplary things that was found was that you can’t eg.: “upload a picture that contains the word ‘anonymous’” and that Piefed lies to you about why.