Just fleshed out the README for timeline at https://github.com/sorenpeter/timeline - Comments/corrections and PRs are welcome:)

@hecanjog@hecanjog.com You need to include the full URL for the audio file for this to work across servers/pods ;)

yes i know @bender@twtxt.net, it’s on my to-do

yes i know @bender@twtxt.net, it’s on my to-do

@bender@twtxt.net you can over at http://darch.dk/timeline/conv/ba3xbfa or by looking at the raw txt https://lyse.isobeef.org/twtxt.txt
I can’t help it that twtxt.net only have temporary caching ¯_(ツ)_/¯

Thanks for your feedback @lyse@lyse.isobeef.org. For some reason i missed it until now. For now I have implemented endpoint discovery for #webmentions as a metadata field in the twtxt.txt like this:
# webmention = http://darch.dk/timeline/webmention

I like the self-shot in the mud: https://lyse.isobeef.org/waldspaziergang-2024-04-07/43.jpg

And now added #filter for replies too:

Image

Added support for #tag clouds and #search to timeline. Based on code from @dfaria.eu@dfaria.eu🙏

Image

Live at: http://darch.dk/timeline/?profile=https://darch.dk/twtxt.txt

Ben Grosser on Degrowth Aesthetics - Aarhus University, Nov 2023 - YouTube

Hi @movq@www.uninformativ.de, is it better now?
I have put in a psudo twthash since I did not archive from a specific date/post, but just what I did not find relevant to keep in my main feed.

you need to send an email @quark@ferengi.one if you want an account. I know that it might not be very profitable. Maybe Odo can disclose it if I give him a new bucket.

@mckinley@twtxt.net I’m over here now. And yes I can send a PR to repo or your are welcome to add it. Credits also to @eapl.me@eapl.me for making a working yarn compatible parser.

What? was? that? Music videos in the 90s was just something else. Especially like the guy in the straitjacket on a pogostick

Same, got one more day at the office, but most folks are already away and the city have shifted from locals to tourists 🌞

It not that easy @xuu@txt.sour.is since I implemented webmentions in a different way that how it have been done in yarnd to work with txt-files. You can find the code in webmention_endpoint.php and new_twt.php at main · sorenpeter/timeline

Thanks @prologic@twtxt.net, I also just manage to get my own version of webmentions working. Please have a read at Webmentions vs. Custom Mentions Spec for Twtxt/Yarn - HedgeDoc and User Lookup for Twtxt/Yarn - Webfinger or Decentralized Identifiers (DIDs) - HedgeDoc for how it sorta works

@eapl.me@eapl.me Take a look at http://darch.dk/timeline/conv/i4nt3ma

@movq@www.uninformativ.de For syncing notes between computers and phones I’ve been very happy with Simple Text - w Dropbox sync for some year, but transitioned to Joplin around new year. Both sync via Dropbox and for Joplin there are also more free options. I guess you could even use something like Syncthing

Also made a webfinger lookup resolver that works with my own webfinger endpoint as well as yarnd servers:
http://darch.dk/wf-lookup.php

Image

Image

Just hacked together this small webfinger endpoint to be used as a companion with timeline: .well-known/webfinger/index.php at main · sorenpeter/timeline

Did another write up on #webfinger and DIDs for twtxt/yarn that you can read and edit/comment in: User lookup for twtxt/yarn - Webfinger or Decentralized Identifiers (DIDs) - HedgeDoc

I’ve gathers my ideas about mentions for twtxt/yarn here: Webmentions vs. custom mentions spec for twtxt/yarn - HedgeDoc
You are welcome to edit and comment in the doc, so our ideas are not fragment into a bunch of treads

So where do we start wring down the specs/protocol for twtxt2/yarn?

@shreyan@twtxt.net What do you mean when you say federation protocol?

• Either use webfinger for identity like mastodon etc. or use ATproto from Bluesky (or both?)

• We can use webmentions or create our own twt-mentions for notifying someones feed (WIP code at: https://github.com/sorenpeter/timeline/tree/webmention/views)

I’m not sure we need much else. I would not even bother with encryption since other platforms does that better, and for me twtxt/yarn/timeline is for making things public

yeah, where and how can we sign up?

Cool news from: https://signal.org/blog/phone-number-privacy-usernames/

It already works: https://webfinger.net/lookup/?resource=xuu%40txt.sour.is
but it not very well described afak

I like this one the most

I’m also more in favor of #reposts being human readable and writable. A client might implement a bottom that posts something simple like: #repost Look at this cool stuff, because bla bla [alt](url)

This will then make it possible to also “repost” stuff from other platforms/protocols.

The reader part of a client, can then render a preview of the link, which we talked about would be a nice (optional) feature to have in yarnd.

What about using the blockquote format with > ?

Snippet from someone else’s post
by: @eapl.me@eapl.me

Would it not also make sense to have the repost be a reply to the original post using the (#twthash), and maybe using a tag like #repost so it eaier to filter them out?

danke schøn, yes the idea was that it should work for all feeds

@johanbove@johanbove.info Sounds interesting. It is only for reading or also posting?

I think is part of the code by @eapl.me@eapl.me that I have based my project on. So try to ask him.

Gracias. Also the git repo now contain code that should actually work

Testing posting for my new http://darch.dk/timeline/

Preparing visuals for #Kune2023 by coding some new #shaders in #GLSL

Image

Image

Image

Image

Image

Image

Image

Image