

Out of curiosity, how is WireGuard blocked in your country? I would assume you cellular provider and or ISP sniffs for the default port (51820) - can’t you just put it on another port?


Out of curiosity, how is WireGuard blocked in your country? I would assume you cellular provider and or ISP sniffs for the default port (51820) - can’t you just put it on another port?


I also know there is a script you can set up which will handle the initial contact to federate automatically.
I tried finding such a script but had no luck. I was able to export my subscription list from sh.itjust.works and imported it on my instance.
I had to unsubscribe and resubscribe to the communities I follow as I was experiencing the ‘Subscribe Pending’ issue but after a little while things seemed to start evening out and becoming a bit more stable.


My instance has been online for about a month, the supplied docker-compose.yaml was quite straightforward, had a little headache with Nginx but nothing overly complicated.
The long-con so to speak is federation, you have to subscribe to each community manually to begin federating with them, i have noticed timing issues with other instances such as Lemmy.world and have not been able to resolve them.


Depends on the instance, some can say “hey don’t index us” whereas others can say “hey index us so we grow”, each instance admin has that decision however search engines can ignore the request to not index and do it anyways.


Guess you won’t be making issues there for a while eh


If you really need to expose something to the internet set yourself up an SSO/OIDC provider and have it sit in front of the service and have a deny-first policy in place, whitelist the known few IP’s that need to connect regularly or alternatively geoblock.
Also suggest setting up some security headers, however headers can be confusing for beginners.


Virtualize or containerize everything.
Take that survey, express yourself