Asklemmy

43909 readers

1297 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago

MODERATORS

Crossposting etiquette when you're not the OP (lemm.ee)

submitted 1 year ago by OldFartPhil@lemm.ee to c/asklemmy@lemmy.ml

22 comments fedilink hide all child comments

I occasionally come across content in my feed that I think would be of interest to one of the small communities that I participate in. Think photo or article, not something personal. Is it appropriate for me to crosspost the content? Without asking the OP? What about if I ask but the OP never responds?

Thanks in advance for your thoughts.

you are viewing a single comment's thread
view the rest of the comments

[–] JackbyDev@programming.dev 7 points 1 year ago* (last edited 1 year ago)

No, it's not a federation issue. What we need is some syntax to link to posts/comments in an instance agnostic way. When you click something like !chat@beehaw.org your UI will take you to your instance's version of it. Clicking a URL will take you to that URL always. As expected, post A in community X hosted on instance blah will have a different URL than post A in community X viewed from instance foo. You can share a URL to the actual post on its actual home instance or you could share a URL to your instance's view of the post. That second one is useful to you and members of your instance but not members from any other instance.

Short of your UI intercepting and redirecting URLs (a very bad thing to do in my opinion, links should go where they say they go without interference) this cannot be solved with URLs. That's why we need some way to specify something like ! community@instance/post.

A big caveat is that I mean HTTP URLs. If there was a custom URL scheme like lemmy: then the rules can be different.