-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replacing @user with full name in microblog posts may alter meaning #1479
Comments
|
The author of the post clearly intended for it to be displayed as |
I would not say that |
The mention |
You're absolutely right, I am sorry. It seems like I didn't properly read the post... However platforms do render things differently and that was my main point. I myself am unsure whether I like the inline previews/components for user and magazine mentions in the rendered markdown... I thought it was a very cool idea and I think with magazine mentions it can look very good, but with microblog mentions, especially in busy comment sections, it can be very distracting... Maybe it is time for another poll @melroy89 ? :D |
I created a discussion thread in the mbinMeta magazine: https://gehirneimer.de/m/mbinmeta/t/516855/Discussion-Magazine-And-User-Mention-Rendering |
Less is more 😅. So I'm also fine for disabling this inline markdown preview in microblog all together if that solves the problem again. |
Describe the bug
In microblog posts, Mbin displays
@user
as the full name of the user referred to. In some cases, if the author of a post intended the reference to be read as@user
, this can change or obscure the post's intended meaning.On which Mbin instance did you find the bug?
fedia.io
Which Mbin version was running on the instance?
1.8.0
To Reproduce
@tea
in the original post has been replaced withtea group
in the mbin version.Expected behavior
When viewed on mbin, the post should have the same meaning as it does when viewed on its original instance.
Screenshots
Mbin version:
Original version:
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: