cross-posted from: https://lemmy.nz/post/825036
What is this called? A banglink?
Anyway, I want to banglink a post.
I know I can banglink a community: !environment@aussie.zone
But what about for this post?
https://aussie.zone/post/132034
I tried several different ways but none worked:
!aussie.zone/post/132034
!aussie.zone/c/environment/post/132034
!environment@aussie.zone/post/132034
!environment/post/132034@aussie.zone
They can try add more syntax. Maybe extend the @instance paradigm to posts too, so /post/123@foo.bar asks for post #123 at foo.bar instead of locally. They can even make it redirect to a local federated post if it’s already federated to local.
@amanaftermidnight
I think we need some way to paste a URL from any instance into a comment that when rendered on any user’s page (whoever is reading it, on any instance) will link to:
The person who is writing the comment should have a low-BS way of indicating this is what they want to do.
The easiest way I think would be to use the whole URL prefixed by something. Not a
!because that already has a different meaning. I was thinking of something like/local/or abbreviated to/l/because special characters aren’t as easily available on all keyboards, they already do other things etc.If I wanted to link to this current thread I would do it like this:
/l/https://kbin.social/m/fediverse@lemmy.world/t/313780/link-for-postsI am thinking that when my kbin instance sees that, it would be triggered to locate “the fediverse url” for the post, which it already has available on anything it displays. In this case it would be
https://lemmy.nz/post/825037. It would remove the kbin.social URL and replace it with the lemmy.nz URL. So then when it comes to rendering on any other instance, that instance will have the “real” location to work with.if interested, here is a thread/xpost which elaborates a bit more on the current situations and both have good comments. I got talked out of the idea of a UUID in favor of something like the above.
Though I think there would be all kinds of complex use cases to work out. Like I don’t only want to be able to do this for URLs that are on kbin.social, so there would be extra work in that case and I don’t know enough (anything) about the internals to suggest how that could happen.
@luthis @instance @willya
The example you show here would give the community 123 on foo.bar. The OP used quite a few common sense examples.
it’s a theoretical example for a mechanism that doesn’t yet exist. you try it now of course it’s not acting like how I proposed.
How you proposed would break the community linking is all I was saying.
I suppose you have never done any server routing coding and has no idea what I’m talking about. I don’t have the gift of eli5-ing this, so I have nothing more to say.