IP addresses are fairly public.

In order to get that kind of infection there need to be a serious vulnerability. None of the services I expose have those kind of vulnerabilities, and I keep them updated.

A Zero-day may be possible, but it can happen with any software.

Any way, even if some of my services got infected that way, I have them all in docker containers. If they managed somehow to insert any malicious software it would have disappeared in the next restart of the container.

And in order to have a software that breaks out of the container it would need to also have some sort of zero-day docker exploit. Two zero-days needed for accomplish that…

Every expose software I have is running on a caddy reverse proxy. And caddy is the only authorized author on my firewall so it gets more difficult to try to run an unexpected malicious software through it.

Any software can have zero-day exploits for that matter.

I don’t think jellyfin vulnerabilities could lead to a zombified machine. At least I’ve not read about something like that happening.

Most Jellyfin issues I know are related to unauthorized API calls of the backend.

I have had jellyfin exposed to the net for multiple years now.

Countless bots probing everyday, some banned by my security measures some don’t. There have never been a breach. Not even close.

To begin with, of you look at what this bots are doing most of them try to target vulnerabilities from older software. I have never even seen a bot targeting jellyfin at all. It’s vulnerabilities are not worth attacking, too complex to get it right and very little reward as what can mostly be done is to stream some content or messing around with someo database. No monetary gain. AFAIK there’s not a jellyfin vulnerability that would allow running anything on the host. Most vulnerabilities are related to unauthorized actions of the jellyfin API.

Most bots, if not all, target other systems, mostly in search of outdated software with very bad vulnerabilities where they could really get some profit.

You can share jellyfin over the net.

The security issues that tend to be quoted are less important than some people claim them to be.

For instance the unauthorized streaming bug, often quoted as one of the worst jellyfin security issues, in order to work the attacker need to know the exact id of the item they want to stream, which is virtually impossible unless they are or have been an authorized client at some point.

Just set it up with the typical bruteforce protections and you’ll be fine.

Not at all. I have my instance sitting on 100MG of RAM and 0% cpu usage. There’s only 3 users that barely use it, but there it is.

It scales by number of users.

It’s true that it’s a resource hog, due to being written in python (who the hell though that), but it all depends on usage.

I selfhost a matrix instance just for myself and my bots. And send myself notifications to the phone client element. I can even trigger a fake VoIP phone call for really important stuff.

Notifications come through as any other message app notification. And calls do the same.

In order to get all notifications and not destroy your phone battery I found out that you need to download the google play version as you need google services for notifications.

I doubt is satire as the project was truly linked with trans groups.

Probably they just count as experience things that are probably not truly experience or maybe there’s a lot that’s being untold there.

Just last week I was setting up a matrix server.

I considered conduwuit but I had a feeling this might happen. Happy to stick with Synapse. It’s just a shane that it’s written in freaking python.

I’ve been thinking for years. Maybe there’s a way to do a collaborative crawler and indexer. In a similar way on how collaborative science is done. And probably using p2p protocols.

Get a bunch of people together to create the perfect search engine in these dire times.

I don’t know fully what’s they are doing. But here’s my workflow with watchtower.

I have a cron task that runs watchtower every day on monitor-mode and only-once one time a day. That creates a list on what containers can be uograded. They using shourrr (it’s already integrated with watchtower it’s just an environment variable to do this) I send myself a message to my phone informing me of what updates are available. If I see fit to upgrade everything I just run watchtower once without monitor mode to upgrade all. I have pendant to automate this last part in a way that I just answer to the bot that’s informing me of the updates and should apply the command without having me ssh into the server. But as for now I have to ssh and run a script I have at hand to launch the upgrade with watchtower.

There are some problematic containers that I don’t want to upgrade this way. For those I have their compose files version locked and I upgrade them manually when I want.

This. Except for a few projects that have given me headaches for an automatic update before (I’m looking at you Jellyfin). Those I have them locked to a version and only upgrade when I think it’s truly stable (spoiler: stable release was not stable) and when I know I will have time to fix things that may broke.

It also has a Firefox extension that add download and subscribe buttons for Tubearchivist directly on youtube website.

Buying a 16 TB hard drive for… purposes.

If there were not for youtube shitty war on adblocks I was able to watch youtube 1080p on a 30 bucks android tv thingy.

I would have to check is someone built an alternative app to keep watching it because power of the device was no issue. When running on a minimal kodi installation it just worked fine.

I used to be able to watch yr on a 30 bucks android tv device in which I installed coreelec.

Sadly youtube apps on there stopped working for me a while ago due the war on adblocks. But the device was perfectly capable of playing YouTube.

I suppose that with tubearchivist and jellyfin you could still somehow watch youtube.

Around 18-20 Watts on idle. It can go up to about 40 W at 100% load.

I have a Intel N100, I’m really happy about performance per watt, to be honest.