@dce@hashnix.club Twet is a far better command line client. Yea 👌
Apparently twtxt wasn’t the right client to use. twet seems to be alright, though.
@bender@twtxt.net You said:
as long as those working on clients can reach an agreement on how to move forward. That has proven, though, to be a pickle in the past.
I think this is because we probably need to start thinking about three different aspects to the ecosystem and document them out:
- Specifications (as they are now)
- Server recommendations (e.g: Timeline, yarnd, etc)
- Client recommendations (e.g: jenny, tt, tt2, twet, etc)
My client is twet which i grabbed at https://github.com/jdtron/twet
Hm, seems i breaking something in twet code for handling mentions
this looks strange in twet xD: blue highlight of @2024-10-09T08:11:00Z(prologic)
should i delete gemini support from twet? iirc in twtxt v2 it starts prohibited. And all of my fields are https
twt
probably isn't the best client I'm afraid. It doesn't really cache twts by their key (hash) to display threads properly. Jenny however does 👌
@doesnm@doesnm.p.psf.lt Sorry I meant twet
🤦♂️
twt
probably isn't the best client I'm afraid. It doesn't really cache twts by their key (hash) to display threads properly. Jenny however does 👌
It has twts cache which used if timeline is set to jew. Maybe i.should fork twet to make wishes like newlines (i see two squares), showing conversations, showing twts if not found in cache and parsing medata to configure url, nick and followers (currenly it duplicated in config and twtxt file)
twet display twts in raw format with some formatting (sadly no newlines). And for reply messages i just seen (#hash). But which text hidden on hash? currenly im open twtxt.net/twt/hash to see this
Back to twtxt from the cli with twet https://github.com/jdtron/twet
Back to twtxt from the cli with twet https://github.com/jdtron/twet
@trevor@destroyed.today Yeah, we just talked this morning about that. There are clients (for example twet) that won’t be able to read signed files.
@trevor@destroyed.today Yeah, we just talked this morning about that. There are clients (for example twet) that won’t be able to read signed files.
@krt@krt.marmaro.de You can use more than 140 characters. It seems twtxt does not limit the number of characters to 140. Neither does txtnix. Twet?
@krt@krt.marmaro.de You can use more than 140 characters. It seems twtxt does not limit the number of characters to 140. Neither does txtnix. Twet?
@kas@enotty.dk You mean, you want to link a url in one of your twets and then send a webmention?
@kas@enotty.dk You mean, you want to link a url in one of your twets and then send a webmention?
@quite@lublin.se Heh, I like twet twet! #twet
@quite@lublin.se Heh, I like twet twet! #twet
@quite@lublin.se Ah sorry, should have checked the commit. #twet is officially the first twtxt client with colors! :)
@quite@lublin.se Ah sorry, should have checked the commit. #twet is officially the first twtxt client with colors! :)
@quite@lublin.se Woah, we both implemented ANSI color support for #twet and #txtnix at the same time!
@quite@lublin.se Woah, we both implemented ANSI color support for #twet and #txtnix at the same time!