Unnecessary hostility. They can not and are not retroactively changing license on past contributions. The only thing affected is upstream future contributions. If nothing was lost, how can it be "theft"?
So can we take the code from up to about a mo the ago
Yes. As long as you also comply with license.
Thanks for the detailed review
I wouldn't call that detailed. It was what glared at me from skimming for a couple of minutes.
was calling pip install --break-system-packages at runtime, which is indefensible
"You" still have three instances left of runtime pip install --break-system-packages without user interaction, one of which dead code.
I think the follow-up beautifully clarified the "is this vibecoded?" question too.
Labeling it 1.0.0 seems premature to say the least.
Is this vibecoded or is there thinking behind why it will silently reuse existing user SSH keys by default? For an app like this I would expect it to exclusively use its own keys. Same for PGP.
I also find the ways dependencies are handled a bit unorthodox and surprising (possibly system-breaking even). For a python project it would make more sense with a lockfile and using a package manager for dependencies installed remotely via pip.
I also wonder why it bundles minified js for Quill editor v1.3.7 (from 2019) when unminified version would be easier to audit and maintain, and v2.0.3 was released in 2024?
I think uBO does have that.
Open popup -> Ctrl-click ⏻
Are you keeping at default window size, or resizing? If latter, it is expected. This is a gotcha when using tiling window managers as they often force a window size that may give you off. TB should otherwise start with static fixed window size. Enabling "Letterboxing" feature can help alleviate this somewhat.
On PG: Also been seeing weird vibes and some inexplicable moderation comms and actions when looking closer. Their "recommendations" and "guides" also raise eyebrows. Something is very strange there.
Hi dmitry,
I suggest committing more often and in smaller chunks. Makes the repo a lot more accessible for outsider,s and reduces risk for stuff like this, which I assume is not supposed to be committed?
Experimental JPEG-XL support in Firefox (and forks) can be enabled by setting the pref image.jxl.enabled to true in about:config.
All info on that site is several years stale and the site itself is unmaintained (last update 2022; git repo permanently archived 2024). Many of the details are not reflecting current state of things and this page is not a good resource for comparing browsers in 2026 (except as inspiration for replicating their methodology^1^).
Konform Browser is to my knowledge the only up-to-date webextension-capable browser today with literally 0 phone-home / background connections under defaults, and no telemetry or other superfluous undesired activity ever. (disclaimer: am dev. I'm certain it would be ranking as top if such a ranking was made today. Come @ me ;))
^1^: Separately recently published container-based flow for doing this kind of analysis and doing similar comparison. There are some basic results and comparison included in readme but would be cool to see someone take it to the next step, drill deeper, share more exhaustive and educative results, present it in a format more digestible for non-techies (whether using this setup or something different).
Just to be clear, most of these (think about egrep/fgrep for a moment) are deprecated and "shouldn't be used" in scripts for distribution. What's new is that you can't expect everyone else to have them and having dependency on them in shipped software is considered antipattern.
Nobody gives a shit what aliases and shims you use in your own shell.
On iptables: By now it's even gone from kernel and the turn tabled with the cli command now actually being a shim calling into its successor nft. IMO nft is much more approachable for beginners to pick up and the rules files become so much more readable and maintainable. If you're already committed to iptables syntax then cool - but with very few exceptions I don't think anyone needs to learn iptables today - just go straight to nft and you'll be happier for it. Similar for ifconfig.
I don't think the data supports that. I'm curious what makes you single it out. Mullvad is in the top-tier but it is not alone (or clearly #1 - like the post gets into - it gets nuanced and I think any attempt at general objective "top 5 ranking" will be reductive to the point of being misleading or plain wrong. So I'm not trying that here). Read again? :)
For example of nuance displayed in results:
### Number of requests
119 firefox
81 firefox-esr
0 konform
7 librewolf
30 mullvad-browser
62 zen-browser
There is a longer discussion to be had about both what RFP does, how effective it is, and the relative impact on entropy of this particular feature.
For now I will just say that this: Providing configuration for this serves the projects goal of user control and freedom. It should be up to the user to make that call. Us as developer shouldn't unilaterally decide on behalf of everyone. We can't think of everything and we don't always know best. Of course we can still provide guidance and put what we believe is sensible as defaults. I find it odd to criticize empowering users in this way, in particular considering the status quo.
Were it up to me, everyone should have Letterboxing on by default, probably with similar reasoning. I don't see why you wouldn't use it. Everyone enabling it would make us all (ever so little) less fingerprintable. Arguably more meaningful impact than dark/light-theme. And less of an accessibility issue. Even so, we still leave this configurable in the same way as the dynamic theming.
You can also see this way of thinking reflected in allowing loading of your own add-ons from file and allowing userChrome customization. Probably niche power-user features with risks involved and sharp edges exposed but we are developers and maintainers of software, not your sysadmins^1^ or caretakers^2^.
If you fundamentally disagree, well, not all software has to be for everyone. Probably there is already something else (like Tor Browser) that serves your needs and aligns with your philosophy better?
^1^: ...xcept... you want us to be your sysadmin? 👉👈 Call me when you close that seed round bb 😘
^2^: Nope.
Let's not forget that Win7 was almost 25% as responsive as Win2k3, which could even hold a candle to GNOME.