With Postmarks, social bookmarking is back -- but this time it's built on the fediverse | TechCrunch
With Postmarks, social bookmarking is back -- but this time it's built on the fediverse | TechCrunch
The successor to Web 2.0 bookmarking site del.icio.us is here, but this time, it's built for the open web and the fediverse -- the decentralized
You're viewing a single thread.
Good news. I was thinking about how annoying it was that del.icio.us got bought up and shuttered the other day. There have been plenty of replacements, a lot of which faded away, but I think this is the first federated one. Will we see people spin up open instances for this?
At the moment it is explicitly designed as a single-user implementation, although I'm sure it could be pivoted to become multiuser. I've simply set up my own on Glitch and it is working great! -> https://pipesmarks.glitch.me/
And it looks like I have it up and running:
Thanks for the information. I've not used Glitch before but will give it a go.
It's just that I thought it would work well with instances based around subjects like books or games - you would then have a "all" feed that would be relevant as well as "subscribed" one for a more curated feed.
Removed the other comment.
Because I think I get the point now. I actually never heard of these services before. And didn’t realize people liked to share their “saves/bookmarks”. Or have people actively follow what they are bookmarking.
It’s super interesting.
It is - I was a big user of del.icio.us and followed a number of people on there, sharing links that would send us off down rabbit holes and the like.
I tend to only share select news and interesting items on here, longer articles might go over to Pocket for a future read when I have time and snippets, articles, images and the like can get shoved over to OneNote (and yes, I am working on replacing the proprietary services with FOSS, preferably Fediverse, ones). Personal links get shared to relevant people on WhatsApp and/or get stashed away in the browser bookmarks but there are still other links that could be shared elsewhere. The tagging system also means that I can resurface older links shared on here (I managed to pluck out a few that weren't that old but I was in danger of losing track of them), so I see Postmarks as being a bare bones handy store for pretty much all the links that are fit to share, especially if I may need to find them again in the future.
I've had an idea, that I could easily pivot to this and become a FOSS solution. But, I wonder if it actually solves a problem. Essentially, I wanted my lemmy instance to allow sign-ups. But, the posts and channels were auto-generated. So when you log into the app or sign-up it creates a community in the instance along with it. (loom.nyc/c/pexavc) and then all the posts are automatically generated from the posts you save anywhere in the fediverse. (The app supports lemmy and mastodon for now). But, this would also allow all your bookmarks to essentially "federate".
Edit: Tbh, it sounds like a more "silent" cross-posting
As you can follow anyone on almost any Fediverse service, is there a need for this? It would render the instance's "All" pretty much unusable.
I could see it working if you had a one-person instance or an instance devoted to a single celebrity. There you'd basically have one such community channeling all their social media in.
What I could see a potential for is FediFeed where you could turn any collection of communities or individuals into a single feed, possibly even RSS. Although I presume most Fediverse services have or could be made to generate an RSS feed anyway.
Ah yes! I almost do that already. With RSS as well. So you can combine communities and RSS Feeds, not mastodon users yet though. It's kind of fun standardizing all the different ActivityPub implementations into a single data model. Mastodon timelines or users are essentially whole communities.
To be honest, building a web-version of that pipeline as a NPM package might be helpful for others, piping in all the different types of fediverse content into a single stream.
Permanently Deleted