# 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 29
# self = https://watcher.sour.is/conv/nj3rtxa
@sorenpeter As @movq correctly points out, the timestamp is a RFC 3339 formatted datetime. The only valid way to parse timestamps and append them to a feed is RFC 3339 😀 -- Doing anything else otherwise would be both invalid, weird and well just not following a standard (_what's a standard for?!_) 🤣
@sorenpeter As @movq correctly points out, the timestamp is a RFC 3339 formatted datetime. The only valid way to parse timestamps and append them to a feed is RFC 3339 😀 -- Doing anything else otherwise would be both invalid, weird and well just not following a standard (_what's a standard for?!_) 🤣
@prologic @sorenpeter @movq yeah i know that there are standard for a reason. But you can't have : in filenames and I'm building an instagram-ish view for twtxt when i want an easy way to link back to the original post.
Why can't you have : in file names? What file system is this?
Why can't you have : in file names? What file system is this?
@anth Sounds like a Windows to me. ;-)
@anth macos and windows does not seem to like it
macOS doesn't care, at least on apfs; just tested. How are you hitting this?
macOS doesn't care, at least on apfs; just tested. How are you hitting this?
@anth just tried on my main disk in my macbook. did not work. I'm more concerned with not confusing the end user and securing cross platform complability that what might be allowed in some OSs.
@anth I would like to prefix uploaded media files via my twtxt webclient with the datetime so the can easly be viewed in a chronological gallery and linking back the original yet with just a simple grep
Entirely sensible, & no reason for file storage to match the wire format. I'm just really curious what's going on on macOS! I can test on hfs+ later.
Entirely sensible, & no reason for file storage to match the wire format. I'm just really curious what's going on on macOS! I can test on hfs+ later.
@darch I don’t understand what problem you’re trying to solve though 🤔
@darch I don’t understand what problem you’re trying to solve though 🤔
@darch Just use a UNIX time stamp 😁
@darch Just use a UNIX time stamp 😁
Will try to explain at a later time. but unix time might be a solution.
@darch did you forget to publish this blog entry? 🤔
@darch did you forget to publish this blog entry? 🤔
Yup... I should be public now
@darch You could use the basic format of ISO 8601, which is compact and doesn't use special characters except in the sign of the numeric timezone offset (plus and hyphen characters). But you could convert it into UTC instead. The timestamp of this twt in ISO 8601 basic format would be 20210616T172000+0200, in the extend format it matches RFC 3339: 2021-06-16T17:20:00+02:00. Converted to UTC in basic format: 20210616T152000Z
