1008
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Aug 2023
1008 points (100.0% liked)
Memes
51752 readers
1060 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 6 years ago
MODERATORS
The amount of data that needs to be exchanged because of this approach is not scalable. Assume that there are 3 instances with 100 users each. Even if lots of users upvote/post/comment, the traffic is exchanged only between 3 servers. But if there are 300 single user instances, the amount of traffic/storage will be duplicated which can cause a huge load for everyone which might not be viable in the long run, for both the sender and receiver. PS: I am assuming that the instances periodically update content by fetching the deltas.
That's incorrect, so far no batching is set up for sending multiple posts at once and the exchange is initiated by the sending server, not the receiving server.
IPs change constantly, MAC is per network device (a laptop with Wi-Fi and wired has two different MACs), so you would need to be able to have a list of MACs and MACs can be easily spoofed so thats a whole other set of issues.
Another interesting thought about MACs and any other chip-based IDs that get floated in the future. Spoofing aside, while MACs are supposed to be unique, there are a lot of dodgy mfgs that just burn the same MAC or set of MACs into entire batches of chips at a time. If a new standard was announced, it would be interesting to see the results of orgs trying to take advantage of the ID while shady mfgs continue to not give a flip.