# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 38
# self = https://watcher.sour.is/conv/i4o4niq
My feed has now been rotated. The code in jenny is still experimental. I’ll push it once I’ve tested it for a while.
My feed has now been rotated. The code in jenny is still experimental. I’ll push it once I’ve tested it for a while.
My feed has now been rotated. The code in jenny is still experimental. I’ll push it once I’ve tested it for a while.
Also, the GPG signature is gone. Not sure when/if it’ll come back.
Also, the GPG signature is gone. Not sure when/if it’ll come back.
Also, the GPG signature is gone. Not sure when/if it’ll come back.
@movq very nice! That was fast, I don't think @prologic has implemented it on *yarnd* yet. How does one goes to browse the old feed? Say, if someone new to *twtxt* were to follow you now, will they be able to see your previous feed, as well as the current one?
@fastidious They’d have to traverse the prev fields (listed in metadata at the header of the feed). jenny doesn’t do that automatically (yet), but this must be implemented. Otherwise, there’s a risk of missing twts.
@fastidious They’d have to traverse the prev fields (listed in metadata at the header of the feed). jenny doesn’t do that automatically (yet), but this must be implemented. Otherwise, there’s a risk of missing twts.
@fastidious They’d have to traverse the prev fields (listed in metadata at the header of the feed). jenny doesn’t do that automatically (yet), but this must be implemented. Otherwise, there’s a risk of missing twts.
@movq Oh nice! I need to do that, too.
@movq Oh wow, you created quite a lot of small archive feeds! I like the hash being part of the filename, very good idea. Definitely copy that, when I come around to implement it, too.
@lyse My goal was to keep the files at “a few kilobyte”. 100 lines of twts gets you to around ~25 kB, so I went with that.
I’m not 100% sure about those file names. I certainly want to have the date in there. To avoid collisions, I included the hash. Another way to avoid collisions would be to just use the full date or a UNIX timestamp. 🤔
@lyse My goal was to keep the files at “a few kilobyte”. 100 lines of twts gets you to around ~25 kB, so I went with that.
I’m not 100% sure about those file names. I certainly want to have the date in there. To avoid collisions, I included the hash. Another way to avoid collisions would be to just use the full date or a UNIX timestamp. 🤔
@lyse My goal was to keep the files at “a few kilobyte”. 100 lines of twts gets you to around ~25 kB, so I went with that.
I’m not 100% sure about those file names. I certainly want to have the date in there. To avoid collisions, I included the hash. Another way to avoid collisions would be to just use the full date or a UNIX timestamp. 🤔
FYI @fastidious @stackeffect
I pushed the experimental code to jenny’s public repo.
Be aware that it will rotate your files as soon as you run jenny -e or write a new twt. The default number of twts per file is 100.
I hope it’s bug-free, but if you find one, please tell me.
Date-based rotation is not yet implemented and I’m not 100% sure if I’m going to – do we *really* need that? The main goal of this feature is to keep the files *small* and I think that “number of twts” is a good measurement for this. But dates? When you write 100 twts per day, you’ll get huge files again. 🤷
FYI @fastidious @stackeffect
I pushed the experimental code to jenny’s public repo.
Be aware that it will rotate your files as soon as you run jenny -e or write a new twt. The default number of twts per file is 100.
I hope it’s bug-free, but if you find one, please tell me.
Date-based rotation is not yet implemented and I’m not 100% sure if I’m going to – do we *really* need that? The main goal of this feature is to keep the files *small* and I think that “number of twts” is a good measurement for this. But dates? When you write 100 twts per day, you’ll get huge files again. 🤷
FYI @fastidious @stackeffect
I pushed the experimental code to jenny’s public repo.
Be aware that it will rotate your files as soon as you run jenny -e or write a new twt. The default number of twts per file is 100.
I hope it’s bug-free, but if you find one, please tell me.
Date-based rotation is not yet implemented and I’m not 100% sure if I’m going to – do we *really* need that? The main goal of this feature is to keep the files *small* and I think that “number of twts” is a good measurement for this. But dates? When you write 100 twts per day, you’ll get huge files again. 🤷
@movq I just use monotonic increasing integers for rotation
@movq I just use monotonic increasing integers for rotation
@movq I just use max size for rotation 👌
@movq I just use max size for rotation 👌
@movq Great work! I wish we could make all those BIG twtxt writers to use it ;-)
I've a problem with local_twtxt_file not beeing supported any more. Being forced to use twtxt.txt as file name breaks at least my URL.
@movq cool! Will update as soon as I hit home. Is the default number of twts per file before rotation configurable? I would like it bigger, like 1,000, or something like that.
@fastidious Yeah, you can configure it: max_twts_per_rotation in conf.json.
@fastidious Yeah, you can configure it: max_twts_per_rotation in conf.json.
@fastidious Yeah, you can configure it: max_twts_per_rotation in conf.json.
@movq so, local_twtxt_file is deprecated now, and we must use local_twtxt_dir instead, correct?
@fastidious Yeah, but hold your horses. As @stackeffect has pointed out, this is *too* backwards-incompatible (I thought I could get away with it :-)). I’ll have to tweak those settings again to allow for custom filenames (i.e., stackeffect.txt or twt.txt instead of twtxt.txt).
@fastidious Yeah, but hold your horses. As @stackeffect has pointed out, this is *too* backwards-incompatible (I thought I could get away with it :-)). I’ll have to tweak those settings again to allow for custom filenames (i.e., stackeffect.txt or twt.txt instead of twtxt.txt).
@fastidious Yeah, but hold your horses. As @stackeffect has pointed out, this is *too* backwards-incompatible (I thought I could get away with it :-)). I’ll have to tweak those settings again to allow for custom filenames (i.e., stackeffect.txt or twt.txt instead of twtxt.txt).
@movq consider my horses held. 😂