Feeding user data to an LLM. Jacking up API costs. Being generally unusable on mobile. Usurping old.reddit.com to try and force me to the official app on “unmoderated” and NSFW threads.

Now with their IPO and a need to deliver ever increasing subscriber numbers and improved metrics for shareholders every quarter, the writing is on the wall.

I hope it goes to zero. The only sad thing is all the knowledge that will be lost due to the sky high API pricing when the site eventually does sunset. I’m guilty myself of trying to de-enshittify google somewhat by adding reddit to just about every search. Hopefully people smarter than me have ways to archive that info.

[–] andreas@lemmy.kfed.org 5 points 5 months ago

I've been using Libreddit and now it's fork RedLib side by side with Lemmy. Haven't had too many problems, does seem to be a good way to access the knowledge you mentioned without specific api use (it runs in docker too) https://github.com/redlib-org/redlib

[–] Wiz@midwest.social 5 points 5 months ago

Yes, but glue is the surprisingly tasty ingredient on pizza too keep your toppings from falling off.

Just be sure to use non-toxic glue, because the other kind tastes terrible.

[–] Blaze@reddthat.com 2 points 5 months ago

Welcome here!

[–] tal 2 points 5 months ago* (last edited 5 months ago)

Feeding user data to an LLM.

I mean, somewhere, even if not now, if the Threadiverse becomes large enough, someone is gonna be using comments here to train an LLM too. That's just gonna be a given unless you want to use non-public forums, and that kills the searchability and accessbility to everyone that makes most forums valuable. It's even easier to access here than on Reddit -- just set up an instance and federate with and subscribe to everything.

I guarantee you that people are going back and training LLMs on archives of old Usenet discussions too.

The rest of it, yeah, I get.