{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieporclnfkxr5ugcvxehurm5p2m4pxhzroifwnfggoj5vzugvkds4",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mhb7bq2sbb52"
  },
  "path": "/viewtopic.php?t=33244&p=271196#p271196",
  "publishedAt": "2026-03-17T11:56:38.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> I'm afraid you won't find it here. While I can't speak for Basilisk-Dev, I will no longer spend time on trying to troubleshoot any \"silly conflicts\" arising from a known-bad extension that, IMO, should be hard-blocked in any UXP-based application.\n\nI don't intend to block users from installing any addons, even poorly written or malicious ones, but yeah I won't be offering support for NoScript at all considering neither of you nor I wrote the extension in the first place and it's known to screw up profiles.\n\n\n> It's just a silly conflict. My browser has no other problems at all. You can just modify it a little so it is like previous version of Basilisk which was working great.\n> Noscript will always have its user base because it is easier to use. Unless ematrix is modified to provide same interface variation too.\n\nI'm not sure what you mean in regards to modifying Basilisk to behave like the previous one. There were no changes that would affect your ability to do a Google search.\n\nA simplified fork of eMatrix with a similar interface to NoScript is actually not a terrible idea.\n\n\n> But we need something right away.\n\nThe community is absolutely happy to help with issues, but demanding immediate help is not going to do you any favors here.\n\n* * *",
  "title": "Basilisk • Re: google search not working",
  "updatedAt": "2026-03-17T11:56:38.000Z"
}