{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihaua76rrpmbtl5jkoezhfvh6czpspydsohbfbdzivpxrvke6viaq",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mjmg437odsa2"
  },
  "path": "/viewtopic.php?t=33298&p=272393#p272393",
  "publishedAt": "2026-04-16T10:56:59.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> tl;dr - you need to change the extension id (don't use name@something - it has to be a proper UUID that you can generate with tools locally or even online) to signify that this is your own separate work with no extension level confusion with what it's based on.\n\nI do agree with you. My project started as a personal use of an updated Greasemonkey fork, but it kept getting more distant from the old fork, the more updates I release, making it act almost completely different from the old fork that it was based on.\n\nSince It's not my intention to introduce any type of maleware-behavior in my extension, I will be changing the UUID on the next release. I'll first have to see if there's any way in backing up the userscripts, not only for me, but for the other users of my extension.\n\n\n> AFAICT external extensions are a special case on the addons site and can't be managed by the developer using an extension site account (separate from the forum). RealityRipple can confirm, he has several externally hosted extensions here. If not, I'll be happy to publish your extension here once you've made the changes.\n\nThat makes sense, since the addons site would only be responsible in adding an external link of GitHub into the site, and everything else would be on the developer's responsibility on the other site. I'll keep in touch, once I make the changes on the next release.\n\n* * *",
  "title": "Add-ons • Re: Working on a Greasemonkey fork for Pale Moon",
  "updatedAt": "2026-04-16T10:56:59.000Z"
}