JsonCulverhouse, 1 month ago

@silsinn9821 @kashi.usuiro It kind of seems like i can mention them from my mastodon instance

JsonCulverhouse, 1 month ago

@silsinn9821 @kashi.usuiro

The activitypub generated has a proper mention in the tag.

{  
"type": "Mention",  
"href": "<https://threads.net/ap/users/17841461281678268/>",  
"name": "@kashi.usuiro"  
}  

silsinn9821, 1 month ago

@JsonCulverhouse Except on my end, you ended up pinging a non-existent user from your own local instance (followed by the dot, the usuiro, & the Threads domain name):
@kashi

JsonCulverhouse, 1 month ago

@silsinn9821
I think that misskey must be broken... (also your mention generated a link back to your site in a strange way...)

you can see that the federated activity pub message is correct.

I've seen this quite a bit with threads mentions. Joining the the h-card in the html and the Mention from the #Activitypub tags is non trivial.

https://flipboard.social/@JsonCulverhouse/112220494684529008.json

silsinn9821, 1 month ago

By the way, that #Threads account belongs to a small Japanese #bakery shop selling #cakes online, in case anyone here wishes to buy from them:
@kashi.usuiro@threads.net
(Sadly, it seems you cannot yet directly @ them from #Misskey as the dot immediately breaks the ping for being outside the instance-domain-name part, so I had to fake the ping here by making it a #maskedlink to their URL.)

silsinn9821, 1 month ago

So, this (the dotted usernames that can federate with other #ActivityPub instances but can't yet be @ pinged from such instances) is a clear example of #EEE being exercised by #Threads upon the #Fediverse.
@youronlyone Your thoughts on this again, as we previously discussed it on #Bluesky?

youronlyone, 1 month ago

@silsinn9821

Oh, and:

but can't yet be @ pinged from such instances) is a clear example of #EEE being exercised by #Threads upon the #Fediverse

Is, well, not a fair example because dotted usernames have been in used years before Threads and the Twitter Migration. As I mentioned, site plugins have been using @-domain.tld@domain.tld format.

If dotted usernames are going to be used to build a case of EEE by Meta, then the same argument can be used to accuse all other “plugins” using the same format, like Automattic's AP plugin and Brid.gy fed. ^_~

To clarify, I'm not defending Threads. I just find the issue of dotted usernames being linked to EEE, to build a case against Threads, as inaccurate. ^_^

Ciantic, 1 month ago

@youronlyone @silsinn9821 You are correct. Even *@example.com is valid.

"The userpart consists only of Unicode code points that conform to the PRECIS IdentifierClass specified in [RFC7564]."

"Code points in the range U+0021 through U+007E, i.e., the (printable) ASCII7 ("K") category defined under Section 9.11. These code points are "grandfathered" into PRECIS and thus are valid even if they would otherwise be disallowed according to the property-based rules specified in the next section."

BeAware, 1 month ago

@youronlyone @silsinn9821 ....my Threads account has a . In it and I never had issues tagging it from Mastodon....🤷‍♂️

youronlyone, 1 month ago

@BeAware

Yep. It looks like a #Misskey, and forks, issue.

I can't test it from a #Pleroma site though (I just found out today the Pleroma site I had an account, closed down).

@youronlyone @silsinn9821