I am glad to see more people selfhosting their own. Makes me feel less out. Had the same issues.
Casey Tunturi is a highly experienced IT professional with over 20 years in the field, including 10+ years in network engineering and cyber security.
I am glad to see more people selfhosting their own. Makes me feel less out. Had the same issues.
I think it’s more people tired of the pollution that took place, and trying to preserve the clean and friendly one we have so far.
I do personally agree with saving old ones, but I’d highlight them as legacy and then make only the admin be able to edit/create content there, with links to the new one still as suggested before.
Don’t burn books, but let’s not study incorporate the worst things and make them normal here. I think is the feeling.
I support the archiver program myself xD
Worth the read. I do wish as we post these for a summary of what the link is if it were at all possible. The one we got here was very limited and could’ve been a bit more expressive but it was absolutely worth reading!
I would be curious if there might be a way to give some sort of “attribute of credibility” that we could come up with.
I absolutely loved reading wholesome content like this. That’s a great idea! We should collectively work together to shape how we want our future year to be!
I wonder if we could petition Lemmy.ml to make the adjustment? I’m not positive how the mod roles function just yet.
I concur and am actively researching this issue as well. I, for example created my own instance but am not entirely sure I should be the one to host yet another Selfhosted community. I am hoping for a dominate 2/3 of them to win out, preferably lemmy.ml as it was the first I discovered. Alas, you asked a very pertinent question that I think you should keep searching to find. I did see the owner on Lemmy.world actually responding to his thread…
We should absolutely instill the desire to keep this community alive though.
Yo - absolutely!
WG easy posts the GUI on a separate port than the primary Wireguard port you’d need to open in the firewall. I think it’s 51821 - but this can easily be changed depending on if you’re using docker-compose files or a gui like portainer to manage this.
In my case - I am using Nginx Proxy Manager - and it even has it’s own basic password requirement “Access List” availability. With NPM I’m routing that gui over vpn (local dns) but you could put it behind a password with limite security via Access List, or the step beyond look into “middleware” like Keycloak.