You're welcome. Are you a LibreWolf developer?
Pictures should be expanded by default on the post page because they provide important context for the post, so anyone who comments should have seen it first anyway.
It is already possible to limit search to a single community, but a search bar above the post list would be faster and more convenient.
This concept screenshot shows how it could be done.
Currently, URLs to posts have this format:
lemmy.ml/post/[number]
I suggest changing it to this so people can see the community immediately in shared URLs:
lemmy.ml/c/[community-name]/[post-number]
afaik, only in tandem with search history
Great, I want that too.
and if you look for it on about:config, it’s enabled
The about:config
setting has been placebo since version 48. It doesn't affect anything.
Firefox 48: (Pushed from Firefox 46). Release and Beta versions of Firefox for Desktop will not allow unsigned extensions to be installed, with no override. Firefox for Android will enforce add-on signing, and will retain a preference — which will be removed in a future release — to allow the user to disable signing enforcement.
(source)
browser.tabs.insertAfterCurrent
is a treasure inside about:config
of Firefox (and LibreWolf for that matter). Instead of opening new tabs at the end, it opens them right next to the current tab so you can go back to the last tab instantly without scrolling through a long tab list! I believe this should be the default behaviour in every browser.
Unfortunately, too few users are aware it even exists.
I suggest you add this as a checkbox in the graphical about:preferences
menu.
A custom version of Firefox, focused on privacy, security and freedom.
The link above says form history is disabled:
> Disable search and form history.
Before I bother installing LibreWolf, I would like to know whether the form history can be activated manually. I think it is very helpful and saves time.
It is stored only locally anyway, so it doesn't violate privacy like telemetry and add-on signing to. If my data was stolen, I would have much greater things to worry about anyway.
I hope not. Add-on signing is a glorified backdoor. Not only does it let Mozilla remotely disable extensions, but in future, governments can force Mozilla to censor unwanted extensions.
In addition, it is a privacy violation, since Mozilla can see who has installed which add-on.
> […] when Firefox contacts Mozilla servers to verify if Mozilla approved each extension, it discloses to Mozilla which extensions are in use. So in addition to being a backdoor by definition, it is a severe privacy violation as well. This comes from an organization that perpetually claims to champion user freedom and privacy.
(source: change.org)
And let's not forget about a certain May 2019 incident:
> all Firefox addons have been disabled due to an expired certificate. And so, people got silently hit with stuff like this when turning their "private and secure" browser on. It was only a matter of time until Mozilla's extension prison backfired, and it did so spectacularly. Though the BugZilla comments were already predictably closed, they will not be able to contain the armageddon this time, no matter how much PR they spew. The whole /r/firefox front page is filled with threads about this, with many people moving to Chrome-based browsers. Hacker News is also booming. Tech sites are running with the news too. The funny thing is, the whole point of the extension prison was allegedly to increase security - and yet today, all security addons got disabled because of it! Shows how freedom always has to trump over security or it ends up in a disaster like this.
(source: digdeeper.club)