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…

First release candidate of android #XMPP client #Conversations is available and working smooth with my server. Hope it will be released soon. 😃

First impression of the VoIP feature for the #XMPP client #Conversations https://nitter.net/iNPUTmice/status/1250309288506974209

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 TUI #XMPP client #Profanity released 0.8.0 https://profanity-im.github.io/blog/post/release-080/

Since beginning of this month the #XMPP TUI client #profanity started a blog: https://profanity-im.github.io/blog/index.html

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

If someone is using this niche microblog thing twitter: #profanity has a poll what terminal #xmpp client you are using: https://twitter.com/ProfanityIM/status/1207317970667606022

This would allow for clients to only be required to download the latest chunk of messages instead of the entire feed every time.

@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.

Made my own super basic twtxt client in 3 lines of code as a bashrc function. #l33t

@johanbove@johanbove.info a random question from someone who’s used Gopher clients a little bit recently but doesn’t quite understand all the memes: Why are numbered directories like “/0/” common on Gopher holes (but not websites)?

Added clients and articles sections and added domgoergen’s twtxt.txt to https://indieweb.org/twtxt

// todo Create a Kaios client for twtxt

The #XMPP Newsletter is out! Read the latest news from the XMPP/Jabber communities: articles, events, software releases with servers, clients/apps, and services… https://xmpp.org/2019/10/newsletter-01-october/ #social #instantmessaging #chat

@ckipp@chronica.xyz - you’re absolutely right! using the official client now, really misunderstood timestamps yet again.

I totally prefer #XMPP over #IRC. I like it being federated and with #Conversations you have a good mobile client, also you don’t need to setup a bouncer.

Dear lazytwtxt, I just saw someone say hi to a few new people. How can I check the accounts of these new-to-me people so I can figure out whether to add them to my own following list? Their URLs are snipped out in the main client (for good reason).

@metamurks@www.metamurks.org Did you intentionally tweet a lot of one word messages or did your twtxt client fail hard?

Don’t trust the locals: investigating the prevalence of persistent client-side cross-site scripting in the wild | the morning paper https://blog.acolyer.org/2019/04/10/dont-trust-the-locals:-investigating-the-prevalence-of-persistent-client-side-cross-site-scripting-in-the-wild/

for now i’ll just be tweeting from here… my twtxt client got borked on my laptop

So, I’m working on a fediverse client based on https://web.archive.org/web/20190101185657/https://jfm.carcosa.net/blog/computing/usenet/ ; it’s here: https://github.com/enkiv2/misc/blob/master/fern . It is currently read-only, but it has read history.

GitHub - paul90/wiki-client-dat-variant: A dat based variant of the Federated Wiki client https://github.com/paul90/wiki-client-dat-variant

Occasionally the simulators get wistful about when they still did client work because when those wanted last-minute-changes, at least their motives weren’t completely alien

I just recently found an issue with my custom client. It was ignoring microseconds on timestamps. Which meant I was missing some twtxt from people. I got that fixed and I know see all of them.

@mdom@domgoergen.com my own custom client I wrote, I use cron to run the update my timeline every 20 mins. My update process also processes 10 curl calls at time. I did that to save time when I poll everyone.

If your subscribed to 1000 users, you have other problems. None of our clients would handle that gracefully.

New feature for txtnish: After setting add_metadata to 1, txtnish will, uhm, add metadata to your twtfile. Currently i only add followings, client and your gpg fingerprint. See my file for an example.

@sdk@codevoid.de Well I’ve added the special datetime to my kitbashed client. I store the URL it gets but I’m not doing anything with it right now.

@sdk@codevoid.de as for the 140 character limit. I swear I read somewhere that the limit was really more of a suggestion than anything else. I don’t think any of the clients I’ve looked out enforce it. As long as it’s on a single line, no one seems to care too much.

@sdk@codevoid.de A comment might not be in the spec, but I know several of the twtxt files I’ve looked at have them. I know my kit bashed twtxt client ignores those lines and I’m sure other clients do too.

@nblade@nblade.sdf.org: It’s just an idea. Not a clean one thoug, as clients would not know upfront who serves such a fiele and who not. Another idea would ne to mix a number of random followers into the twtxt file, which are updated when a person tweets.

@71m@timmorgan.org If your nick is mentioned with @ (i forgot yesterday, sorry) most clients should highlight it in your timeline if you are following the person mentioning you.

403 You are banned from this site. Please contact via a different client configuration if you believe that this is a mistake. http://freakonomics.com/2013/02/20/how-to-game-a-grading-curve/

@Leo it was a client problem it seems. #txtnish doesn’t crash.

@freemor@freemor.homelinux.net Somehow I don’t see your tweets after 2018-03-16 in the client although i updated your url. @buckket@buckket.org a caching issue maybe?

Uh, thought I made a mistake while adding more functions to my bot but actually it is the default twtxt client crashing when doing a unfollow. :-/

Hot take: the web never ‘belonged to the people’ – the moment a centralized client-server model with hostnames embedded in the addressed was decided upon, the seeds of Facebook & Google were sown.

GitHub - erroneousboat/slack-term: Slack client for your terminal https://github.com/erroneousboat/slack-term

@leveck@leveck.us, I just use the standard client (wrapped in a local script for tweeting).

@leveck@leveck.us, I often use twtxt.xyz but when I am at my laptop at home I use the client as I have my terminator always opened.