Hi,
From Misskey (11.37.1), when a person under Glitch-Soc writes a message or answers me, the name of the instance of the people in the conversation is automatically replaced by the name of the person under Glitch.
Reply example, (me on Misskey : @meow.zarchbox.fr)
This problem only occurs with people under Glitch-Soc, no problem with Mastodon, Pleroma, Hubzilla or other social platform.
Issue on Glitch-Soc : https://github.com/glitch-soc/mastodon/issues/1304
<a href="..." class="u-url mention" rel="nofollow noopener tag noreferrer" target="_blank">
みたいに、rel=tagなものがHashtag扱いされてしまう。
たぶんtag = Hashtag | Mentionなのでtag見てHashtagを判定するのが正しくないのかも。
しかし、rel=tagを採用しないようにするとMisskeyのHashtagが認識できなくなってしまう。
contentのHTMLタグの属性を見るのではなく
APのtagのnameにあるかどうか見たほうがいいかも
tag: [
{
type: 'Mention',
href: 'https://example.com/users/user',
name: '@[email protected]'
},
{
type: 'Hashtag',
href: 'https://example.com/tags/tag',
name: '#tag'
},
でもこれ content <=> tag ってマッチ不可能では
content: <a href="https://example.com/@User">@User</a>
hrefはurl, textはホスト名が省略されている
tag: [
{
type: 'Mention',
href: 'https://example.com/users/User',
name: '@[email protected]'
}
hrefはid
textはホスト名が省略されていない
Hashtagのhref正規化してくれるとうれしい
<a href="https://example.com/tags/RSSfeed" class="mention hashtag" rel="tag">
tag: [
{
type: 'Hashtag',
href: 'https://example.com/tags/rssfeed',
name: '#rssfeed'
},
The cause is
At the time of reception, it is miss judged as a Hashtag instead of Mention.
Therefore, the host name is not added at the time of reception.
The client displays it as its own host.
The developers of Glitch have fixed the problem 👍