Hey, you, who's reading this in the future: you can find out who I am today at https://rarf.zone/about/. 💙


E-mail me at:
info@rarf.zone
Mastodon/Fediverse
yiff.life/@katja

jkap
@jkap
deafhobbit
@deafhobbit asked:

do you know if we'll be able to log in to cohost once it is set to read only?

I've seen lots of people saying mutuals can find their contact info from their profile links. would be nice to know if that will still work once the Posting ends.

yeah. PREVIEW OF HOW WE ARE IMPLEMENTING READ ONLY MODE:

we’ve had a “permission” setup for a while that set your account to read only. it was used to put users in timeout when they weren’t doing anything bad enough for a ban but still needed to chill for a bit.

we’re currently doing an audit to ensure that nothing can slip through this permission. on october 1, we will bulk assign it to all users.

all site functionality that doesn’t involve changing or creating things will remain.

ADDITIONALLY: the data exports include a “find your friends” page which is a unified set of profile contact links for everyone you followed. we want to make that part easy.


eramdam
@eramdam

ADDITIONALLY: the data exports include a “find your friends” page which is a unified set of profile contact links for everyone you followed. we want to make that part easy.

Bro I've been spending the past few days going insane looking at a Google spreadsheet like Sisyphus looking at his boulder.

I could cry, thank you @staff for doing that. You didn't have to but you're doing it and that's why I'll always be a friend of eggbug.

ANYWAY MAKE USE OF PROFILE LINKS Y'ALL. IT'S LITERALLY FREE REAL ESTATE!!!

Addendum from @plumpan about not wanting that info to be publicly available in the archives


plumpan
@plumpan

Go to your profile page, then click "edit profile"

Scroll down to the "profile links" section

Fill them out, and set them to "visible to logged-in users" as such. Per this comment, after the site goes read-only, users can still log in and view them (and get them from their data exports), but non logged in users and stuff like archive dot org should not include them. This means they (cohost users) can still get this info after the site goes read-only.

If someone makes one with cohost-dl and their own login cookie, it will, but that's just how that works since it's acting like the user is logged in directly.

The important part

Scroll back up and save the changes!


You must log in to comment.

in reply to @jkap's post:

thank you. really appreciate all the thought and effort you're putting into this, and that you put into this site over the years.

you all were fucking right about numbers being bad, and i'm never going to stop telling people that.

edit - also, awhile ago you pointed me to the rss reader i've been using happily for many years now (feedbin). thanks for that too.

proposal: rather than making sure nothing can slip through the mass permissions change, you should randomly select one yinglet to still be able to post

also i have mentioned before about replacing cohost plus with a "keep the servers on past dec 31" voluntary fund, but i'm mentioning it again. dead serious.

So in theory between the "find your friends" page as well as the read only mode functionality, if we set our bio info links to "logged in users only" then everyone who made an account can read them, but none of the archives/rips will be able to see them (aside from ones made by users with login cookies)?

in reply to @eramdam's post:

agreed. i had that thing about pinning your how to find me post, but i also want this site to be archived, and worried a bit about having that contact info just hanging out there on archive.org forever. i'm gonna remove that info from my post, and just put it in a sidebar, with most links set to any logged in user can see them.

in reply to @plumpan's post:

thank you for taking the time to do this.

small addition - you can set different display rules for each link, so if an artist or someone does want a profile link that would be preserved in a future archive, they can set it to be viable for anyone.

likewise, if someone wants their bluesky to be visable to anyone on cohost, but for some reason wants people they follow to know their linkedin page, they can do that too.

(i'm sure you know this plum, but i wanted to add this in case it was helpful to others)

I hoped that was implicit by showing the field was a drop down. It's actually really annoying to screencap the drop down dropped-down without firing up OBS so hopefully anyone wondering will read carefully or check the comments....