melroy

Look out there is a bad ghost right behind you in the closet.

Just welcome to the club. Greetings.

Yes please sign the petition!

Yeah Caddy is also a great option.

Something we didn’t had a decade ago. Then the most likely approach was either apache or nginx.

qbittorrent (docker) 😁😎

Or he just uses a reverse proxy like nginx. So all can be hosted behind the same port (443)

Best solution you most likely want to go for. Or use multiple ports.

Wow. Maybe create some torrents out of your collection? 😉

I just torrent the sht out of it. And put it on a USB stick. And plug it into my car. That’s it.

You have been acquitted🤪

I don’t like it. But maybe that is just me.

Bittorrent joined the room.

Another reason to self host: https://techcrunch.com/2025/06/12/google-cloud-outage-brings-down-a-lot-of-the-internet/

Ah yes peertube. There it goes wrong already. The name is too much alike.

My mumble server, gitlab, mbin, nextcloud server, blog,… 😴☺️.

Everything is still up https://server.melroy.org/

I hate youtube so much. When are they moving all to freetube peertube or something? How long do we all accept Google youtube?

Nextcloud

You’re not my bro, bro

Pocket just works. And now Mozilla is killing it. It’s a shame. There are even companies asking them to take over the software and support. So pocket will stay… Not sure how far that is.

Yes. It’s important to verify the dependencies and perform audits like automated scans on the source code and packages from repositories like PyPi and npm. Which is done on my day job.

Also before mirroring data, I look at the source code level if I see anything suspicious. Like phoning home or for example obfuscated code. Or other red flags.

Even at home, working on ‘hobby projects’, I might not have the advantage of the advance scanning source code tools, but I’m still suspicious, since I know there is also a lot of sh*t out there.

Even for home projects I limit the amount of packages I use. I tent to only use large (in terms of users), proven (lot of stars and already out for a long time) and well maintained packages (regular security updates, etc.). Then again, without any advance code scanning tool it’s impossible to fully scan it all. Since you still have dependencies on dependencies with dependencies that might have a vurnability. Or even things as simple as openssl heartbleed bug or repository take overs by evil maintainers. It’s inevitable, but you can take precautions.

Tldr: I try my best with the tools I have. I can’t do more then that. Simple and small projects in C is easier to audit then for example a huge framework or packages with tons of new dependencies. Especially in languages like Python, Go and Javascript/typescript. You have been warned.

Edit: this also means you will need to update your packages often. Not only on your distro. But also when using these packages with npm and PyPi, go or php composer. Just writing your code once and deploy is not sufficient anymore. The chances you are using some packages that are vulnerable is very high and you will need to regularly update your packages. I think updating is just as important as auditing.