Conversation:
Notices
-
........yeah. If it wouldn't mess up all the #StatusNet instances out there that will never upgrade (and expect the insecure behaviour).
-
That'd be solved using the extensibility of XML, rather than versioning :]
One feed can support all versions at the same time.
-
Assuming the notice is accessible yes. Might be so that the original is gone and people are repeating because the notice should be shared. (consider that it might have been deleted from its source or is unaccessible because of censorship, and we still want a reliable distribution which we can validate).
-
Afaik the link is already transmitted, together with a URI. ;)
But there are subtle issues with this that need careful thought so as not to break either StatusNet, PuSH or generic third party implementation support.
-
...that the implementation from #StatusNet simply takes the attached repeat without retrieving or verifying its authenticity in any way.
-
Except that it's on the web. HTTP sucks pretty hard. (no requirement on HTTPS in !ostatus :P)
-
Doable? Yes. When anyone feels they have time for it? No idea. :)
But given the newfound popularity (and since repeats are now federated again like that, they weren't for a while), it's definitely higher in my priority list. I do a bunch of quicker, relatively necessary, fixes first though.
MMN-o ✅⃠
All Hacker Poesy content and data are available under the