this post was submitted on 17 Dec 2023
47 points (94.3% liked)

Fediverse

17698 readers
2 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
deadsuperhero@lemmy.ml
wakest@lemmy.ml
47
Yet another approach on Threads (Jerry Bell) (infosec.exchange)
submitted 10 months ago* (last edited 10 months ago) by Masimatutu@mander.xyz to c/fediverse@lemmy.ml
17 comments fedilink hide all child comments
 

I continue to be squeezed by both sides of the threads situation. I am operating on the premise that people who think I’m a terrible person and this is a terrible instance for allowing any interaction with threads have left and/or blocked, those remaining seem to want to either have nothing to do with threads at all and are mainly concerned with their data, and those who want to seamlessly interact with threads. I have threads limited/silenced on Infosec.exchange, but that isn’t seamless, and it’s also not fully blocking. So, here’s my proposal: I remove the limit from threads, and run a job to domain block threads for each account. Any account who chooses can undo the block (or ask me to do it) and then they can seamlessly interact with threads, and those who want nothing to do with them get their way.

[...]

(Note: this was only intended for Infosec.exchange/.town, and fedia.social)

– @jerry@infosec.exchange

you are viewing a single comment's thread
view the rest of the comments
[–] Killercat103@infosec.pub 11 points 10 months ago

Sounds like a decent approach. Private by default but without taking away the freedom to interact with threads if so desired. At worst an inconvenience