Would it make sense to create a new namespace called 'sandbox' or whatever to use for new tags that aren't adopted into the name space?
I'm asking this in light of a github discussion about removing podcast:image from the namespace because it's not widely used, and I don't think any of the apps support it.
Should we have a one year period with the early adopters to flesh out new tags in a sandbox so we can figure out if the tag is useful and be able to safely modify it before adopting it?
Steven Bell :pci: /
npub12q…wrqfx
2024-01-19 13:49:08
Author Public Key
npub12qsqnxcdzphcgvlc07f8fwhflx9kvvnzqmv99h83dc2ljnxewyds4wrqfxPublished at
2024-01-19 13:49:08Event JSON
{
"id": "073deecf9e501968bd41fb28c6b9169b9090beaa4e7b58f39de2db40ceb79fe0",
"pubkey": "5020099b0d106f8433f87f9274bae9f98b66326206d852dcf16e15f94cd9711b",
"created_at": 1705672148,
"kind": 1,
"tags": [
[
"proxy",
"https://podcastindex.social/users/StevenB/statuses/111782929925860728",
"activitypub"
]
],
"content": "Would it make sense to create a new namespace called 'sandbox' or whatever to use for new tags that aren't adopted into the name space?\n\nI'm asking this in light of a github discussion about removing podcast:image from the namespace because it's not widely used, and I don't think any of the apps support it.\n\nShould we have a one year period with the early adopters to flesh out new tags in a sandbox so we can figure out if the tag is useful and be able to safely modify it before adopting it?",
"sig": "d9ad81622491a27303c0c90d30e185a0030c00bf4c66c4fc0856561295042ee223d6f30b2be2a330063c18edc344f0e3a45ed6ee1ae6f58f708414c84e16160d"
}