66 comments
@pieceofthepie@social.n8e.dev @dansup@mastodon.social @pixelfed@mastodon.social This is very important, otherwise #susanalbumparty could mean #SusanAlbumParty instead of #SusAnalBumParty... @dansup from my observation (in IG), most folks there purposely "hide" hashtags by putting in a lot of newlines (and force "show more") or add them via a comment instead of post description. Surfacing them this way seems to undo their intentions in my opinion 🤔 @cheeaun @dansup Yeah, but didn't nt they do that because all the tags are noisy, which this UI would fix? That manual way of hiding tags is more work for those posting, and annoying for those reading, because they can't know if there's a read more link because there's a new paragraph of actual text, or just tons of tags. So people have to press the read more all the time just to check, wasting everyone's time. What if the tags are separated out, like this, but also hidden behind "Show tags"? @dansup @pixelfed I'm old school and don't like the overall UI push to more whitespace/vertical spacing. This is minor but still, tend to prefer tags that are different color so they stand out. But also realize that's not fully accessible. Buttons certainly make tag navigation more likely. So on fence 😂 @mspsadmin @pixelfed There will be a "distraction free" setting that hides everything but the media, allowing you to long press for options or tap to load the full post screen! @dansup Generally I agree with @SunDancer. But I do prefer if they’re highlighted somewhat, e.g. with a different color. I also generally despise these hashtag soups where people add so many of them @aymm @dansup @SunDancer @pixelfed I like the new ones better. The separation makes them better readable. @dansup@mastodon.social @pixelfed@mastodon.social looks much better, more fedi clients need it @dansup @pixelfed I love this, but my primary concern is losing the context when users rely on inline hashtags. By pulling a tag out of context it can completely break the flow of the post. If you could identify inline tags and leave the content in place, but add the tag to the footer. It would work fine. “This #tag adds meaning. Could become: “This tag adds meaning. [tag] [pixelfed]” Love it - looks super clean and easy to read. Are you going to treat tags embedded within the text the same way, or keep it to tags at the end of the post? @dansup @pixelfed I like the pill display much better. 👏🏻 1. However, keep the letter casing untouched. Also, what is the behavior with hashtags in the middle of the text? Are they cut off? @dansup @pixelfed I would caution against lowercasing tags since concatenated CamelCase words are useful for legibility and accessibility. Visually this style is more pleasant, but might cause people to new to the platform to not know how to create tags (i.e. by prefixing words/phrases with a #). You'll also have to contend with how this content appears in feeds or via the API. Also: how would #hashtags appear inline? @chrismessina @dansup @pixelfed Seconding the point about hashtags and accessibility. @dansup @pixelfed I much prefer the new version, but as others pointed out, I think maintaining the case is important. I would also like for the # signal to be kept to make it more explicit, which I feel is specially more relevant when the hashtag is in the middle of the text for example (which I assume would still be possible, it would be horrible to not be able to use hashtags in the middle of the description). @dansup @pixelfed Like the second one much more, looks cleaner, nicer and more organized too. The improve readability is a plus and it can help with accessibility too! I'd say go for the 2nd option, limiting the amount of hashtags visible will also help reduce post clutter and make it a much more enjoyable viewing experience @dansup @pixelfed what would this do with inline hashtags? Ie if i use a hashtag in a sentence like |
@dansup I find "hashtag buttons" more readable and overall nicer