1. You connect to friends and you either manually assign or "grow" a bunch of weights to your amount of trust in them and your interest in various topics they might post.
2. You and your friends make posts and assign "topic" metadata to the posts. The value of the system depends on your friends properly assigning metadata to posts. But it makes it easier to filter out extended families' political shitposting (based on trust and negging untagged posts).
3. Your feed is selected based on the weight of your friendship times the weight you base on the interest of the topic. If your best friend posts something about computers and you have positively weighed that topic it would bubble up.
4. Friends-of-friends can transitively receive a proportion of the trust score you have in your friend. Highly trusted friends will make you trust their friends more.
5. Down-votes and upvotes would train your local agent. They could also be fed back to the originator IF votes were signed by trusted encryption keys to prevent your friend from faking his vote count on the "post".
This decentralizes the network out of FB and democratizes the algorithms / system for what and how you want to receive your information.
1. Everyone makes a website.
2. Those websites submit articles to content indexes.
3. Part of your website hosts your own reader client:
3.a The reader subscribes to a set of indexes.
3.b It can also subscribe to individual feeds.
3.c Your client decides how to mix the feeds into displays, eg, you could have several indexes feed into one "feed" and have all of your family feeds in a second "feed".
4. Most of this is actually done via cloud hosting of managed packages, rented.
There's still many strong factors in favor of centralization, but if it's built around interop, then having a few large providers than mesh together is still an improvement and begins a competition to provide better services.
It's what happened with blogs and RSS anyway.
... aaaaaand, there it goes; the spammers already ruined it ;)
Like they did with email. Then you have companies come with robust AI tech and filter the spam, and also give good recommendations. A few of those companies come to dominate the market
... aaaaaand, there it goes; we're back to the situation we have now with Facebook and Google.
The situation for social networks would be strictly better if you could easily migrate accounts between FB, Google, etc and subscribe to feeds from multiple networks.
The situation you're calling out is exactly the point.
That's also my point.
That sounds pretty malicious for what basically amounts to attempting to serve you the content and ads you want.
Basically, serving you the content and ads you want can turn out to be pretty malicious. By doing so, a big company can manipulate and shape your perception. Year by year, data processing is making big companies ever more potent at doing just this. Is it any wonder that it eventually got to a point where we started seeing problems?
Malicious sounding, indeed.
“Discover” hardly ever means, “check out what’s interesting,” usually it’s “check out this targeted ad”
Its also really good for following journal articles in my field. Pubmed has active search RSS, for instance, and every journal pushes their new articles to RSS.
How does one do that? I'm interested.
Shameless plug: Binaries here: https://gitlab.com/somini/go-hnrss/
I'm surprised so few people here have picked up on the fact that "filter bubble" is a rhetorical trick about as obvious as the "pro-life" and "pro-choice" dichotomy.
People like getting good recommendations, and they'll always like them. "Filter bubbles" are here to stay.
First, we are outsourcing recommendations to profit-driven corporations. At best, the recommendations I want to see will be mixed with the ones advertisers want me to see. Revenue expectations of social media companies currently ensure this is a non-trivial issue with no easy middle ground.
Even assuming the recommendations are reasonably good, you still have the problem that these ML-type recommendations require massive datasets and therefore it naturally gravitates towards a winner-take-all situation. Having one giant borg of a recommendation engine is bad.
We are replacing a rich tapestry of individual word-of-mouth and small-scale communication channels with a massive mono-culture. Scalability is worshipped in tech companies (it's great for getting rich!), but it's not a inherently a good thing. In nature we find diversity trumps scalability, and I feel the same way about culture.
Yep. When it decentralized you can control how strong are the bubble walls and can try different bubbles from time to time.
The thing is though we want to talk about the stories and ask questions. I mean, that’s why we’re all here, right? Comment forums on a million sites don’t work.
In the early days of the web someone had the idea that you should be able to run your own group commentary without the site aurhor’s permission. You’d register for the service and your browser would tell you or show you that there’s a conversation going about this page.
I still feel like we need this.
Most people I add because I meet them in read life. Actually, 100% of the people I add on FB after I've met them in real life.
Maybe if there was a good search and easy add mechanism for people I've met, it would fulfill the discovery aspect. I agree with you, it does feel easier to find people on FB.
I'm not sure how to monetize this, but it would add some discovery to rss.
Make it good enough to pay for.
but instead of following "feeds" you follow people, and it queues up links they've shared on twitter
That last phrase could add a lot of friction.
you could use different clients, some could give you recommendations for events,etc based on your subscriptions if you so choose
That would indeed replace Facebook. However, then you have a chicken and egg problem. Those clients won't be much good unless people provide data by using them, and people won't use them because they don't already have the data to provide good recommendations.
Up until you get to "different clients" you're basically describing classic Google Reader.
It's based on the idea that you'd publish to your personal website either publicly or privately. The private posts can only be read by your friends (who own personal websites themselves and have established a friendship connection using a friend request).
The implementation is just a (not yet standardized) friend ship request REST protocol plus authenticated RSS feeds (using a secret key exchanged by the above process).
Since the whole decentralized social network idea is a chicken-and-egg game, I've constructed the plugin in a way so that it is useful to use by yourself: You can subscribe to RSS feeds, filter feeds with your own rules, and get full-content e-mail notifications for all or selected posts.
The plugin also implements Emoji-Likes on posts and allows recommending posts to your friends. It doesn't have an automatic recommendation engine (yet?).
Actually, there is no need to have this restricted to WordPress since it uses very much established technology, so it could interoperate with any other compatible platform. I just implemented it with WordPress for its ecosystem and that you can use existing mobile apps to read on it and share to it.
Overall the whole endeavor allows you to have your personal social network decentralized, ad- and spam-free since you select who you listen to.
The plugin is already well usable but it only progresses at side-project speed, so help is welcome (not only development work but also trying it out, posting about its features with screenshots/-casts, etc.)!
You can read more about some technical details at https://alexander.kirk.at/2018/11/03/decentralized-social-ne... and take a look at the presentation: https://alexander.kirk.at/2018/11/08/wordpress-meetup-presen...
I have noticed friends reverting back to RSVP e-mails via Paperless Post Flyer. I'm still not sure if one person in this social group is not on Facebook, causing the change, but it has been a welcome adjustment. If Facebook Events can be replaced by an e-mail approach, I don't see why other products can't follow suit.
So like a rule to push it into your newsletter folder?
For a long time I held onto my account, trying to mute anything part of SJW or communist discourse, but to no avail. Twitter shows you stuff you didn't sign up for anyway, I suppose to maximise engagement.
And HN user "jsgo" wrote...
>If it is more difficult than Facebook, it can't hope for being anything more than a niche...
These are the sorts of common sense observations missing from so many "let's replace Facebook/Twitter/Whatever" debates. If we're serious about replacing FB/Snapchat/Twitter/Whatever then we need to consider realistic alternatives. Using the Mastodon-like distributed media and personal website ideas to get rid of Facebook/Twitter is like using the People's Front of Judea and the Judean People's Front to get rid of the Romans. You just have to ignore a lot of reality to assume it would ever work.
We would need some sort of aggregator. Currently, you could call Facebook an aggregator of personal websites. Of course all of the personal websites are also hosted there, but it technically is an aggregator of those webpages. Let's not forget most of the people that I am friends with on Facebook would never be able to create their own personal website without a lot of help which is what makes something like Facebook so convenient and popular.
It could be a protocol, independent of the browser. But the browser could support it inline, so you could just click a button to follow a content stream. It shouldn't be complex, it should be simple. Really simple. Syndication.
Me, I personally treat it like a blog in the sense that I'm there to either "like" it, go past it, or go to the comments section.
Regardless, reproducing Facebook via personal websites would be daunting if not impossible. One, not everyone is going to feel comfortable doing HTML/CSS/JS or even working in a CMS w/ drag-and-drop/WYSIWYG. Two, if I know your name (and if it isn't unique enough, we either share connections or I know some other details about you you've posted), I can search for you on Facebook. How easily can that be created with personal websites when you're also searching against the broader web (good luck searching for your friend Mercedes's personal site. Have a friend named Mike Rowe and you guys joke about how his name is like that one guy with the tv show? Best of luck finding his site too).
And we can argue "but the user can take back control of their data" which on face value is true, the problem is that I think for a lot of people I know on Facebook, they don't care. At least the convenience outweighs the concerns. And that's fine, that's their right. They weighed the pros/cons and found Facebook to have agreeable compromises. As do businesses that sell on Amazon I'm sure.
I do want a solution that gets away from Facebook. The problem is it needs to be something that is easy enough for a non-tech user to manage and consume. If it is more difficult than Facebook, it can't hope for being anything more than a niche.
But that's the point, isn't it? Personal websites isn't what will "solve the customer's problem", persé, but it is what will allow Facebook to no longer be irreplaceable, which is the real reason why people stay on the platform. The question isn't whether personal websites can replace Facebook, but whether personal websites will allow room for a real Facebook competitor (which improves the passive consumption experience) to grow.
No, you're making a common mistake of looking at the surface level of what Facebook shows to users (the so-called "webpage"). Therefore, the seemingly "obvious" solution to beat Facebook is -- Everybody Has Personal Websites.
Since I've seen many smart techies and programmers (e.g. the author of the article we're discussing) make that same claim, I think Mark Zuckerberg has (inadvertently) pulled off the most stunning "Keyser Söze"[0] type of misdirection about the real competitive advantage of Facebook. Programmers are mislead into looking at one thing (e.g. "personal websites") when they really should be looking at something else: The Real Names Lookup Database.
The Real Names Lookup Database is what makes the other features such as "point-to-point messaging", "chat", "calendar events", and finally "personal blog platform" aka "personal websites" -- all work so well with minimum friction.
To put it in more computer science syntax, Facebook has the following SQL table (approximate pseudocode) that's very valuable:
create table real_ids (
real_name,
real_phone_number,
real_email_address,
... other metadata ...
);
Facebook has accumulated approximately ~2 billion rows in that table with those special primary keys. The end users of Facebook also find that table very useful. (My previous comment about this.[1]) Do not get distracted by things like "personal webpages". It's that special SQL table that makes Facebook hard to replace.To continue the Facebook analysis via psuedo SQL, when a user wants to see something relevant from somebody she knows, it's:
SELECT posts FROM real_ids WHERE real_name = "Jane Doe";
Getting relevant calender events & invites is the same idea: SELECT event_invites FROM events,real_ids WHERE real_name = "Jane Doe";
Here's where some observers get sidetracked: Even though the SQL columns "post" and "event_invites" are eventually rendered in HTML, this does not mean that "personal websites of html" is the solution to supplant Facebook. The real issue to analyze is the SQL WHERE clause. Making that WHERE clause work for real names is not trivial to build.Another company that has a similar real_ids database is LinkedIn. But because they cater to professionals, they have mostly white-collar workers looking for jobs; they're missing blue-collar plumbers, or grandparents that are retired, etc. In any case, the same "flawed solution" can be misapplied here: "The solution to replace LinkedIn is to make it easy for people to make personal websites of their résumé and job history."
If you still have doubts whether Facebook's special sauce is the real_names database or if it's the "ease of personal websites", consider what Mark Zuckerberg chooses to spend billions on: Instagram ($1 billion), WhatsApp ($19 billion), and attempt to acquire Snapchat ($3 billion).
Notice that MZ does not bother with acquiring "easy-to-use website builders" such as Wix[2], or Squarespace[3].
What does Instagram/WhatsApp/Snapchat have in common that Wix/Squarespace does not? Those competitors' smartphone apps have a database of real_phone_numbers of their users!
On a related note, thinking that a protocol like ActivityPub can replace Facebook is also misguided analysis. ActivityPub is not a "real names lookup database" so it can't replace the actual thing that makes Facebook useful. Instead of focusing on protocols, think of how to make an alternative database of real_names-lookup that isn't owned by Facebook. Also think of where the db will be physically stored (blockchain is probably not the answer), and how costs for the maintenance of the db will be paid.
Without a viable real_names lookup database, it's pointless for Everybody To Have Personal Websites because there's no easy way for them to connect to other relevant websites to share data. That "connection" is easiest and more scalable when it's based on real names instead of urls.
For a database lookup of domain names to ip addresses, we have a canonical and universal "database": DNS. It's also very useful to have a "real names" reverse-lookup to "web profiles" but right now, the closest analogy we have to that is the realnames database privately owned by Facebook. Facebook has become the biggest and most authoritative "DNS of real people's names".
[0] https://en.wikipedia.org/wiki/Keyser_S%C3%B6ze
Back in the old days I was on IRC. I loved IRC. It was anonymous and everyone could have their own server and you could have individual chat and direct file share instead of broadcasting to everyone. But it's not asynchronous. I would do this thing where I would send my IP and a passcode to my IRC friends and with the IP and credentials they would have access to a specific folder on my home server. I put occasionally a diary or some photos on there and they could leave me messages. (OK it was a very crude solution. I was very young.) I liked it because it did not commit me to having the stuff up all the time but at the same time it wasn't gone forever if I didn't get to it right then.
I realize I am something of an anti-market and nobody would find my dream social network viable. Maybe I should make one for myself. I only have a dozen people I talk to really so there's no "all my friends are here" effect to consider for me.
Is it though? People I know refer to their pages with short urls and nicknames all the time because nobody wants to scroll through bazillion of John Doe profiles in Facebook search.
Similarly, the history of the White Pages and the Yellow Pages is a fascinating read and took decades for those books to be accepted. (Nowhere near as fast as they declined in the internet age.)
Before the standard of "web development" became "learn the terminal, Git and some Linux, unit testing, install and learn Node, learn Docker or some other container, learn ssh, learn a framework and any of several languages that compile to javascript" it really was simple enough that plenty of "normal" people grasped it without any issue.
I can't complain about anyone else's lack of design skills... I once had all of the text on my website bright red Nosferatu on a black background in tables with 3d bevels and a background I swiped from a surreal art site.
But there's no reason some modern, stripped down and ultra-minimalist version of a self-hosted site service couldn't borrow from Facebook's UI design (which, all else considered about the service, obviously works for the general public) and have publishing a "page" be as simple as publishing to their Facebook feed, complete with some non-editable css.
But then that gives you none of the benefits (in my mind) to having your own site (complete control over code and content) as well as none of the benefits of Facebook (integration with your social graph and discoverability) and keeps all of the downsides of a third party host.
I think the other user was right who commented that most Facebook users are content consumers, versus content creators. That is, they browse much more than they post.
It’s part domain registration, web builder (simple website with fees you add content to via text message), part automated dns records, part social media/search engine.
So imagine these personal websites are all connected, one website can follow another, that’s it. You own the content, traffic, ad revenue. You could search content across these distributed websites with the tomorrowbook search engine, you could use tomorrowbook to register a domain (built in dns/website for the nontechnical) or use your own registrar and embed the tomorrowbook feed into your site.
Original post: https://news.ycombinator.com/item?id=11473190
But yes that seems to allow websites to link to one another.
It's funny when people paint such wide strokes for 2 billion people. I would assume people use Facebook for literally hundreds if not thousands(if you can imagine) of use cases.
Probably one of the most complex consumer products ever made from that perspective. I don't think it's useful to reduce Facebook to something as simple as "most people do X on Facebook".
For instance, Facebook in India has nearly 300 million users. They all use Facebook the same way as the 215 million in the United States?
The only people that know how Facebook is used by people is Facebook.
search engines solve that somewhat ... but you could have a directory that points to the correct address (a bit like a web directory or a phone book)... maybe the government could even host that...
Is that true? I would have thought it's mostly used for chatting with people they know, or commenting on things people have shared. But I'm just guessing.
For many it's become more of an address book
Maybe where you would sign into your own site and it would have polled posts from all the sites you follow (probably with rss) into a single feed. Your site IP is your identity, so commenting etc would be done as your site e.g., `MentallyRetired.com says: Hey these are cool!`
I dont know, just shooting from the hip, but it seems a lot of these technologies are possible. I remember signing into places with my website.
But it needs to be EASY. As easy as Facebook. And backwards compatible to avoid breakage.
Very true and Twitter is better for this in general. I keep a Twitter feed running at all times on 2nd monitor.
EDIT: Specifing the claim
> Recommending "personal websites" is talking about a solution to a problem that most of the billion users don't have.
I thinks this is mostly a valid argument. The burden of proof for whether the problem exists is on the person proposing the solution; Solutions require action, and the side that requires action needs proof.
I do think the claim that “most people use facebook like an rss feed” needs some data to back it up though. I personally use it that way, but that is andecdotal and I also have many friends who use facebook to promote their life, which is more along the lines of a personal website.
EDIT: Spelling
Plus asking for data about a long post without referencing which part you even want data on is unconstructive.
Two wrongs don't make a right, and how do you know to what standard the parent poster holds the author? ¯\_(ツ)_/¯
Plus asking for data about a long post without referencing which part you even want data on is unconstructive.
There was one claim made in the five sentence GP post.
Where does the author get that idea? The majority of Facebook's 2 billion users do not post to their profile feed. Instead, the FB account is mostly used as a way to passively receive content. Some of the content is from family and friends, and some is from media outlets (NYTimes, etc).
Recommending "personal websites" is talking about a solution to a problem that most of the billion users don't have.
The way most people use Facebook is more of an RSS feed rather than a 1999 Geocities personal website. (But that doesn't mean RSS readers can replace Facebook because that technology is missing a "real names" reverse directory lookup database.)