Part of making standards and stuff like that is making sure that whatever you end up doing doesn't break preexisting expectations and code. That is why a bunch of standards are so messy - they can't disrupt existing behaviour, only add on to it.
The `profile:username` tag is complicated in this regard because (1) you can't guarantee that you won't break any existing expectations & code, as well as (2) it's very ambiguous.
Every other OpenGraph tag has a clear usecase. The username tag on the other hand does not. If you are making something that uses it how can you tell what platform that username is meant to point to? Is it Facebook (most likely the idea when making it)? Twitter? Reddit? The same random blog/news site it comes from?
And your idea about formatting - how can you guarantee that the username is a fediverse username and not, for example, a defederated chat apps username (or even a fediverse clone that doesn't interoperate with the fediverse!)). You just can't, all you can do is guess.
Making a whole new tag with a very clear usecase is a much better solution than taking over a very ambiguous tag which may or may not break preexisting expectations and code.
Exerra :wee: /
npub1a2…dgpwe
2024-09-17 20:37:31
in reply to nevent1q…4wy3
Author Public Key
npub1a2xc7yy58g2pg6wwgtpukvy2rwpp9nqklph3smg4zl5mnx3vmjcqsdgpwePublished at
2024-09-17 20:37:31Event JSON
{
"id": "b1bc4a15abdd1d228841e6512c5aad237bf494d02e5a74ba64ee580423da3353",
"pubkey": "ea8d8f10943a141469ce42c3cb308a1b8212cc16f86f186d1517e9b99a2cdcb0",
"created_at": 1726605451,
"kind": 1,
"tags": [
[
"p",
"8240035a9f30abf3fd91387f32e922b6a1240df57fb21d9b267c1c87c65434da"
],
[
"p",
"9ec94f7955b3da50a74e045be41348a80872a774f4ff9c275ed51f7d6fbb4607"
],
[
"p",
"ea8d8f10943a141469ce42c3cb308a1b8212cc16f86f186d1517e9b99a2cdcb0"
],
[
"p",
"d567f5913d1b9c350dca342b0adc75b5891ee4c2e899d8aec7628631524a46f1"
],
[
"e",
"77d87a4f248c8945e8504108f9eb35f65547b150923b4fa11c8231c658f50e43",
"",
"root",
"9ec94f7955b3da50a74e045be41348a80872a774f4ff9c275ed51f7d6fbb4607"
],
[
"e",
"70cf0cb0d2f2b9b4caf9adc4723d0f2d7ea08022e55e4002e97706cf18e8a0b0",
"",
"reply",
"8240035a9f30abf3fd91387f32e922b6a1240df57fb21d9b267c1c87c65434da"
],
[
"proxy",
"https://daedric.world/notes/9yagm9w5imxg02fq",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://daedric.world/notes/9yagm9w5imxg02fq",
"pink.momostr"
],
[
"-"
]
],
"content": "Part of making standards and stuff like that is making sure that whatever you end up doing doesn't break preexisting expectations and code. That is why a bunch of standards are so messy - they can't disrupt existing behaviour, only add on to it.\n\nThe `profile:username` tag is complicated in this regard because (1) you can't guarantee that you won't break any existing expectations \u0026 code, as well as (2) it's very ambiguous.\n\nEvery other OpenGraph tag has a clear usecase. The username tag on the other hand does not. If you are making something that uses it how can you tell what platform that username is meant to point to? Is it Facebook (most likely the idea when making it)? Twitter? Reddit? The same random blog/news site it comes from?\n\nAnd your idea about formatting - how can you guarantee that the username is a fediverse username and not, for example, a defederated chat apps username (or even a fediverse clone that doesn't interoperate with the fediverse!)). You just can't, all you can do is guess.\n\nMaking a whole new tag with a very clear usecase is a much better solution than taking over a very ambiguous tag which may or may not break preexisting expectations and code.",
"sig": "94a1892418274205ca3765b2de1235c865915ca259517ddc33f3a36448bba6dc4c6dc9bf39be7cc529e829826a05768e5343310a0427e001450b1ea7c4d2a90c"
}