[no description] https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/atom?h=other-replaceables 2024-08-31T13:45:41+00:00 2024-08-31T13:45:41+00:00 hodlbod jstaab@protonmail.com 2024-08-31T13:45:41+00:00 urn:sha1:24e97c25390baa7d492d7ef71517e8f14e0e9a65 Clarify what happens when a duplicate subscription is sent, remove CLOSED on duplicate subscription 2024-08-20T15:56:05+00:00 fiatjaf_ fiatjaf@gmail.com 2024-08-20T15:56:05+00:00 urn:sha1:ca3c52e3e74f0a4679f1c6c0d9ac6461ea748d2d 2024-07-19T03:16:45+00:00 Alex Gleason alex@alexgleason.me 2024-07-19T03:16:45+00:00 urn:sha1:9c54549f1842245b842d8a66f3bade744da24189 2024-07-05T16:31:23+00:00 Cody Casterline cody.casterline@gmail.com 2024-07-05T16:31:23+00:00 urn:sha1:8c47577ecb6b3ae6ad840e5b4d187a3f3a6b97c8 * More precisely document since/until bounds. Lower in this document, this is expressed as "since <= created_at <= until". But the English description said that these values had to be "newer than" or "older than". These two were in conflict. I assume the inclusive behavior is the intended one, since that documentation was added later to clarify. This just makes both cases match. * Update 01.md Co-authored-by: Alex Gleason <alex@alexgleason.me> * Update 01.md Co-authored-by: Alex Gleason <alex@alexgleason.me> --------- Co-authored-by: Alex Gleason <alex@alexgleason.me> 2024-06-28T00:00:16+00:00 Jon Staab shtaab@gmail.com 2024-06-28T00:00:16+00:00 urn:sha1:f6b08429a270fbae71f0ae1689a5adf8fa91c543 2024-06-23T00:40:57+00:00 Arjen Stens 18398758+ArjenStens@users.noreply.github.com 2024-06-23T00:40:57+00:00 urn:sha1:4aa18e329a8858ed46727b970c28652c5a0f7b43 * Clarify which kinds have lifetime of 'regular' * Missed space * Document kind 41 as replaceable * Revert "Document kind 41 as replaceable" This reverts commit eead2f5a749cfee6de131944e0e73350759e28b4. 2024-06-17T15:38:57+00:00 fiatjaf fiatjaf@gmail.com 2024-06-17T15:38:57+00:00 urn:sha1:1728f93d17fe399fa6e0911e7bb69d2e159ca572 2024-06-17T15:36:42+00:00 hodlbod jstaab@protonmail.com 2024-06-17T15:36:42+00:00 urn:sha1:747f634004a918d712c32307ac58184fc11bca80 metadata clarity.md 2024-06-16T19:33:49+00:00 Arman The Parman 77603167+ArmanTheParman@users.noreply.github.com 2024-06-16T19:33:49+00:00 urn:sha1:c576737ba42772a561c6ebfd9faf0baae6d19b17 * Update 01.md A few small changes that can potentially help a broader audience (non-developers) follow the meaning. * monospace hex Co-authored-by: Asai Toshiya <to.asai.60@gmail.com> --------- Co-authored-by: fiatjaf_ <fiatjaf@gmail.com> Co-authored-by: Asai Toshiya <to.asai.60@gmail.com> 2024-06-16T09:20:00+00:00 Arman The Parman 77603167+ArmanTheParman@users.noreply.github.com 2024-06-16T09:20:00+00:00 urn:sha1:a52d170c8cc5c99cf658d184922dcfe4e8177660 This is not a correction but a suggestion... When I first read it, it wasn't clear that metadata is specifically for a user and not inclusive of other things (eg not metadata about a photo). Adding this one extra word here would have helped me understand that immediately.