15
submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/[email protected]

Help! I'm paralyzed by indecision. Where should this "Cross-posted" badge go. It will be used to show that a post's URL has been cross-posted to another community.

Options:

Under the title Above the title Above the header Under the post Somewhere else entirely?
top 15 comments
sorted by: hot top new old
[-] [email protected] 7 points 2 weeks ago

+1 to under the title (I've been staring at this for too long, I think this one looks most pleasant).

[-] [email protected] 5 points 2 weeks ago

Don't devote an entire horizontal row in the UI - share the row used by the author name:

[-] [email protected] 4 points 2 weeks ago
  1. Wow I did not format that table correctly. Will fix.
  2. I considered this but the issue is I am worried I will need to add another badge in the future. Giving it its own row adds an easy way to add more badges in the future.
[-] [email protected] 6 points 2 weeks ago

I guess if the need for more badges arrives you could always change the design or offer an option then.

Semantically it makes sense to put it after the community (ie crossposted from somewhere else) or after user who did it. I'd rather have this information in some shape or form in that location than that it's shaped like a badge.

[-] [email protected] 2 points 2 weeks ago* (last edited 2 weeks ago)

I don't really think it makes any sense personally for it to be there. The point of the button is (1) for users to know the post was cross-posted somewhere else and (2) a tappable item that if the user taps will display all the locations it was cross-posted too.

Another user made a good point that it should probably appear after the title because it reads better. Eg. you see the post first and then you see that it's cross-posted. In addition, it ties the information to the post which makes sense. It shows the user "this post has been cross-posted elsewhere".

If it appeared by the name, it would be confusing since the immediate context is the name and community. A name or community being "cross-posted" makes no sense. You can't cross-post a person or a community. You cross-post a post.

[-] [email protected] 2 points 2 weeks ago

Unless you have immediate plans to add other badges, I'd go with the nice inline design, since that frees up some space in the current layout. You can always revisit it later.

[-] [email protected] 3 points 2 weeks ago

I agree with this one. And if you adjust the size could fit two (maybe three?) badges if more needs to be added in the future

[-] [email protected] 5 points 2 weeks ago

My opinion, as a web dev who strives for semantic and accessible document structure, is that you cannot put such a tag ahead of the title of the post. The post is the thing being cross posted. Not the community, not the user, not the whole app, etc.

So now it's just a matter of how important the declaration of cross posting is. Is it more important that the (preview) body copy? Maybe to some communities but definitely not to others.

[-] [email protected] 5 points 2 weeks ago

I'll just do "Under the title"

[-] [email protected] 5 points 2 weeks ago

Absolutely not in the notification bar, that's for damn sure.

[-] [email protected] 5 points 2 weeks ago

Lol that's a joke. It's meant to be a choosing of your choice. Although if you want it in the notification bar...

[-] [email protected] 4 points 2 weeks ago

I think i like under the title, more.

[-] [email protected] 3 points 2 weeks ago

I think under the title looks better but under the post feels better. Does that make any sense? Anyway I'd be happy with either of those.

[-] [email protected] 2 points 2 weeks ago

I think, above or below is great

[-] [email protected] 1 points 2 weeks ago

I also tried some other places like in the header. However I am not favoring those places just in case I have to add another badge tomorrow. Ideally this solution should scale to more than just 1 badge type.

this post was submitted on 15 May 2025
15 points (100.0% liked)

Summit

961 readers
9 users here now

Community to discuss Summit, a Lemmy reader for Android.

App (Play Store): https://play.google.com/store/apps/details?id=com.idunnololz.summit

APK: https://github.com/idunnololz/summit-for-lemmy/releases

Source: https://github.com/idunnololz/summit

Support the app

Support me on Patreon

Website: https://summit.idunnololz.com/

founded 2 years ago
MODERATORS