I had a nightmare last night, I had to check my email on an M1 MacBook Pro, and the email client on it was just terrible, almost unusable.
Sure. I think search, if it’s going to exist, should be the client’s responsibility. But I also value the readability of the raw twtxt file a lot more than y’all do.
Found a PGP signed twtxt feed. I’ve been thinking about this, I wonder how many clients it breaks. https://domgoergen.com/twtxt/mdom.txt
I want read-only iOS client that just does the simplest model: pull a list of feeds, make a timeline.
@xjix@xj-ix.luxe Saw your oldish note about wanting an offline/async twtxt workflow. Do you have something that works for you? My (very young!) client was designed with that in mind.
I agree clients should present things better (part of why I’m writing one!). But that should be additive. There’s a reason we’re not passing json around.
@prologic@twtxt.net Exactly, but that reduces the argument for URLs in the post. The client should figure out how to search based on the hashtag.
My silly Plan 9 rc twtxt client now has a web page: http://txtpunk.com/tw/index.html
@prologic@twtxt.netYes, I think tags should just be #foo, and let the client figure out searching if it cares.
@movq@www.uninformativ.de No argument that threading is an improvement. But I think (#hash) does that, and I think figuring out how to search should mostly be up to the client.
Hah… my silly twtxt client now has “stories” mode.☺
@prologic@twtxt.net deedum for android.
Kristall for OS X
Elaho for iOS
though I can only vouch for the first two.
what clients support this?
I have a working model for the reader portion of what I want this twtxt client to do.
@ “that’s it. I’m sticking to this txtnish client.” Solid choice.
that’s it. I’m sticking to this txtnish client.
that’s it. I’m finding another twtxt client.
Learn about ghapi, a new third-party Python client for the GitHub API ⌘ https://github.blog/2020-12-18-learn-about-ghapi-a-new-third-party-python-client-for-the-github-api/
Can we not have clients sign their own public keys before listing them on their Pod’s account?
Yeah.. we probably could. when they setup an account they create a master key that signs any subsequent keys. or chain of signatures like keybase does.
Scuttlebutt is an interesting space. I’m using the Patchwork client and so far it works great!
@prologic@twtxt.net (#gqg3gea) ha yeah. COVID makes for a timey-wimey mish-mash. Worked on some WKD and fought with my XMPP client a bit.
@prologic@twtxt.net huh.. true.. the email is md5/sha256 before storing.. if twtxt acted as provider you would store that hash and point the SRV record to the pod. .. to act as a client it would need to store the hash and the server that hosts the image.
Ignite Realtime Blog: Client Control plugin 2.1.6 released ⌘ https://discourse.igniterealtime.org/t/client-control-plugin-2-1-6-released/89159
@xandkar@xandkar.net I’m going to give it a shot. always interested in trying new clients
@prologic@twtxt.net to answer some of your previous questions, i’m using txtnish for my timeline and user controls, and plain twtxt for posting. the alternative to that would be setting up a bunch of shell aliases or small scripts. or making my own client in Go. There’s a thought… ;)
i didn’t think clients would be necessary for something like twtxt and yet here we are
@prologic@twtxt.net I will probably stick with command line client just to make sure it keeps working
A fork of twtxtc, a #twtxt client in C: [[https://github.com/neauoire/twtxtc]] #links
Ignite Realtime Blog: Client Control plugin 2.1.5 released ⌘ https://discourse.igniterealtime.org/t/client-control-plugin-2-1-5-released/88550
Ignite Realtime Blog: JSXC web client now available as a plugin for Openfire! ⌘ https://discourse.igniterealtime.org/t/jsxc-web-client-now-available-as-a-plugin-for-openfire/88467
a microblogging creative coding platform like dwitter, but for sound. users would be encouraged to remix, the output of one persons code would become the input of the new code. only text would be stored on the server, with audio rendered client-side. to save on time, there could be caches of frozen audio for remixes. #halfbakedideas
@hjertnes@hjertnes.social are you using emacs as twtxt client or something? does it render the org markup for you into links?
ANN: Announcing twtxt.net - a Web based twtxt client anf free micro blogging platform ⌘ https://www.prologic.blog/2020/07/20/ann-announcing-twtxtnet.html
Go and xmpp-client ⌘ https://hack.org/mc/blog/xmpp-client.html
mub - a minimalist IRC client in Go ⌘ https://hack.org/mc/blog/mub.html
mu4e — a powerful Emacs mail client ⌘ https://hack.org/mc/blog/mu4e.html
I’m not even using a real client, I made a (poorly written) bash script to write messages to a file and exit if it’s over 140 characters.
Incomplete, not packaged for casual use, and this UI library won’t scroll, but my twtxt client kinda works https://github.com/jcolag/Uxuyu
Disregard this message - I’m testing a GUI client prototype. Hopefully this doesn’t wreck my feed…
I currently have mine set to 5 minutes, but I’ll probably change it to longer than 15 minutes once I’m done playing around with my client.
Due to the same situation, my original twtxt.txt file was also lost, but since I keep various clients, making a new tweet restored part of it.
Due to the same situation, my original twtxt.txt file was also lost, but since I keep various clients, making a new tweet restored part of it.
Testing txtnish on my main laptop, neither the original twtxt client nor the js version worked here.
Testing txtnish on my main laptop, neither the original twtxt client nor the js version worked here.
The nice API makes me wonder how hard it would be to put together a lightweight twtxt desktop client; maybe I’ll look at that next week.
@sarmonsiill@twtxt.ti-l.de : what do you mean ? I’m on ssh using txtnish as client
@kas@enotty.dk [re: gopher client] If you happen to be on Windows, then Gopher Browser for Windows by Matt Owen is pretty nice, otherwise I use Lynx indeed for gopher.
wow, richtig gut, das: https://github.com/trizen/youtube-viewer (yt cli client #perl)
@johanbove@johanbove.info : re other twtxt : I’ll consider it then, but it\’d be on another server, meaning I\’ll use a client on the other server
@von@tilde.town having topic-specific twtxt feeds is not a silly idea. Not sure if the clients allow easy switching though.