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.
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.
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.
@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
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?
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.
@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.
@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
Added clients and articles sections and added domgoergen’s twtxt.txt to https://indieweb.org/twtxt
// todo Create a Kaios client for twtxt
@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/
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.
@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.
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
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
I think this week I’ll look at a bare bone PHP CLI for a twtxt client. Just for fun mind you
@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
@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
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.
Popular, finally. https://github.com/mdom/we-are-twtxt/ – Now exploring client options.