Searching txt.sour.is

Twts matching #twtxt.
Sort by: Newest, Oldest, Most Relevant

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.

⤋ Read More

@kas@enotty.dk the only thing I can think is that people are finally re-figuring out that static sites are really fast because the content doesn’t need to generated on the fly. I noticed there were a lot of static content generators out there.

⤋ Read More

@sdk@codevoid.de you know the more I think about it, it might make sense to have it the twtxt file. It would just need to be a comment line something like “#follows sdk gopher://codevoid.de/0/tw.txt” on a single line. That way it would be easy to parse out those follows by finding the #follows.

⤋ Read More

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.

⤋ Read More

@benaiah@benaiah.me sounds a lot like why many years ago, I went with Drupal for a simple Blogging site vs Wordpress. WP was easier but Drupal allowed me as an admin to not have any filters. Which allowed me to put raw HTML in the posts to control certian that I was doing at the time

⤋ Read More

@nblade@nblade.sdf.org I could probably put something together, but I went this route originally because existing generators felt like they took too much control from me over the exact output. I want very small, static pages I can throw behind nginx, and I want to know exactly what the contents are. My current mess of spaghetti Racket is getting hairy since I’m halfway through an unfinished rewrite I started a while ago and forgot about, but at least I know exactly what it’s doing.

⤋ Read More

@tdemin@tdemin.github.io good points, though another that I’ve noticed is that it’s difficult to tell who in your network is actually reachable with your tweets. My HTTPS cert went unupdated for a brief while and now I have no idea who is still following me since I got it working again, so it’s difficult to tell where I can really have a conversation. A centralized service can tell who’s following who, but that’s basically impossible in twtxt.

⤋ Read More

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.

⤋ Read More