@benk@kwiecien.us I meant literally a few minutes 😄 @prologic@twtxt.net told me he’d just implemented it. Btw, which twtxt client are you using now, Ben?
Ignite Realtime Blog: inVerse plugin for Openfire version 9.0.0.1 released!
The Ignite Realtime community is happy to announce the immediate availability of a an update to the inVerse plugin for Openfire, which makes the Converse.js web client available to your users.
This release updates Converse to version 9.0.0.
Your Openfire instance should automatically display the … ⌘ Read more
DESQview/X : The forgotten mid-1990s OS from the future
X11 client and server. DOS. Windows 3.1. All with preemptive multitasking. ⌘ Read more
@quark@ferengi.one No client, those were created using date -Is and emacs. Off course all is UTF-8 encoded, but now Apache also announces content-type: text/plain; charset=utf-8
JMP: Newsletter: Action required for SIP accounts, new inbound call features, and more!
Hi everyone!
Welcome to the latest edition of your pseudo-monthly https://jmp.chat 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 num … ⌘ Read more
@stackeffect@twtxt.stackeffect.de
I am seeing this characters on your twts: )?â\200¨â\200¨. Which client are you using?
@stigatle@twtxt.net
A twtxt client would be nice! Or a very simple cgi script to print twts to web nicely—not a second Yarn, just something to show twts in a pretty form on the web.
@eldersnake@yarn.andrewjvpowell.com
RSS links are archaic. Clients discover them if properly linked, they do not need to be human visible.
I am noticing that Yarn doesn’t treat “outside” (that is, twts coming from a client other than Yarn) twts hashes right. Two examples:
There are many more, but those two will give you the gist. Yarn links the hash to the poster’s twtxt.txt, so conversation matching will not work.
@lyse@lyse.isobeef.org Unless you are stripping stuff on your twts, there is no much to implement. Things will be bold , italics , underlined , and so on, on a client that can render them. Since jenny uses Mutt, I can use my own regex in it to color them as I like. That’s pretty much it.
GitHub security update: revoking weakly-generated SSH keys
On September 28, 2021, we received notice from the developer Axosoft regarding a vulnerability in a dependency of their popular git GUI client - GitKraken. An underlying issue with a dependency, called `keypair`, resulted in the GitKraken client generating weak SSH keys. ⌘ Read more
@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
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
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.
https://github.com/shaarli/python-shaarli-client cli python shaarli
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