- cross-posted to:
- privacy@lemmy.ml
- cross-posted to:
- privacy@lemmy.ml
cross-posted from: https://discuss.tchncs.de/post/1053698
https://github.com/RupertBenWiser/wei-wpt-other
https://github.com/RupertBenWiser/wei-wpt
these showed up after Jul 21 per GitHub “contribution activity” but are retroactively dated to 13 - they were probably private before that.
We may not see that full implementation is already worked on.
add to that - just from https://discuss.tchncs.de/post/1051714
https://github.com/chromium/chromium/commit/6f47a22906b2899412e79a2727355efa9cc8f5bd
Please comment any information under this post and create cross-links at any possible posts - to create comprehensible information source.
I don’t see where to comment there, but I found this: https://github.com/chromium/chromium/pull/187
The issue with your cross-post is that it links away from the viewer’s local instance. Somehow, you’ve managed to link two posts in the same community together (/c/Privacy@lemmy.ml), where the only difference in this post is that you have the discuss.tchncs.de link. It would have been better if you managed to cross-post the other post from discuss.tchncs.de, such that users can get an instance agnostic link to the other post.
Although really that probably isn’t your fault. They really need to make instance agnostic post and comment links a thing. Let the host instance decide the number, then the link can be
https://yourinstance/post/<number>@theirinstance
. Rather than every instance assigning a different number to posts and comments independently.Edit: wait a minute, your discuss.tchncs.de link is just the same lemmy.ml link, but in a different instance. That’s not much good, you should just stick with the lemmy.ml post and let others view it from their own instance. For me, your post is https://lemm.ee/post/2087164, and there will be a different link for every instance that’s federated with the community.
Like I say, they really need to make post links agnostic.