If we don't keep insisting on simplify and "The beauty of twtxt is, you put one file on your server, done. One.", then people should just use ActivityPub-based software like Mastodon, PixelFed, etc. which are getting a lot of attention and uses migrating to the fediverse from meta/x here in Denmark over the last couple of months.

yes it works now :)

@prologic All the URL are missing the protocol part (https://) and my markdown parser does not know how to handle but I see yarnd does it just fine.

@falsifian it look like your markdown image tags are missing the protocol part (https://) so they don't render at least on my server: https://darch.dk/timeline/conv/3vtnszq

@andros Thank you :-)

@andros screenshots plz :=!

What exact feeds are we talking about that uses spaces instead of tabs or the T's in timestamp?

@lyse that 3th shot of the heron taking off is epic!

@aelaraji I've been noticing the same, so I opened an issue now (https://github.com/sorenpeter/timeline/issues/55) and then we will have to look into it.

@arne nice work with the client. I also see you are using the Yellow CMS for your website🍋

@doesnm.p.psf.lt Cool lets see if this works?!

@prologic I say we should find a way to support mentions with only url, no nick, as per the original spec.

• For <a href="/profile?url=url">@nick</a> we already got support
• For <a href="/profile?url=the posting client should expand it to@<nick url">@nick></a>, if not then the reading client should just render it as @nick with no link.
• For <a href="/profile?url=the sending client should try to expand it to@<nick url">@url></a>, if not then the reading client should try to find or construct a nick base on:
  1. Look in twtxt.txt for a nick =
  2. Use (sub)domain from URL
  3. Use folder or file name from URL

hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt

@doesnm How did you post from IndiePass? Did you add support for twtxt or use some kind of bridge?

I've implemented Use only nick as handle if nick and domain is the same · sorenpeter/timeline@8c12444

See it live at:

• nick = domain: https://darch.dk/timeline/profile?url=https://eapl.me/tw.txt
• nick ≠ domain: https://darch.dk/timeline/profile?url=https://twtxt.net/user/prologic/twtxt.txt
• no nick, use domain: https://darch.dk/timeline/profile?url=https://akkartik.name/twtxt.txt

I'm not sure I like the leading @ thou...

What should the advantage be to nick = _compared to just not defining a nick and let the client use the domain as the handle?

What is not intuitive is that you put something in the nick field that is not to be taken literary. The special meaning of _ is only clean if you read the documentation, compared to having something in nick that makes sense in the current context of the twtxt.txt.

@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as @domain.tld instead of @domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as @domain.tld

Are we talking about profile view heading, heading of posts or inline mentions? In yarnd I recall there is a setting for changing the heading of posts, but not for the two others as of yet. I like the hover option for inline mentions. For the other places some like how yarnd does it in two line or " nick (domain.tld) " could also work.

@eapl.me A way to have a more bluesky'ish handles in twtxt could be to take inspiration from Bridgy Fed and say: If NICK = DOMAIN then only show @DOMAIN So instead of @eapl.me@eapl.me it will just be @eapl.me

And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I've implemented webfinger on my sever for a single user;)

I've started a draft over at: https://git.mills.io/yarnsocial/twtxt.dev/src/branch/main/exts/webfinger.md

@prologic maybe you meant to specify twtxt as a type similar to ActivityPub's application/activity+json in https://webfinger.net/lookup/?resource=sorenpeter@norrebro.space

    {
      "rel": "self",
      "type": "application/activity+json",
      "href": "https://norrebro.space/users/sorenpeter"
    },

Then it would also make sense to define a Link Relations but should that then link to something like https://twtxt.dev/webfinger.html where we can describe the spec?

@prologic Well I just mirrored yarnd's JSON in my webfinger endpoint and lookup, so not much else to do for standardization.

And for people who don't like PHP you can always just go with Added WebFinger support to my email address using one rewrite rule and one static file. or simply putting a static JSON in place for .well-know/webfinger

I like the cleaness and indiewebness of using just domains for handles/shorthands similar to blusky, but the situations with more users on the same domain and that people in the fediverse (threads too?) are already familiar with the syntax speaks for webfinger. And since we already got support for webfinger in both yarnd and timeline it makes sense to stick with it.

@movq Where in firefox can I set custom CSS?

test

@prologic What IRC client is that?

@aelaraji https://github.com/sorenpeter/timeline/commit/555baefcd0e75e6a281472994e8eb7ae9b5d2a1c

@movq I will take that as a compliment

good luck with the doughnut on a stick in a URL

or timeline.txt ;)

test post EDIT

Yes it work: 2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :D

The .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.

Access to those files are closed to the public.

My twtAgent.php was turned off, so try again now. I have uploaded the code to: https://github.com/sorenpeter/twtAgent

What was it suppose to look like? a <detail><summary>-tag maybe?

@eapl.mx Yes, the idea is to add User Agent support to #Timeline. Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request. I'm not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from twtAgent.php to the acctual twtxt.txt Help with making Timeline send proper User Agents to others would be much appreciated:)

@lyse One person had came access it before, but no tried it

@prologic Just that people thought twtxt sounded cool and maybe want to set it up themself

@eapl.mx Super to see you got webmentions working too :)

EDIT: A webmention was send to: https://eapl.mx/timeline/webmention (Status: 202)

@johanbove Thanks, I'm glad you like it.

@movq There was no time for discussion just after the presentation, but I had a chat with some folks later.

Because I don't have capacity on my server to host and stream video and I want others to be able to find the video.

I'm gonna upload my part of the video to youtube and the slides to my website within a day or two. Then you can add it to yarn.social etc.

Live from Piksel Festival in about an hour via: https://www.twitch.tv/pikselfest - Also other presentations stating momentary

I'm giving a shot talk about twtxt/yarn/timeline tommow around noon CET at Piksel Festival in Norway. More info and link for live stream at: https://24.piksel.no (So I will most likely not be joining the call)

@bender The tagline of Timeline is "a single user twtxt/yarn pod" not just a yarn pod. Similar to GNU/Linux. When we came up with the concept of Yarn Social it was a way to rebrand twtxt with the extensions that makes conversations like this possible.

Great to see another user @aelaraji - And I can confirm that my #webmentions works from your server (I know, the formatting is messed up;)

Hey @aelaraji I'm running PHP 8.2 on my server

@movq I knew you would like it;)

@eapl.me here are my replies (somewhat similar to Lyse's and James')

1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

4. Discovery: User-agent for discovery can become better. I'm working on a wrapper script in PHP, so you don't need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that's the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

6. Languages: If the need is big then make a separate feed. I don't mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it's about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

7. Emojis: I'm not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

I'm planning to be there tomorrow (message from yesterday, since we can not all live in the future;)

@movq How hard would it be to implement something like (#<2024-10-25T17:15:50Z https://www.uninformativ.de/twtxt.txt>)in jenny as a replacement for (<a href="?search=twthash" class="tag">#twthash</a>) and have it not care about if is http(s) or a g-protocol?