We:

• Drop # url= from the spec.
  
• We don’t adopt # uuid = – Something @anth@a.9srv.net also mentioned (see below)
  

We instead use the @nick@domain to identify your feed in the first place and use that as the identify when calculating Twt hashes <id> + <timestamp> + <content>. Now in an ideal world I also agree, use WebFinger for this and expect that for the most part you’ll be doing a WebFinger lookup of @user@domain to fetch someone’s feed in the first place.

The only problem with WebFinger is should this be mandated or a recommendation?

Can i change identify without ruining federation? it is important because i can change server and want migrate all my data

Wait, webfinger? Mandate this ruin philosophy “twtxt is just text file”

@doesnm@doesnm.p.psf.lt Like now?

@prologic@twtxt.net How is nick@domain any better than a feed URL? Changing the nick now also breaks threading. That’s even worse than the current approach. Also, there might be multiple feeds with same nicks on one domain, e.g. on free hosters.

@lyse@lyse.isobeef.org Yup you’re right, it’s s terrible idea 💡

Probably the best idea I’ve heard/seen si far is @anth@a.9srv.net’s idea of a feed having a uuid # uuid = (if present) otherwise just falling back to the URL you fetched it from and dropping the idea of a feed # url = entirely.