Instead of/in addition to cleaning dead links, this would benefit from integrated link archival via third parties or a first party integration, self-hosted solution, and/or bring-your-own API key to third party archives like Wayback Machine, archive.is, or others.
1. When I delete a link from one of my snacks it opens a new tab with a 404. Is that expected?
2. There seems to be no persistent identifier for a snack - if I change the title, the URL changes and then the previous URL is dead. While it's nice to have a human readable URL is that actually necessary, or could you use a string? Maybe it's a SEO thing though, in which case maybe the title and the URL should be uncoupled so that changing the title doesn't break the link to the snack.
3. It would be nice to be able to add an image to the snack header, as well as the emoji. Maybe using unsplash or something. And maybe some colour styling.
Loved del.icio.us. This is a pet peeve of mine, that proper tagging (with AND & filtering properly implemented) is rare in software. Tagging peaked with del.icio.us.
I've had a similar idea kicking around for some time now. This might be it.
One of the core concepts I wanted was to see how my list E.g. "Top 10 Best burger joints in <city>" or "Top 5 white wines for a Summers evening" compared to others similar lists. I've never been able to land on how to best implement something like this, without requiring some kind of strict tagging by the user to enable like for like comparisons and accurate rankings.
I wanted to call it "Social List" / "Socialist" :-)
Love how dead simple and to the point this is. Great job. Put some stuff about it in my newsletter so you might see some traffic from a newsletter called The Teardown (on Substack)
Starting the page with the sign up button before telling me what the page is seems like a mistake. I almost closed the page at first (it’s not even obvious that you can scroll, it looks like a full page popup).
You should show example screenshots of actual useful lists people could share. The site is currently too focused on “what” you can do (features and capabilities), and not enough focused on “why” (practical real world use cases).
