Default Branch

master 02502e3263 · update debian changelog · Updated 2025-02-20 14:53:29 -05:00

Branches

silly-failover-timeout 92184a4282 · add isolators for reseed and reseed and Tor management, integrate Socks plugin · Updated 2022-01-28 17:54:05 -05:00    idk	198 3	Compare
tab_text 26b637f201 · fix tab text color · Updated 2021-12-28 20:22:33 -05:00    idk	203 0	Included
use-esr-dammit c1b55a4feb · Merge branch 'innet-updates' into 'master' · Updated 2021-12-28 20:15:38 -05:00    idk	204 0	Included
innet-updates 80c66ba2f7 · Auto-proxy on sites that specify a port · Updated 2021-12-28 20:13:12 -05:00    idk	209 0	Included
fix-torrent-webui-button 83b5dcc4b4 · fix Open WebUI button on torrent menu · Updated 2021-12-02 20:45:42 -05:00    idk	208 0	Included
fix-proxy-check-reversal 73f2883fbd · address erroneous text issue #113 · Updated 2021-12-02 19:50:33 -05:00    idk	209 0	Included
android-trunk 5cd23c5b3a · pare this branch down to only the manifest.json and the Makefile · Updated 2021-09-30 18:10:34 -04:00    idk	230 1	Compare
android-compat aa6a9a0da8 · Make changes to allow upstream to manage android containers as well, but do not change manifest.json because we need all the entries for desktop firefox. · Updated 2021-09-30 18:00:30 -04:00    idk	229 0	Included
fix-brb-blog 95a282c07f · Fix checks on blog and port containers · Updated 2021-09-26 00:23:48 -04:00    idk	235 0	Included
better-linter 7fbfa52109 · add hidden manifest to .gitignore · Updated 2021-08-30 22:35:51 -04:00    idk	236 5	Compare
no-chrome b402dc10e6 · This is never getting Chrome compatibility back. The Chrome, Chromium, Brave, edgium(<--Worst browser ever, and I'm including IE, the second-worst browser ever) is going to have to be a completely different codebase basically forever · Updated 2021-07-24 19:11:35 -04:00    idk	236 1	Compare
code-cleanup d3cf9e8686 · bump strict-min-version so the validator shuts up, nobody's as far back as Firefox 60 right now · Updated 2021-07-07 22:53:14 -04:00    idk	244 0	Included
thoroughly-delete-containers 49ce0162d1 · update changelog · Updated 2021-05-24 14:06:23 -04:00    idk	275 0	Included
secure-marking 42f90273e2 · prettier · Updated 2021-04-26 17:18:41 -04:00    idk	280 0	Included
themes-again eec31ad3db · bump · Updated 2021-02-05 13:03:30 -05:00    idk	291 0	Included
rpc-over-i2p 8bebe2a920 · Extensions run requests in what is effectively their own container for our purposes, and one that's not exactly easy to determine is in use. But when we don't recognize the context and cannot jump out of context into an I2P tab, we basically it's coming from inside an extension(Or firefox-private, but that's sort of a whole other can of worms I need to tackle soon). TL:DR if it has no context, then we'll need to decide in favor of proxying requests to .i2p urls via I2P HTTP Proxy for it. The effect is that we can set the RPC remote for say, a bittorrent client, to the .b32.i2p URL of our BiglyBT xmwebwebui remote, for instance. · Updated 2020-12-23 18:17:36 -05:00    idk	297 0	Included
main b605ea515f · Merge pull request #104 from eyedeekay/spanish · Updated 2020-12-21 18:13:19 -05:00    idk	299 0	Included
spanish a38d18c049 · fix #102 · Updated 2020-12-21 18:11:30 -05:00    idk	300 0	Included
page e810d7f194 · switch it to page css · Updated 2020-12-15 15:00:51 -05:00    idk	303 1	Compare