Correct, which is why reddit must ultimately do it. Only they would have access.
abff08f4813c
joined 2 years ago
Yup, I couldn't see my own comments or posts on subs that were private. When I tried to delete them via API/script it got me an error too.
However, there's an exception. If you are a mod or approved user for a sub, then you can see and edit/delete as normal. I have never tried this scenario but maybe in this case when it go public again, any deletions are undone (because of the caching issue).
They've got this big profitability issue right? Wouldn't it be better - more affordable - to take those concrete follow-up actions instead of repeatingly spending money on showy, quirky, fun things over and over again?
I think this stems from two things. First, IIUC GDPR applies if the entity is based in and the data is in the EU. So for example all USians and Canadians are covered by the GDPR for kbin.social because kbin.social is in Poland which is in the EU.
This probably doesn't apply to reddit which likely processes data for non-EU folks outside of the EU.
Second, for reddit it's probably easier to just handle routine GDPR requests for everyone rather than trying to verify that folks are covered by the GDPR individually. Especially because reddit is somewhat anonymous (no real name or identity verification).
That said, keep in mind that right now reddit only handles these requests to give you an archive of your data. They still expect you to delete it manually. (I know, it's not GDPR compliant, but that means you have a choice between fighting reddit through court and such or taking the path of least resistance.)
Sounds reasonable. So mostly it's just a sign of reddit not giving a darn to those that they used to reach out to. Another sign of how downhill things have gone.
That's cool, I didn't know about that. Hopefully someone acts on https://discourse.linuxserver.io/t/kbin-and-lemmy-fediverse-reddit-alternatives/7667 soon.
Cool! Do you have a writeup or something that you could share? Maybe any mods you did to the docker-compose files to get it to work? Would help a lot of us out.
Yeah, that's one of the things kinda holding me back for now as well.
Edit: I fnally gave it a shot. It turned out to be pretty easy. I just followed the admin guide on kbin's codeberg at https://codeberg.org/Kbin/kbin-core/wiki#admin-guide and scrolled down to the "Install with Docker" section.
Did this on an M1 Mac that already had Docker Desktop set up, so basically I skipped the first four subsections as not relevant and went straight down to the "Clone repo" subsection. (After cloning the repo, there is a section on getting docker-ce set up for Linux/GNU that I skipped).
I simply did "docker compose build" and didn't explicitly need to build fresh images. Then I ran "docker compose up" and the system was up.
Going to https://kbin.localhost .. told me that I forgot to build my npm or yarn assets. Whoops!
Since I didn't want to mess around with yarn on the host system (though that probably would have worked if I tried) I just found the kbin-php container id by checking the list from "docker ps" and then used "docker exec -it [kbin-php-container-id] /bin/sh" to log in with a shell. Then I ran "apk add yarn" followed by "yarn install" and "yarn build"
After that everything worked.
Somehow I missed seeing the configuration section, and so I created an admin user by registering a new user through the UI, and then running "docker exec -it [postgres-contanier-id] psql -U kbin kbin" to connect direcly to the database. Using psql I executed "update "user" set roles="['ROLE_ADMIN']", is_verified=true where id = 1;" then logged out and logged back in get recognized as an admin.
Finally I went ahead and created the random magazine through the UI.
Something is still off. The UI works fine and anything locally is good, but I can not seem to subscribe to magazines on other instances or even search for them from my own kbin.local - they just comes up empty. Not sure why this is happening but I'll update as soon as I learn more!
Hey, I think I can help you with this. If you go to https://reddit-top20k.cworld.ai then you can search for and download an archive from the subs you posted in. From there you can search for your old reddit username and rediscover your old content that way.
Something I love about the fediverse!
Let me reword what I originally wrote for clarity so we can understand how this part got misinterpreted:
IANAL but there's suppose to be a blurb in there about ~~not exercising too much control over the content~~ (actually i was wrong about this, as it was about) [moderating in good faith]. The more moderating decisions the admins get involved in, the greater the [chance] in going afoul of this. Once the company ~~has editorial control~~ [is deemed to not be moderating in good faith], they lose the Section 230 protections [for that or those particular moderating decisions].
The caching issue would clear up eventually, just give it some time. The CCPA process is slower, so probably the caching issue would be resolved by the time the courts heard it.
Private is different. What if I posted in a sub like r/BasicIncomeUSA that went permanently private during the blackout and never came back? 30 days, 45 days, still private. Worse, what if it's a sub where the mods all delete their accounts - or they are unresponsive (because they quit using reddit without deleting their accounts).
So yeah, private means that reddit has to be the one doing the deletion, as a regular user may not even have the tools to delete otherwise.