It took me so much fucking time to realize how it works. There it is:

https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/

I learned Kubernetes in a hurry in my previous job, so I skimmed over lots of “obvious” things (in my manager’s eye) and this was one of them:(

I just rented a VPS from Hetzner because that’s the workflow I’m already familiar with. Lowest tier, 5$, and since it’s ARM it’s also beefy enough to never need an upgrade I hope :P

What’s that?

Frankly I’m not sure what it does haha. What are the “best communities”? Which communities? Also what does it actually do, subscribes all users on your instance to those “best communities”?

You nailed it, it only pulls posts from communities that someone on your instance subbed to. It doesn’t even pull retroactively; your instance only starts pulling posts created after the first subscriber on the instance subbed.

I’m more concerned regarding media, because just like Mastodon, the pics themselves are copied from other instances onto yours. I hope it will be enough to just find -mtime -delete once in a while

“vanity purposes” lmao I love it

Also seeing the federation happening live at tail -f /var/log/nginx/access.log is so satisfying. I think I like computers

Oh there’s an --exec flag as well? That’s great. This seems like a totally viable solution for cases where the crux of the container is a small script, with a handful of decision branches so the surface area to cover is manageable, but it also needs to come in a non-alpine distro because I assume that’s the hefty part that we’re like to remove. But that’s just off the top of my head, I’m sure there’s more. It’s genuinely a good idea and it deserves a respectful README as well :(

It ptraces the main container process and cuts off unused files. It also fires some customizable HTTP requests to trigger any dynamically loading libraries. Clever idea. If I understand correctly, the problems that arise to me are:

1. Undoubtedly some essential files will be omitted. Unless my image consists merely of scratch and an executable, I can’t imagine myself successfully covering all edge cases.
2. What about files that aren’t loaded by HTTP requests?

I’m not shitting on this program at all. These are two problems that I’m sure they could solve or just tell straight up “we can’t guarantee it’ll work in XYZ scenarios. Don’t use it if that’s your use case”. Then I saw that this is backed by some kinda SaaS with a domain that ends with .ai, and that explains why THAT FUCKING README IS WRITTEN like a FUCJik/INg MIND NUMBING LINKEDIN POST that my CEO could write bro what the fuck do you mean by simplifying the value of my digital assets in a seamless secure cost efficient way??? Who fucking cares??? ?WHat does your program ACTUALLY DO???

10000000s of seemingly AI-generated paragraphs going on and on about how convenient their product is, 1 measly line in a diagram that describes what it actually does. Again not to shit on the programmers at all, this is a great idea and I’m glad that it’s being explored I just hate this industry I can’t read another pile of gibberish like that. That ruined my night. Thanks for listening