(#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(TM)

(#opev6mq) @marado Exampje GitHub Pages?

(#opev6mq) @marado Please if you could do so that would be great 🙇‍♀️

(#opev6mq) @marado So the point is: When you move from one pod to another, you start *afresh* on that new pod? You don’t take your current feed and the archived feeds with you? Example: - 2022-01-01: Starts twting on foopod.example.com - 2022-02-01: Moves to barpod.example.com, puts `prev = $hash foopod.example.com/twtxt-old-$hash.txt` in header of new feed at barpod; actual feed at barpod.example.com starts empty Is that it? 🤔 (If yes, then this raises another question for me: What if I want to move from one pod to another and want to keep my entire feed? That’s would I, personally, would want. Like, when I open an account on a Yarn pod, there could be an “import this twtxt file” feature – dunno if that’s already possible.)

@movq (#opev6mq) 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...

@prologic (#opev6mq) I think so, yes. More generically, places were you have no control over the webserver (hosting services via ssh/ftp without htaccess support is another example).

@prologic (#opev6mq) 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?

@movq (#opev6mq) That would be a scenario, yes.

@movq @prologic (#f45oiqq) Redirects will work for on feed removals, *if* the poderator is interested in providing them - it depends on its benevolence and good will. In any case, removals must be implemented somehow (at least in pods operating under EU law), so there's no downside in implementing it with a redirect option. Regarding `# prev`, maybe it is best to recover the old thread (which I think was (#opev6mq)).

(#opev6mq) @marado I _could_ have sworn we discussed the spec mandating absolute uris no? cc @lyse and @movq for comment. if this is not the case, we should re-discuss and amend the spec. Otherwise, put up a PR and let's discuss it right there in code 👌