I wrote it by hand, so it's probably my bad. Still getting familair, also.. it would be nice if I could implement into this client to autocomplete a direct [at] nickname into a twtxt format.

Thats quite good. I'm just thinking of how to keep things simple without needing databases (as a client app), for now it uses cache.. Would be great if a follower would have an AP-layerI over a twtxt and just fetch from the most recent timestamp known in my cache.

Maybe. If, I would miss some content they have, but a lot of it I won't. I am good with Rumble, Bitchute and alternatives. If they do, views will go down too, creators might feel the pain and double up on alternatives.

Well, having added more accounts, I have noticed aggregating (+/- 15min refresh, and caching afterwards) is still a hefty proces. Something I am pondering on how to do that one better.

Ehm.. you are now asking above my paygrade 🤣 I really don't know. Haven't look into webmentions, let alone how it is implemented in Timeline. What happened?

Wouldn't you rather have work and private seperated? Any thought behind this decission? I like tags, like Gmail does it. I still think mail needs a big rethink. It's too prominent in life, to be this archaic.

Some interesting responses, hearing some with (intentional) manual labour involved. I am modifying @sorenpeter Timeline. Still have things I want, and also pondering what would help others.

Hey, @bender I know. Just wondering the kind of apps or software and how you all stay up to date in conversations. Is it through webmentions?

Nice 🤞

Nice. Will this be the place to slowly build a better documentation and explaining some of the considerations for people who use and/or start using twtxt?

We cannot bulletproof it, no matter which solution we use. If somethings changes, most likely something breaks. However a Nick+Timestamp is fairly unique hash, even if someone for whatever reason had the same nick. For display nick@url would make that unique and recognizable again.

🤣 Indeed. It's like using disallow is only pointing them to look for more stuff to index. Those few kB's for a twtxt file, meh.. shouldnt even be a discussion.

I agree. The idea of twtxt is to be an 'open' format or standard. Regarding how often, the TTL could (should?) be honored, but open means open.

Well, as for a new UUID it's a thought to combine the timestamp+username or timestamp+url to create a unique id. In this scenario I think the first would probably be favourable. This way if someone decides to use a different url (most likely they will stick to their nickname) UUID's will still hold up.

Adding to that, we could implement a version variable in the meta, adapt code to either read the old or new format UUID, so older threads won't break.

Thanks as well @prologic 😃

There is a reason P2P was invented. The streaming model will never work, but.. if they want to act like digital kings, then own the pain that comes with it.

Thank you, thank you @sorenpeter 😃

Well I have been working on an update of Timeline, mainly improving speed. Getting a multiple of feeds can really become a big fetch. So I would advocate for ideas to maintain performance.

Regardings your points:

1. Agreed, but at the moment date+txt creates the unique timestamp
2. Preferably newest twt as the last line, will make for more structure.

@prologic @sorenpeter Late to the party, but this could be nice. @bender I agree there needs to be optimizations. Following like 70 or more feeds really puts a strain. I am pondering some ideas.

Looking nice, simpel. We need some better open source analytics tools. I might try it.

On threads? all ten users? :D At least they are agreeing that decentralized is the way to go.

Testing a reply