This reminds me of this video: The Biggest Gap in Science: Complexity
However you might end up with more questions (complexity?) than answers (simplicity?)
s/(www\.)?youtube.com\/watch?v=([^?]+)/tubeproxy.mills.io/play/\1
for example? 🤔
Have not tried any of them, but some of these seem to fit the bill:
ok != perfect
It looks okay on my timeline: http://darch.dk/timeline/conv/omu7e4q
@prologic@twtxt.net The old options are still valid, so “Show latest post per feed” should just be added as a 3th.
I think it is a good addition. Similar to how the Fraidycat RSS reader works. Fraidyc.at also support twtxt, but have not seen any updates since 2021…
Here now too
echo chambers?
# follow = dbucklin@www.davebucklin.com https://www.davebucklin.com/twtxt.txt?nick=dbucklin
I fixed it by adding (?<!\S)
to the regex filter. But what is going on with the ?nick=dbucklin
anyhow?
@Prologic@twtxt.net can you pleas fix this line in your twtxt.txt:
# follow = dbucklin@www.davebucklin.com https://www.davebucklin.com/twtxt.txt?nick=dbucklin
It is cause this weird effect on my timeline, where you are now called dbucklin
http://darch.dk/timeline/?profile=https://twtxt.net/user/prologic/twtxt.txt
@movq@www.uninformativ.de Maybe something for you: 7.css - A CSS framework for recreating Windows 7 UI
@prologic@twtxt.net Haha, that sh!t is pure (net)art!
@dfaria@twtxt.net the difference is that these other servers does not post several times a day with content that are not informative/interesting to people outside your academic context, which can be perceived as noise.
What @prologic@twtxt.net have done is what I would call curation of the service he offers to the world for free (as in beer). It’s no one right to have their posts syndicated to the frontpage of twtxt.net, it’s simply a gift he gives to the world and he is free (as in speak) to wrap is anyway he sees fit.
@dfaria.eu@dfaria.eu I hope you stay around 🌞
@prologic@twtxt.net and @bender@twtxt.net for a start a single user twtxt/yarn pod could look like this 😉
I just “published” a #draft on my blog about “How I’ve implemented #webmentions for twtxt” (http://darch.dk/mentions-twtxt), so I wanted to know from you guys if you see yourself doing a similar thing with yarnd
@prologic@twtxt.net or others with custom setups?
The wording can be more subtle like “This feed have not seen much activity within the last year” and maybe adding a UI like I did in timeline showing time ago for all feeds
I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.
The “not receiving replies” could partly be fixed by implementing a working webmentions for twtxt.txt
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:
Added support for #tag clouds and #search to timeline. Based on code from @dfaria.eu@dfaria.eu🙏
Live at: http://darch.dk/timeline/?profile=https://darch.dk/twtxt.txt
prev
field in your feed’s headers is invalid. 😅
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 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
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/
@xuu@txt.sour.is
=> https://text.sour.is/user/xuu/twtxt.txt
It already works: https://webfinger.net/lookup/?resource=xuu%40txt.sour.is
but it not very well described afak
>
?
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.