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

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

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

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

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

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.

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/

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

@freemor@freemor.homelinux.net You wouldn’t even need to add the recipient in the tweet, clients could just try to decrypt anything.

Well after 4 hours of work, I finally think I solved all my client side calculation issues. I have no desire to screw with it again

Work Project Note : Trying to redo server side logic on the client side sucks.

Re: support for other protocols, it seems like twtxt would be pretty easily adapted to work over the p2p file network DAT, though it’d need client support for DAT or some way to follow people via files and sync in the background, which might be simpler for clients to support but would still require changes to most clients.

@tfurrows@grex.org It is neat. Although it did require to recode a little bit of my kitbashed client LOL

@freemor@freemor.homelinux.net I’m cheating geting @mekon@sdf.org file by using my own kitbashed php CLI client I am playing around with

Had to update my client to use CURL so I could get @mekon@sdf.org twtxt file via gopher

@tfurrows@grex.org just saw your one reply. Yes the client does have a way to sync with the we_are_twtxt list. So far the biggest issue with the PHP CLI client is that it takes a long time to poll all the sites

@kas@enotty.dk I’m not currently using a handrolled client, but I’ve started a couple.

@mdom@domgoergen.com I am playing with the txtnish client, all the systems I have available are running an old version of Python

@nblade@nblade.sdf.org What client are you using? Your mentions are somehow broken?

I think this week I’ll look at a bare bone PHP CLI for a twtxt client. Just for fun mind you

@tfurrows@grex.org It’s not a hard limit, most alternative clients do not care about the amount of characters you’re posting. As long as you don’t write a novel and it still fits on a line… :)

@freemor@freemor.homelinux.net @kas@enotty.dk #twtxt’s quietness is actually something I enjoy about it. I care a lot more about signal-to-noise ratio than I care about the regular activity. It’s also a really fun thing to write clients for to play around with new libraries or languages.