blog.ratterobert.com

Timeline

Recent posts from feeds followed by pftnhr@blog.ratterobert.com

eapl.me (eapl.me)

and going back to a handle you could input in your client to look for the user/file, like @nick@domain.tls I think Webfinger is the way to go. It has enough information to know where to find that nick's URL.

@prologic does that webfinger fork made by darch work OK with yarn as it is now? (I've never used it, so I'm researching about it) https://darch.dk/.well-known/webfinger/

In reply to: #6qodp6q 5 months ago
sorenpeter (darch.dk)

@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;)

In reply to: #6qodp6q 5 months ago
sorenpeter (darch.dk) In reply to: #6qodp6q 6 months ago
sorenpeter (darch.dk)

@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?

In reply to: #6qodp6q 6 months ago
sorenpeter (darch.dk)

@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

In reply to: #6qodp6q 6 months ago
sorenpeter (darch.dk)

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.

In reply to: #6qodp6q 6 months ago
eapl.me (eapl.me)

BTW I'm watching that darch has already worked on that, interesting https://github.com/sorenpeter/timeline/blob/main/_webfinger-endpoint/.well-known/webfinger/index.php

In reply to: #6qodp6q 6 months ago
eapl.me (eapl.me)

after thinking and researching about it, yep, I agree that WebFinger is a good idea.

For example reading here: https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial I wasn't considering some scenarios, like multiple accounts for a single domain (See 'How can I set and manage multiple subdomain handles?' in the link above)

In reply to: #6qodp6q 6 months ago
sorenpeter (darch.dk)

@2024-10-08T19:36:38-07:00 Thanks for the followup. I agrees with most of it - especially:

Please nobody suggest sticking the content type in more metadata. ๐Ÿ™„

Yes, URL can be considered ugly, but they work and are understandable by both humans and machines. And its trivial for any client to hide the URLs used as reference in replies/treading.

Webfinger can be an add-on to help lookup people, and it can be made independent of the nick by just serving the same json regardless of the nick as people do with static sites and a as I implemented it on darch.dk (wf endpoint). Try RANDOMSTRING@darch.dk on http://darch.dk/wf-lookup.php (wf lookup) or RANDOMSTRING@garrido.io on https://webfinger.net

In reply to: #jsj23rq 8 months ago
sorenpeter (darch.dk)

@mckinley Thanks for the feedback.

  1. Yeah I agrees that nick sound not be part of syntax. Any valid URL to a twtxt.txt-file should be enough and is more clear, so it is not confused with a email (one of the the issues with webfinger and fedivese handles)
  2. I think any valid URL would work, since we are not bound to look for exact matches. Accepting both http and https as well as a gemni and gophe could all work as long as the path to the twtxt.txt is the same.
  3. My idea is that you quote the timestamp as it is in the original twtxt.txt that you are referring to, so you can do it by simply copy/pasting. Also what are the change that the same human will make two different posts within the same second?!

Regarding the whole cryptographic keys for identity, to me it seems like an unnecessary layer of complexity. If you move to a new house or city you tell people that you moved - you can do the same in a twtxt.txt. Just post something like "I move to this new URL, please follow me there!" I did that with my feeds at least twice, and you guys still seem to read my posts:)

In reply to: #weadxga 9 months ago
sorenpeter (darch.dk)

I was not suggesting to that everyone need to setup a working webfinger endpoint, but that we take the format of nick+(sub)domain as base for generating the hashed together with the message date and content.

If we omit the protocol prefix from the way we do things now will that not solve most of the problems? In the case of gemini://gemini.ctrl-c.club/~nristen/twtxt.txt they also have a working twtxt.txt at https://ctrl-c.club/~nristen/twtxt.txt ... damn I just notice the gemini. subdomain.

Okay what about defining a prefers protocol as part of the hash schema? so 1: https , 2: http 3: gemini 4: gopher ?

In reply to: #n4omfvq 9 months ago
sorenpeter (darch.dk)

how little data is needed for generating the hashes? Instead of the full URL, can we makedo with just the domain (example.net) so we avoid the conflicts with gemini://, https:// and only http:// (like in my own twtxt.txt) or construct something like like a webfinger id nick@domain (also used by mastodon etc.) from the domain and nick if there, else use domain as nick as well

In reply to: #n4omfvq 9 months ago
sorenpeter (darch.dk)

Thanks @prologic, 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

In reply to: #dzobbnq 1 year ago
sorenpeter (darch.dk)

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

In reply to: #i4nt3ma 1 year ago
sorenpeter (darch.dk)

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

In reply to: #i4nt3ma 1 year ago
sorenpeter (darch.dk)

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

Read replies 1 year ago
sorenpeter (darch.dk)

@shreyan What do you mean when you say federation protocol?

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

In reply to: #7uxy6nq 1 year ago
sorenpeter (darch.dk)

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

In reply to: #mnpnvda 1 year ago
Reply via email