/me is finally working on a twtxt client
Man, I love to twtxt with my mail client on the go. :)
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.
@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
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… :)
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 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.
@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?
@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?
Popular, finally. https://github.com/mdom/we-are-twtxt/ – Now exploring client options.
@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.
@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.
@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… :)
@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?
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.
@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
Hello from #txtnish, a new twtxt client with minimal dependencies: posix tools, wget and xargs with -P: https://github.com/mdom/txtnish
@abliss@abliss.keybase.pub I’m still just appending to my twtxt, my client signs it afterwards and uploads the signed version.
@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.
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.
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
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! :)
@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.
This could be a way to discover other twtxt users more easily. Clients could ignore such lines in the timeline if wanted.
This could be a way to discover other twtxt users more easily. Clients could ignore such lines in the timeline if wanted.
@kas@enotty.dk That probably my client at https://github.com/mdom/twtxtpl. It sends a proper user agent string now.
@kas@enotty.dk That probably my client at https://github.com/mdom/twtxtpl. It sends a proper user agent string now.
I’m developing my own implementation of a twtxt client with perl at https://github.com/mdom/twtxtpl
I’m developing my own implementation of a twtxt client with perl at https://github.com/mdom/twtxtpl
@buckket https://matrix.org for more info, https://vector.im/beta for a shiny client. There’s a weechat script too
I have many stories of working with that person. We counted many of the super rich among our clients - super rich but not in money.