|
|
|
|
|
|
by toyg
3781 days ago
|
|
|
The problem is that if you didn't fetch the file at the right time, you will lose some history after rotation happens. At the very least, it needs a standard way to deal with that (like a mandated date-based URL format?), which has to be specified in the format. Also, no DM and no @-replies. For those, you need a registry of some sort, but decentralized registries enable name-squatting. Before you know it, you have reinvented the WWW, except limited to 140 chars. |
|
|
Very true, and that's a trade-off, not unlike what Twitter does today. In my pseudo-code I didn't make the -n part of the url (it easily could be, but that'd add changes to the client). So I agree with your criticism, but a "since" lookup would be a fairly easy extension of the client (i.e. part of query, so unsupported frontends still work), as the data file already contains date.
> Before you know it, you have reinvented the WWW
Yes. :)