twt reply hash text...? π€
twt reply hash text...? π€
> π¦ A command-line utility (non-daemon) written in Go for creating Linux containers and sandboxing processes.
> π¦ A command-line utility (non-daemon) written in Go for creating Linux containers and sandboxing processes.
> Storage is cheap. Data is invaluable.
And:
> TIme is limited and precious.
Maybe? π€
> Storage is cheap. Data is invaluable.
And:
> TIme is limited and precious.
Maybe? π€
yarnd does make is that the hash is a valid Twt. This is part of the Twt Hash Extension where Twts are content addressable by the hashes we defined in the spec π
yarnd does make is that the hash is a valid Twt. This is part of the Twt Hash Extension where Twts are content addressable by the hashes we defined in the spec π
yarnd implement the Twt Subject extension which states:> 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.
yarnd implement the Twt Subject extension which states:> 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.
Finally fixed a long-standing bug in a project @markwylde and I started over a year ago π₯³ The basic idea was (and still is) to provide the only Container as a Service (CaaS) π Now that this bug has been squished (_might need to tidy things up_) -- Might be able to continue with this idea and maybe start beta testing it with some interested folks? π€
Finally fixed a long-standing bug in a project @markwylde and I started over a year ago π₯³ The basic idea was (and still is) to provide the only Container as a Service (CaaS) π Now that this bug has been squished (_might need to tidy things up_) -- Might be able to continue with this idea and maybe start beta testing it with some interested folks? π€
hlive: HLive is a server-side WebSocket based dynamic template-less view layer for Go.
Search Β· github.com/SamHennessy/hlive SamHennessy/hlive: HLive is a server-side WebSocket based dynamic template-less view layer for Go.
hlive: HLive is a server-side WebSocket based dynamic template-less view layer for Go.
* 93f87d8c 2022-09-17 | Fix preflight checks to support Go 1.19 (HEAD -> main, origin/main) [James Mills]
* 93f87d8c 2022-09-17 | Fix preflight checks to support Go 1.19 (HEAD -> main, origin/main) [James Mills]
main? Can you tell me what commit you're on?... Oh wait ... This is fixed in the branch I'm working on right now π Let me quickly cherry-pick that change out!
main? Can you tell me what commit you're on?... Oh wait ... This is fixed in the branch I'm working on right now π Let me quickly cherry-pick that change out!