Live data from Hacker News

Specifying Spring '83

robinsloan.com

11–13 of 13 posts

Re: Specifying Spring '83

#11
Full CSS and zero javascript is the opposite of what I want.

I love the idea of just seeing everyone's current status, but realistically I want to be able to read people's history as well, otherwise the FOMO will have me checking this thing manually every minute (maybe an effective growth hack, but sounds like it'd end up even worse than twitter if it worked at all).

And realistically an RSS reader with a "tile view" achieves everything that this does.

Re: Specifying Spring '83

#12
Top-level cryptographic identifiers that create an identity separate and distinct from a network location are basically de rigueur for network protocols these days. Almost as if it's a missing layer between IP and TCP? Interesting to see the trend continue in this proposal.

Without an easy way to pay for content online, this will be subject to the same distorting, ad-infiltrating forces as the web in general. Charging even tiny fees for content online resolves a host of problems... while of course creating others.

Re: Specifying Spring '83

#13

The idea is appealing but I feel that there is a conflict between > I want this to work, furthermore, whether those people are sharing a random thought every day, a blog post every week, or an art project every two years. > More importantly, every board holds its place, regardless of when it was last updated. I would not like to stare at the same board for two years between updates, so probably I would end up manuall…

This is like an RSS client where the last update is never expired. I have a few feeds where I manually mark an update as unread so that it keeps popping up.
Post reply on HN