nosut

u/nosut@lemmy.world
21 posts · 100 comments

Recent posts

Recent comments

Dropping in to echo this sentiment. I am interested in blocking the instance itself due to the communities it has. I don't want to block comments from the users on it though.

If you use discord for it's intended purpose there really isn't any issue. Choosing to imagine discord is something it isn't and then getting shocked about it later seems like a personal problem.

I myself use it for basic chat with some gaming friends and memes. It certainly isn't the place for sensitive materials.

Home assistant

Plex

Jellyfin

Sonarr

Radarr

Prowlarr

Readarr

Organizr

Overseerr

SaBnzbd

Transmission

Calibre web

Homepage

Memos

Pwndrop

Picsur

Remotely

Youtube dl

Changedetection.io

Uptime Kuma

Kavita

Nginx

And a couple discord bots

Think of it like email.

The email provider is the instance:

Google, Yahoo, outlook, etc

The community/user is your email address:

Android@gmail, Android@yahoo

Because they are different providers you can have the same name since it's the only one on that provider.

I have done basically the same thing. With a few differences.

I setup Transmission and SaBnzbd on the NAS but offloaded sonarr/radar/prowlarr + jellyfin to my server so it's not taking up resources from the NAS.

Found Usenet to download significantly faster overall and sonarr/radar get releases from them much quicker then torrents. Only about 1/15 downloads end up being torrents.

Also overseerr is an amazing tool that you should add into your system. I use it for myself but I also have made accounts for my family so instead of asking me to download something they can just press two buttons and it automatically does the rest.

It's all public information.

Admins are shown on the front page

Modlog shows even when an admin is added or removed.

Blocked instances are shown in the instances list.

Thanks for the work. As a heads up it appears most of the block instances are back however I believe explodingheads is still missing which you may want to confirm.

EDIT: it has been added back to the block list.

I find it unlikely to be necessary because the MichelleG account shouldnt have needed database access and it appears the attack was troll related with basic XSS redirects. You can wait for an official response however it is always good policy for yourself to do so anyways.