Detect when your installed Firefox addons have changed owners
github.com
github.com
Fortunately, most customizations can be done via bookmarklets.
Benefits of bookmarklets:
- Easy to edit
- Inactive until clicked
- Work in all browsers
- Work on mobile
- Integrate nicely into the UI. You can move them around, put them into any bookmark folder, assign shortcuts.
I wrote this bookmarlet editor which makes it easy to convert between clean code and a bookmarklet:
https://www.gibney.org/bookmarklet_editor
Here is one that I use to read HN:
if (!location.href.match('ycom'))
location.href='https://news.ycombinator.com';
doTheMagic = function() {
if (typeof e!=='undefined')
e.style.background='#c0c0c0';
e=Array.from(document.querySelectorAll('.age a:not(.seen)')).sort().at(-1);e.style.background='#ff0';
e.classList.add('seen');
e.scrollIntoView({behavior:"smooth",block:"center",inline:"nearest"});
}
doTheMagic();
if (typeof theMagicIsActive=='undefined') {
document.addEventListener("keydown", function(evnt) {
if (evnt.key === "n") doTheMagic();
});
theMagicIsActive = true;
}
When clicked and HN is not already opened, it opens HN. When on HN, it jumps to the next newest story. Or comment - it also works in the threads. After jumping to the newest story, clicking it again jumps to the next newest story. Instead of clicking it, pressing "n" also works.Also works in the comments view of a profile. So when you want to see if someone replied to your comments, you click on "comments" in your profile and then on the bookmarklet to jump to the newest reply.
That's because addons are a relic from the wild west era of the 1990s, where the philosophy was to give the user a chainsaw and if they chop their own leg off that's their problem.
That's in contrast to the modern software design philosophy, which is that the average user is so drunk they're almost falling over, and the world should contain no chainsaws whatsoever in order to accommodate this.
Browser designers would love to remove add-ons, but no browser can succeed without an ad blocker, and providing an extension mechanism provides this, without requiring the browser maker to get into the ad blocking game personally.
https://greasyfork.org/en/help/code-rules
https://greasyfork.org/en/help/external-scripts
It would be great if there was a way to set them to not execute until clicked, but at least it's easy to see the list of scripts that are set to run on the current page and toggle them on and off.
https://github.com/1ps0/elos-connect
https://elos-edu.notion.site/eLOS-Connect-0-0-11-a72acbec893...
Curious to see if anyone else is able to find use cases for the components/sidebar and urlbar CLI I've been building.
Honestly, I'm not sure what difference this makes. If someone really wants to hide their sale of an extension, they can absolutely include the usage of their dev account to the buyer, rather than making use of mozilla's system for transferring ownership.
If you're curious, here's the relevant section of code. I'm totally open to reworking it if you have alternative suggestions:
https://github.com/maxtheaxe/under-new-management-firefox/bl...
I'm hitting the AMO API directly, so you can see an example response of all the data I'm working with here:
https://addons.mozilla.org/api/v5/addons/addon/under-new-man...
I know there is a setting to not auto-update on an case-by-case basis, as browsers auto-update extensions by default as a security measure. In that case, an alert that there are updates would be welcome.
Any solution to this, or am I missing a setting somewhere? (On Firefox or Chrome)
Can an extension see what other extensions are installed and their versions? Can your extension maybe show when one of them is updated? Can also be a way to keep 'manually' an eye on changes?
A lot of discussion on the main one earlier: https://news.ycombinator.com/item?id=39620060