terribleplan

Pretty sure it needs to be https://$user:$pat@github.com/username/repo.git#branch.

1. You host it yourself
2. You can get a cool domain name
3. It's pretty low maintenance

I run my own for myself and some friends who don't really use it. If you are interested in doing so I say give it a shot.

Docker isn't super necessary, there are some scripts out there that hide a good bit of how it works like the official ansible playbook or lemmy-easy-deploy.

I use docker to easily run many pieces of software in isolation from each other, it's like VMs if you're familiar with those, but different in some key ways that don't really matter for this discussion.

I would still go with one that isn't one of the biggest. My general advice is to find one that fits the vibe you're going for, communities you're interested in (e.g. some are focused on art or cybersecurity, etc), or is somehow tied to your locality. It shouldn't matter that much, though some servers will be a little more (or less) strict with things like federation, content warnings, alt text, etc. Usually the server will have some info telling you some of this, and their admin should be linked and likely has a post or two pinned to their profile explaining some of this as well.

I am partial to kind.social, though have opted to run my own instead of joining up anywhere.

Honestly it depends on what your experience level with running software is and what you want out of it. For me things have been rather smooth sailing as I already host a number of things for myself (so know all about domains, DNS, servers, reverse proxies, docker, etc.) and I am the only one actively using my instance right now so (local or admin-level) moderation isn't really an issue either.

I am very aware of what it takes to run a small instance, you are indeed correct that domain registration is not the hardest part.

Just run your own instance, I say.... that way it's your fault when you forget to renew the domain name instead of the poor soul running vlemmy.

It depends on what specific thing you want to add geoblocking to, but often something like the MaxMind GeoIP database, which then can feed into a firewall to pre-emptively geo-block at a connection level, or as part of e.g. nginx geolocating the IP a of the connecting IP then making the blocking decision at request time.

There's a project that works with Traefik's forward-auth middleware to do this, which is probably how I would go about it if I wanted it at an HTTP level.

Nope, not from a DNS level. All the posts you are reading are cached by whatever instance your account is on. Basically the only thing served from the remote instance is full-size media uploaded to that instance. Even thumbnails are served from whatever instance you use. Mastodon/Akkoma/etc can be set up to even proxy full-size media for users, which is a feature I imagine will eventually make its way into Lemmy. Your best bet at the moment would be to find an instance that defederates those you don't want to see (or run your own and do so yourself). I know "blocking" an instance is an often-requested feature, so that may end up a feature in Lemmy itself at some point.

Nope. PETG is maybe the easiest "safer" option, but AFAIK there isn't a true food safe filament. Also 3d printed things will basically be impossible to clean without extensive post-processing (including probably needing to coat it in something), so "safer" single use pretty much.

Yep, nobody is talking about it at all...

• https://prime8s.xyz/post/3812
• https://lemmy.ml/post/1409164
• https://lemmy.one/post/337062
• https://lemmy.world/post/1079916
• https://lemmy.world/post/1060627
• https://lemmy.one/post/629353