a reverse proxy these days is pretty much just a requirement of any dynamic service. they often run on the same host as the software
a reverse proxy these days is pretty much just a requirement of any dynamic service. they often run on the same host as the software
hello welcome to my new venture capital firm: we specialise in funding game studios where 90% of the staff got fired in an acquisition turned shutdown
i wasn’t talking about ethereum, and i don’t think anyone was saying they don’t have TRADE OFFS. in the world of consensus protocols, there are many different trade offs that build a network that suits your needs
however the consensus protocol has little to do with how mathematically secure a network is: the security of the consensus protocol comes down to a lot of complex things
it also has nothing to do with how you bootstrap a node
these things are all different, albeit interconnected things
no; they all have trade-offs and that’s different… you can have trust less proof amongst semi-trusted parties like a consortium of banks: they don’t entirely trust each other, but trust each other enough to keep an eye on the other members of the consortium
there are plenty of situations like this that are non-public
you’ve just demonstrated your lack of depth of understanding of blockchains. congratulations, your opinion was correct about 15 years ago. the technology has moved on
that’s not what the quoted text says at all… let’s rephrase this:
much like how users of one lemmy service such as lemmy.world can still reply to users of another service such as kbin.social, users may still view content and interact with users on any other instance in bluesky
this doesn’t say that lemmy/kbin isn’t part of the fediverse. it takes no position on that fact, merely saying that the things conceptually work in a similar manner
peer to peer is an option too
IP is still information you don’t want falling into just anyone’s hands… the issue is you don’t want a big list of people, locations, and “dating” metadata all gathered in a single place - ESPECIALLY if that information includes things like sexual orientation, and in the case of grindr, HIV status etc
grindr in particular would be tricky! the location data has to be kept safe from bulk collection and targeting, but public for limited queries
it also has to update fairly quickly
it’s possible, but that would seem… odd… for such a large and tech-savvy instance. there’s a lot of reasons why this isn’t a good idea, and very few technical reasons why it is
my guess is that it’s less about obscuring server location for privacy reasons as is the implications in this thread, and more about handling changes cleanly or something like that - in which case, sure it obscures the server location but more that it makes the server “location” (or hardware, etc) irrelevant and fungible