• 0 Posts
  • 5 Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle
  • Dokuwiki user here. Your cons are true, but compared to the cons of other ones, they are all solvable. The concern with a plug-in being required to do something is silly. It’s open source and the plugin system is limitless. If it’s ugly, make a theme. I’ve never had a problem with article titles being mutilated, but then again, I treat the file name (e.g. the url of the page) separate from the root header as you’re supposed to.

    Considering your comment about search being awful in another wiki, it’s pretty good in Dokuwiki.

    Considering how much you care about plain text, you should probably discount the con about file names as I’m pretty sure that’s part of why Dokuwiki does what it does. It’s an actual text file sitting in a directory that matches the path.

    For what it’s worth, I admire Obsidian. If it’s a personal project with no intent to share, that’s what I’d use. For business or public hosting, I’d use (and do use, at my company) Dokuwiki.


  • Another fun thing from this show is the magic system, which limits the caster’s ability based on what they can imagine. Programming feels exactly like that to me. I mean, a lot of human ability is limited by that, but most stuff is also limited by physical constraints long before imagination. With programming, we more often hit the limit of our imagination, or time feasibility, before any other constraint.

    Working with non programmers, it’s always wild to field their unimaginative solutions, and refreshing when someone actually had a good idea.

    Working with less experienced programmers, it’s fun to help them through problems. So often they hit a wall they can’t imagine walking through, take some concession and build around the wall. You can appreciate the work, and then show them the simple solution to walk through the wall. If they have talent, they grow quick.

    Working with a much more experienced programmer, or in a domain you don’t have much experience with, helps keep you humble because there’s no way you’re going to learn everything.

    Anyway, back to writing my spells.



  • Ah, thank you and sorry, I should have just searched before posting.

    Part of the issue is the quotes from Facebook rep saying they only do this with public posts, makes me wonder if its user error, platform lying, a bug, etc. but fuck all that. Any situation like this is strictly the platform’s fault, idc if the mother is mistaken and actually posted it publicly, if that’s possible then it’s bad design. Invest more in UX and less in user manipulation. If a parent was intentionally whoring out their children, we’d expect the platform to prevent that, not enable it.


  • I’m not trying to defend Meta, but where in the article does it say that private posts were shared publicly? I’m only seeing that public posts made by adults were used this way. The main rub is Facebook being accused of intentionally serving these publicly posted photos of children in school uniforms (by parents) as bait to join another one of their platforms. Like, a grown man was sent multiple advertisements where this was the exact content, no back to school pictures of young men, or any other type of photo. That they sexualized children algorithmically to bait men into using Threads, and are justifying it’s ok because the parents shared the photo publicly and didn’t opt out of the advertising settings (which seem to be a way to gain followers?).

    One of the men was like, I’ve no idea why they keep sending me these pictures, I don’t engage with them. That might be an even more interesting story, because either Facebook is trying to offer sexualized children to uninterested men, or they know exactly which men are interested in sexualized children and instead of using it to push intervention ads, ban them from seeing the content their AI can definitely classify as enticing, or anything else, they use it to try to make more money.