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.

  • 2 Posts
  • 716 Comments
Joined 3 years ago
cake
Cake day: July 26th, 2023

help-circle

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





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











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



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