- cross-posted to:
- fediverse@lemmy.ml
- cross-posted to:
- fediverse@lemmy.ml
Over the past year or so I’ve been playing with the idea of a decentralised social platform based on your location. By putting physical location at the centre of the experience, such a platform could be used to bring communities together and provide a source of local information when travelling. Please let me know what you guys think.
I spent several weeks thinking about this exact idea.
Federation is cool. You could set up each instance to only federate with instances for nearby towns and cities. Maybe a “2 district” radius. Users would only see content for their local communities. Local news stays local. Local government could officially participate if they wish. People you talk to are actually neighbors you might see in person. Larger regions like counties, states, provinces, or even countries, could also have dedicated instances and federate similarly. I think this is the big appeal and it sounds awesome!
There are a few problems 🙂
First is a little bit of confusion with posting. Let’s say that I see a post about a cool new restaurant in my town. I share it with a friend who lives a few towns away and that’s outside the “federation radius”. I can’t share the post with that friend very easily. Maybe the tools could be enhanced to make this viable?
Second is a matter of privacy. How do you know that new accounts belong to people associated with the geographic location of each instance? If you don’t validate, the system will certainly be abused. If you do validate, then users need to supply some real info! Home address, ID, etc. that’s a big deal for users and instance admins.
Third. What happens if you move? Do you have to abandon your old account and start over? Again, the system itself can be developed further to solve this. But that’ll take time and money.
Next is the operating costs. You would need to build thousands of instances to build this system up. And each one would have to be tied to a geographic region. You need new features to handle signups this way. You have the simple cost of running these servers. You probably need a lot of staff to manage it all. This is an expensive platform for one party to run. Alternatively…
It doesn’t have to be one party running this entire system. That’s the point of the Fediverse, right? The operational costs go way down if anyone can run their own instance. But how do you enforce the rules of federating with instances for geographically nearby locations? I don’t see a reasonable way to solve this one.
I could probably keep listing issues. But these are the big ones IMO. If you solve these, the system is viable and could be amazing.
Hey, it’s good to know that others have been considering this sort of thing.
My article does detail solutions to some of the issues you’ve raised here, but I’ll go over them each just to see where our visions differ:
All posts will have a publicly available URL. I don’t think it would be good to create closed communities, only solutions that would show the user local posts.
I don’t believe we should validate that people actually live in the community. I think administration of blocking malicious users should work just like Lemmy, but I don’t think the potential for abuse is quite as high, given that the reward for a spammer would be to spam to such a small amount of people. There’s less work in spamming to a larger group by choosing just about any other type of community.
You don’t, just like Lemmy and Mastodon, your account on one instance could be used to interact with other instances. The Connecting Instances section of the article details how this could work from a technical point.
Distributed cost and administration is exactly how I see it. I would only care to host my local instance.