Having a VPS and routing all traffic between VPS and homeserver using wireguard. It's often discussed in selfhosting communities where the admin is behind restrictive firewalls and policies (which means no port forwarding) or cannot afford to reveal their home ``IPs
Arguing about the metaphors and analogies instead of actual topics? Saw plenty of those during college, especially when the guy in question was being a contrarian just to 'stick it to the man' and look cool to their buddies.
I thought working adults would grow out of it - nah, we're all dumb children inside, including me.
There is a need for something like this. Lots of folks here are die-hard free speech defenders, which I completely understand, but some are starting to get into 'Freeze Peach' territory side of things. You can't expect every new Lemmy instance admin to manually research about this nazi instance or that pedo instance everytime, especially with self-hosted hobby projects. If there isn't anything like this, then admins might as well as start copypasting blocked instances lists from big servers like Lemmy.world or Beehaw.org, which again makes it even less coordinated.
There are plenty of potential for abuse as well. Eventually it has to have some kind of a public wiki where the reason for block can be consulted and have an appeal process with a 3rd party ruling to handle these things.
I suppose we're adding instances manually at this point, but won't the list grow exponentially as time goes on? Not to mention the offline and abandoned instances.
We should be able to test a domain if it's Lemmy-compatible.
Being a chromium skin is a business decision. I don't like it, but at least I understand the thought process. The crypto stuff however? No thanks. That's when I take my business elsewhere.
I imagine executive meetings with people rambling about (an already well established) brand cannibalizing (what could become, if everything goes perfectly, an equally or even more recognized) brand. Basically, throwing away what you have for what you could have in the future.
Best bet is to purchase a prepaid sim card and activate it with an old spare mobile phone (if you have one, that is). This is how you get a "physical" number that's authentic enough for sms verification. This is assuming you live in a place where prepaid sims are sold freely and can be activated without hassles.
There are websites and applications offering "burner numbers" for situations like this or people living in places that place restrictions in new sim cards. Most of them tend to get their numbers from voip providers sold cheaply. They can work most of the time, but picky organizations like Google and Discord can and will probably detect voip numbers when it's the case.
My personal experience is that Google doesn't like it and refuse those ones, asking for an actual "physical" phone number. Discord, on the other hand, did accept voip numbers when I tried (around 2 years ago).
Is there technical reason it has to be the original instance's link instead of any other server being linked to? Federation and all, I see it as having an additional node before destination, but it's not a broken link regardless.
I'm sticking to my win10 LTSC vm whenever something doesn't run on wine. I dont like it when candy crush appears on the start menu.