4 ms·
I've been kicking a design around in my head for the past few weeks which retains most of the outward form of something like Reddit, on the grounds that it has
by jerf 9y ago
I've been kicking a design around in my head for the past few weeks which retains most of the outward form of something like Reddit, on the grounds that it has proved to be a model that can attract users, but redefines the upvote and downvote process such that an upvote now means "I want to see more of this poster's comments, and transitively (and weaker as the links go out) what that user sees" and a downvote now means "I'd like to see less of this poster's comments and transitively what they upvoted". The difference here being that upvote no longer means "I think everyone should see more of this comment", but now "I think I should see more of this commenter".
I think it ought to be unidirectional to prevent obvious attacks. I'm not too worried about the "filter bubble" because I think you are inevitably in a filter bubble, and it's on you to manage it, not expect random sites on the internet to somehow pop you out of it (they basically can't, by definition).
I think I'd still want categorizations for subject, just to give things some sort of focus. The result is that instead of /r/politics or /r/$ANYTHING being captured by some sort of single monolithic gestalt, multiple simultaneous gestalts could be running side-by-side. You'd want some deliberate mixing, both to keep things interesting and because I think you'd want to ensure some "heat" in the simulated annealing sense to ensure that things don't get too isolated and things keep moving. (Communities themselves keep moving, after all.)
The net effect of this is that while trolls would still exist, anyone not interested in trolling should naturally filter them out of their view relatively quickly, while the trolls get each other to troll at. Since they can not be eliminated, all you can really do is fence them off. One of the other interesting side effects is that you ought to get some other interesting communities in there, too; the community of people who thoughtfully comment, the community of "doers", etc. One interesting possibility is that this may even allow "celebrities" to have a "social network" that nominally anyone can join, but requires sufficient social proof that it isn't just "anybody with a Twitter account and an itchy trigger finger can get the first reply below $CELEBRITY's tweet.", wrecking the utility of social media for the celebrity. I haven't quite solved the question of how to initialize the communities once the system gets going, but it's probably feasible.
What stops me from coding this up is that whenever I start really fleshing this out into an implementable system, I realize it violates one of my life rules: "Never engage in an endeavor in which the worst case scenario is complete success." I don't want to run a community site like that. So for me personally, the outcome matrix boils down to "Failure -> waste of time, Success -> oh shit". Because even if this did miraculously fix all social issues, which I am hardly naive enough to suppose, there's still legal compliance, DMCA compliance, etc., all sorts of things I personally have no desire or drive to do.
However, by all means, feel free to "steal" my idea. While I am by no means an expert in this field (the aforementioned paragraphs are pretty much the sum total of my thinking at this time), I'll even spot you some free "consulting" in the form of playing intelligent-rubber-duck to bounce ideas off of if you'd like. And let me know if you get to deployment.
- Slansitartop 9y agoIIRC, Advogato did something like that a million years ago. https://en.wikipedia.org/wiki/Advogato https://en.wikipedia.org/wiki/Advogato
- jerf 9y agoWell, it wouldn't be the first time someone had the right idea decades before the world was ready. (No sarcasm; fully serious.) Though you'd want to open it up to people beyond open source developers. And it's possible the idea of using the "up/down arrows" that everyone is familiar with may still be worthwhile; it's been too long since I've seen the advogato interface to remember if they had that. And finally, a "likeability" metric that was less mathematical and a bit more rough & ready might be a good thing; mathematical constructs are really good at maintaining the properties you design in, but are often extremely fragile. I'd want an algorithm with some knobs I can twist, not a single algorithm. But by all means read the papers in question; why rediscover those things the hard way?
- cwkoss 9y agoI've been thinking about a similar system for a while. I think you can avoid a lot of the success-as-worst-case issues by designing this as a decentralized protocol. Each 'user' is a cryptographic identity: all votes or posts are authenticated by the users signature. When you follow/upvote a user, your clientside software increases that user's weight in your feed. All content on the system is content addressable by hash. All 'likes' are signatures on a content hash. When you connect to another node, you request all recent signatures for people you follow/have upvoted. Clientside software can use various schemes for weighting - totally up to each individual user (ex. how many upvotes is equivalent to following someone? how much time decay in scoring do you want? how deep do you want to traverse followed users' social graph? etc.). Weights for each followed user are multiplied by that user's score for that piece of content, and is then summed across all followed users to create an ordinal list of content - a 'feed'. In this way, if multiple users you follow all like the same piece of content, it would probably be scored higher than a piece of content liked by only one user you follow - so long as your weighting for all those users is equal. Ideally: - Nodes should be able to support multiple users, and host a webserver that provides access to the network to those who are not technically sophisticated enough to host it themselves. - User data should be portable and transferrable to different nodes. - Nodes could implement their own email+forgotpassword userflow to abstract the crypto complexity away from laypeople, though this complicates account transfers and risks account theft by unscrupulous nodes.