Yarn

Recent twts in reply to #opev6mq

I’m uncertain I’m looking at the right place, but from how I read it, absolute URLs not only aren’t mandated, they aren’t even a possibility. I’ll open a PR soon™

⤋ Read More

@prologic@twtxt.net @movq@www.uninformativ.de Imagine I want to stop updating my feed on my domain.com by starting a new feed at coolerdomain.net, but point to the previous one in its previous address, for history purposes.

Or maybe I want to stop using this pod because I think I like yours best, or I host my own now… so I want to continue there, pointing to this as my previous one.

⤋ Read More

@marado@twtxt.net There is one problem with this though. We can’t guarantee that the prev_url link is actually valid. I believe we’d run into potential “spoofing” problems by allowing that to happen? 🤔

(side-topic) on the other thing you mentioned about “maybe I don’t like this pod and I like yours better”, that’s a planned feature too (I think it’s in the backlog) whereby if you decide to delete your account on some pod, you’ll get an opportunity to put in a redirect which the pod will honor for some period of time. We want to encourage folks to move around pods (if they want to) and discourage large (high-user count) single pods 😅 (at least this is the greater vision/idea)

⤋ Read More

@prologic@twtxt.net Spoofing is always possible, and always a concern (don’t we “deal” with it already for the url field?).

For the side-question, the feature is nice but depends on availability, and trust, I’m more interested in adversarial interoperability. What if I’m moving from a pod because I dislike their new policies, or new terms of service, their monetization model, etc.? And what guarantees do we have that every pod (or even yarn implementation) will have the redirect option available to its users?

⤋ Read More

@marado@twtxt.net Good points. I think we just have to understand your use-case a bit more… Originally the Archive Ext was developed as a way to let clients fetch older versions of a feed if they wish to (or haven’t seen it before). This is less of an issue with the growing Yarn.social (pods) network itself as they’re “always online” so to speak (even if it’s a single-user pod, which we have many of too).

⤋ Read More

@movq@www.uninformativ.de That’s the scenario, yes. Importing twtxt feeds seems like a good functionality, but it doesn’t totally replace (or exaust) the scenarios in which one could want to have their “prev, static twtxt file” on a different path/subdomain/etc…

⤋ Read More

@prologic@twtxt.net I see reasons for allowing absolute URIs, and see no reason not to.

I suppose I should condense this thread into a write-up proposing the change, explaining why, and proposing client behaviors (“how to deal with a prev pointing to an absolute URI”). But that takes time, and I don’t know when will I reserve some to sit down and actually do the proposal :-)

⤋ Read More

Participate

Login to join in on this yarn.