2025-06-07T19:30:09Z (
remote@www.codebuzz.nl )
(#2yr3s6q) Anywhere I can have a look. I do CSS on the daily, and am a big fan of flexbox. It's a real good spec once you use it often and get familiar with it.
2025-06-07T19:27:33Z (
remote@www.codebuzz.nl ) @Codebuzz So ehm, 7 months down the line.. work, life.. etc. I am still looking at twtxt or a form of it. I like the decentralized aspect, a lot! but I also have more things I would like to add. @eapl.me I've messaged you on Mastadon.
2024-11-02T00:44:50Z (
remote@www.codebuzz.nl )
(#dn2zlga) 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.
2024-11-02T00:39:08Z (
remote@www.codebuzz.nl )
(#b6juizq) 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.
2024-10-31T22:47:16Z (
remote@www.codebuzz.nl )
(#w2fylnq) 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.
2024-10-31T22:44:30Z (
remote@www.codebuzz.nl )
(#b6juizq) 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.
2024-10-31T22:40:08Z (
remote@www.codebuzz.nl )
(#dn2zlga) 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?
2024-10-31T22:38:03Z (
remote@www.codebuzz.nl )
(#bbr43aa) 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.
2024-10-31T22:32:46Z (
remote@www.codebuzz.nl )
(#q5rg3ea) 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.
2024-10-30T22:12:24Z (
remote@www.codebuzz.nl )
(#q5rg3ea) 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?
2024-10-30T17:34:57Z (
remote@www.codebuzz.nl )
So I am really curious, now that I am building upon @sorenpeter's Timeline app, how other users write/add their twtxt, and how you follow conversations. Comment svp!
2024-10-28T23:54:34Z (
remote@www.codebuzz.nl )
(#i233nxq) Nice 🤞
2024-10-28T23:13:04Z (
remote@www.codebuzz.nl )
(#i233nxq) 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?
2024-10-28T23:10:11Z (
remote@www.codebuzz.nl )
(#cs3mjwa) 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.
2024-10-28T18:21:05Z (
remote@www.codebuzz.nl )
(#frjxwvq) 🤣 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.
2024-10-27T22:31:03Z (
remote@www.codebuzz.nl )
(#frjxwvq) 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.
2024-10-26T12:44:36Z (
remote@www.codebuzz.nl )
(#pqhbula) 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.
2024-10-25T09:30:34Z (
remote@www.codebuzz.nl )
(#zo4hvla) Thanks as well @prologic 😃
2024-10-24T17:59:54Z (
remote@www.codebuzz.nl )
(#z6ameqa) 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.
2024-10-24T17:52:40Z (
remote@www.codebuzz.nl )
(#zo4hvla) Thank you, thank you @sorenpeter 😃
2024-10-24T17:46:02Z (
remote@www.codebuzz.nl )
(#lnlbnsq) 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.
2024-10-20T17:03:42Z (
remote@www.codebuzz.nl )
I found Timeline by @sorenpeter and I liked it. Decided to change some stuff around. Making some nice progess on my version of Timeline 
2024-10-19T14:01:38Z (
remote@www.codebuzz.nl )
(#lhfziyq) @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.
2024-10-19T13:31:40Z (
remote@www.codebuzz.nl )
(#323k54a) Looking nice, simpel. We need some better open source analytics tools. I might try it.
2024-10-18T00:34:03Z (
remote@www.codebuzz.nl )
I am currently working on a next version of Søren Peter's [Timeline](https://github.com/sorenpeter/timeline). Making it v1.1. Is it 1.1? Anyways I am seeing to where i can take it. Made some nice improvements.
2024-10-18T00:25:57Z (
remote@www.codebuzz.nl ) @bender Lol.
2024-10-12T08:47:18Z (
remote@www.codebuzz.nl )
(#xizvsna) On threads? all ten users? :D At least they are agreeing that decentralized is the way to go.
2024-10-11T22:24:50+02:00 (
remote@www.codebuzz.nl )
(#mz6xhia) Testing a reply
2024-10-11T14:39:52p (
remote@www.codebuzz.nl )
Just testing this new timeline tool.
2024-04-23T20:05:00Z (
remote@www.codebuzz.nl )
Testing posting from http://twtxt.deso.loc/timeline/