@benk@kwiecien.us I’ve logged in to Monad now (iOS XMPP client) but I’ve gotta be honest: I don’t know if I’ve created a user in the app or logged in to tilde.team 🤔 Do you happen to know how I join a group? And which groups do you recommend?

JMP: Newsletter: Blog, New Registration, New Billing, New App!
Hi everyone!

Welcome to the latest edition of your pseudo-monthly JMP update!

In case it’s been a while since you checked out JMP, here’s a refresher: JMP lets you send and receive text and picture messages (and calls) through a real phone number right from your computer, tablet, phone, or anything else that has a Jabber client. Among other things, JMP has these features: Your phone number on every device; Multiple phone numbers … ⌘ Read more

Ignite Realtime Blog: JSXC Openfire plugin 4.3.1-1 released!
The Ignite Realtime community is happy to announce the immediate availability of version 4.3.1 release 1 of the JSXC plugin for Openfire, our open source real time collaboration server solution! This plugin can be used to conveniently make available the web-based JSXC client (a third-party developed project) to users of Openfire.

The upgrade from 4.3.0 to 4.3.1 brings a small number of changes from the JSXC project whi … ⌘ Read more

Exploring spartan (spartan.mozz.us)! Also trying to make simple client on netcat

I and @r1k@r1k.tilde.institute developing new client for twtxt: https://tildegit.org/g1n/twtxt-c

Fixed another bug in my finger client: rfc1288 says lines have to end with crlf, but I was just sending lf.

Indeed! I think the first “network protocol client” I ever wrote was something that just did the PING/PONG part and passed everything else raw.

Looking at raw IRC traffic streams to debug a client issue and it’s 1997 again.

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.

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

more here

though I can only vouch for the first two.

@prologic@twtxt.net deedum for android.

Kristall for OS X

Elaho for iOS

more here

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/

@prologic@twtxt.net

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.

@prologic@twtxt.net

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 (#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.

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

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

On Wednesday 10.06.2020 the developer of the #XMPP client conversations will talk about implementing audio/video calls with XMPP during the Berlin XMPP meetup (held online with Jitsi-Meet): https://nl.movim.eu/?node/pubsub.movim.eu/berlin-xmpp-meetup/3e091c00-5e20-4727-a61d-c92a247b106e

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

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.

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.

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.

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

@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