*potential servers ;)
I remember this automation causing false positives on Twitter. Mastodon approach expect an explicit http(s):// and I think it's fair because when you share a link then in 99% cases you copied it from a browser and with the protocol. It's rare to type example.com
My three sats here
Diff-thong
npub1ma…uptl0
2024-09-26 12:50:59
in reply to nevent1q…cn6y
Author Public Key
npub1maqyarfu90swstp34r7ervz9wmg07gazv5ezjfmpa2cfpv5885hszuptl0Published at
2024-09-26 12:50:59Event JSON
{
"id": "b8556a250a13136e64be76603105c49f5c62d8fc0623ce32b8ebc27687014301",
"pubkey": "df404e8d3c2be0e82c31a8fd91b04576d0ff23a26532292761eab090b2873d2f",
"created_at": 1727355059,
"kind": 1,
"tags": [
[
"e",
"d5979dce9bf9969cc6a8f8d11c9a79baa7a9cf18bef7d61fa86f8d1c459f6e4f",
"",
"root"
],
[
"e",
"5c3fa0fb4b6ba7e17b1842793ed9d6491715f04c485c316212e0ef8c5b9ea996",
"",
"reply"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"r",
"example.com"
]
],
"content": "*potential servers ;)\n\nI remember this automation causing false positives on Twitter. Mastodon approach expect an explicit http(s):// and I think it's fair because when you share a link then in 99% cases you copied it from a browser and with the protocol. It's rare to type example.com \n\nMy three sats here",
"sig": "33842ce387d59d0097de04747ee7fa64b7bbfafa7ab45df03ffc5dd743e9eef566fd564ffa701954a36d87e1070d50c129dc7114d99866edfbd237b7fcd02a8f"
}