a lot of stuff:

• owncloud
• paperless
• immich
• jellyfin
• jellyseerr
• traefik

than i have stuff only accessible from local, like the *arr stack.

i’m not using cloudflare or anything, should I?

the only exposed ports i have are http / https and a random port for ssh.

i also don’t use any sso… maybe i should set one up.

this is the way.

also fail2ban to ensure that nobody bruteforce it’s way in.

don’t be an asshole.

works for corporations, individuals, and everything in between.

i think nsfw as content warning is ok. after that, we need tags.

with tags you have, then the ability to filter them.

since tags are not standard, you can have as many as you want.

i got one from GoDaddy, but i regret the choice…

i think they added the ability to force upload a photo in one of the latest releases, see it that helps.

otherwise yes, you have to delete that record from the db…

yes i agree

the salary?? you will hear about it on the tird interview if you’re lucky

i hate this so much. i have applied to jobs with so generic job description, and than thay wanted a very specific thing. but no it was not in the job description.

can we have the GitHub link? so i can subscribe to the release. (and leave you a star <3)

how did you find this?

they said angle brackets <>

so confusing reading bidet and is a totally different thing from what i have in the bathroom

thank you

we should implement tags on lemmy, that filter by tags.

i don’t care about us politics and sports. i could create a filter with sports and (us & politics).

same for the nsfl / porn, add those as tags, and you can filter them.

you have “bot account” checked on the settings.

add fail2ban, so they cannot brute force the web interface.

interesting, even if they got access to the plex service, how they could have escaped the plex docker container?

i run pretty much the same stack as OP, but also run immich and paperless. i very much care if someone else have a way to access those…

ugreen is Chinese, but one of the good ones.

not really add.

when you set up an instance, all will be empty. the moment an user subscribe to a community for the first time, that community will start appearing on all, for everyone to see.

for this reason all is different for every instance.

the motivation for it is resources. if a new instance would receive updates from all the communities on all the instances, it would be very much like ddos. and a small instance will not be able to endure it.