I was bored tonight, so I created a generator of twtxt file using git (https://github.com/tkanos/gitwtxt) :
- Each commit is a message
- Each branch is a thread –> Then I generate a twtxt file out of it.
@email@example.com Oh that’s hilariously funny 😂 And very clever use of Git history 👌
@firstname.lastname@example.org Nice idea, the generator code is missing, though.
Twts in their purest form provide only the mentions mechanism to reply to certain twtxt users. This works well in small, low traffic twtxt communities. However, if there are several ongoing discussions at the same time, a single mention may not be enough for consuming twxt users to clearly identify the exact conversation > this twt is considered part of by its author. So twtxt users quickly started to provide more context in parentheses at the beginning of the twt right after any mentions – the so called subject – in the form of:
@<nick1 url1> @<nick2 url2> (re: topic) That's what I think as well. ^^^^^^^^^^^ traditional subject
The twt subject provides a mechanism to specify references in twt replies and thus group twts into entire conversations.
@email@example.com Haha no Twts ingested that are found to be in the future are just silently dropped on the floor 🤣
@firstname.lastname@example.org Ah, now there it is!