Some middle-aged guy on the Internet. Seen a lot of it, occasionally regurgitates it, trying to be amusing and informative.

Lurked Digg until v4. Commented on Reddit (same username) until it went full Musk.

Is on kbin.social but created this profile on kbin.run during a week-long outage.

Other Adjectives: Neurodivergent; Nerd; Broken; British; Ally; Leftish

  • 0 Posts
  • 9 Comments
Joined 1 month ago
cake
Cake day: June 4th, 2024

help-circle


  • So I decided to go peek at the ragecomic subreddit. Yes, the very one-time ragecomic home-from-home outside of 4chan. Last post 17 days ago, using at least two “extinct” faces, got 600 upvotes.

    It’s complaining that there are no good tools to make ragecomics any more. (I have not checked to see if that’s true.)

    Y’know, I feel like they should stay there. Anything that’ll mess up an AI should stay on that site for as long as humanly possible. smilingthumbsuprageface.jaypeg



  • Yep. When I was migrating, I saw some advice to avoid Lemmy on account of its provenance, which is how I ended up on Kbin instead.

    Unfortunately, it’s not going well on the original instance (getting in before “how’s that working out for you”), but for reasons very different to lemmy.ml.

    Still don’t have a lemmy account, but I am, for my sins, subscribed to communities there. Like this one.




  • [I have told this story elsewhere before]

    I thought I was so clever once. I taught a word filter about “th” thinking that would solve the problem, but it still got stuck on Scunthorpe. mfw.

    Had to step through what it was doing. It had hit a rule that treated ‘oo’ the same as ‘u’ which, at least sound-wise, is valid for some words in some dialects. e.g. Consider “book”, which is identical to “buck” for many people. You can imagine why that might want to be caught.

    To save you the head scratching, it had spotted the ‘c’ then a double-‘o’ then the ‘n’ and threw it out as containing a known racial slur.

    The filter was for a random string generator so that it wouldn’t generate strings with bad words in them. Seemed like a good idea at the time.

    Since it was unlikely that it was going to generate “Scunthorpe” anyway, the problem remained unfixed.