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

@tdemin@tdemin.github.io too busy working on a twtxt client to tweet on twtxt

@reednj@twtxt.xyz I think we are all using an client to read our timeline, but i somtimes use http://twtxt.xyz/ to read on the go.

I’d imagine clients wouldn’t implement gpg verification because it’s too much hassle. Most clients probably won’t even implement this… :/

@reednj@twtxt.xyz I think this would be the first time two clients implement the same #metadata format.

Remember to add “AddDefaultCharset utf-8” for your twtxt file if you’re using apache. Otherwise browsers will serve cp1252. The twtxt clients won’t care but maybe someone is watching your file with a browser?

New repository: aquilax/skyscanner-go - SkyScanner API Client

@kas@enotty.dk Doesn’t Scuttlebut also needs a central server if both clients are not on the same network?

@reednj@twtxt.reednj.com Basically there are just more clients… :) And thanks for twtxt.reednj.com, i think we all are still heavily depending on it!

I have the feeling that writing twtxt clients will become my prefered test case to learn new languages… :)

Ups, i did it again! I just started a new twtxt client in c, just for fun and to relearn a little c. https://github.com/mdom/txtio

@kas@enotty.dk my bad - I’ve been developing a twtxt client, hence the frequent requests. I’m switching it over to use a fs cache for testing so I’m not hitting the twtxt files so much.

/me is finally working on a twtxt client

Man, I love to twtxt with my mail client on the go. :)

Additionally, there’s a lot that can be done by a client to reduce the network traffic and UI latency of twtxt without changing the protocol.

@phil@philmcclure.duckdns.org I can’t imagine a simpler time format than rfc3339. I would be fine with just using utc or unix time, but i don’t think most people could write that without a client… :)

@dave@davebucklin.com, @kas@enotty.dk I thought about propsing “There is no maximum length of a message. Clients should show at least 140 characters of a tweet after collapsing the mentions.” Or something like that.

Although that would seperate the network in clients that can or can’t support some protocols. Not to mention if someone would mention me with my ipfs address and other with my http address

I recently tried to write a command like client to GNU social, but after reading the specs on ActivityStreams, Webfinger, PubsubHubbub and Salmon i soon lost interest… :)

@kas@enotty.dk Mhh, only 27% of the feeds i subscribed to, declare an explicit charset in the header. Probably easier to fix that in the clients…

@kas@enotty.dk And to make it even worse, most clients interpret the data as win1252. But does any twtxt client autoconvert to utf8 in case another charset is send? I think it probably okay for every client to assume it’s utf8.

@phil@philmcclure.duckdns.org You mean the leap second in evil.txt? It’s expected to break clients … :) You can just skip lines that you can’t parse. Although it’s a valid date according to rfc3339. Maybe file a bug against coreutils?

@freemor@freemor.homelinux.net Ha! Thorsten Glaser is an old colleague of mine. Shared his office for three days before i switched to another client.

@trevor@destroyed.today Yeah, we just talked this morning about that. There are clients (for example twet) that won’t be able to read signed files.

@tx@0x1A4.1337.cx Reusing twtxt config is probably the easiest way for new clients. Although i’m really happy that i can now use comments in txtnish… :)

Maybe we should just release the spec and not our clients so that any users is required to write a client.

twtxt: The only social network where every new user starts by writing it’s own client.

@tx@0x1A4.1337.cx But be prepared that you terminal is b0rked! In what language are you writing your client?

@tomas@bootlog.org Something is still broken, every clients but curl works for https. The ppl in #curl bet it is some ssl option.

Hello from #txtnish, a new twtxt client with minimal dependencies: posix tools, wget and xargs with -P: https://github.com/mdom/txtnish

Fake email clients
For a few (years?) now, there has been an increase of so called email clients that are not so. I am talking about the “value added email clients” that require a third party server/service to work. Within that category there is Nylas, Polymail, and Sparkmail, to mention a few. Although they bring an array of features not normally found on an email client, they are worthless if the third party company server(s) goes down, … ⌘ Read more

@abliss@abliss.keybase.pub I’m still just appending to my twtxt, my client signs it afterwards and uploads the signed version.

Let’s be honest, it seems to be impossible to use twtxt without adding new stuff to the client. So much fun.

Or do you ask because you want to implement a client or server? I can probably write something up, it’s a very minimal api.

This would be a good use case for metadata. @kas@enotty.dk could ask clients to refetch less, eg with /refetch 10m

@quite@lublin.se Ah sorry, should have checked the commit. #twet is officially the first twtxt client with colors! :)

He once designed entire cathedrals, but his clients ran out of money. Now he specializes in portable microtemples, no bigger than dice.