21–30 of 35 posts
How does this compare to Apple Private Relay?
Apple private relay uses Fastly as one of the providers so I wouldn't be surprised if this is implemented the same way.
Earlier quoted context omitted.
This service with Mozilla utilizes OHTTP, whereas iCloud Private Relay uses MASQUE. OHTTP is ideally suited for privacy enablement of APIs, whereas MASQUE is more for general purpose traffic. OHTTP has similarities to MASQUE in that it uses a two hop proxy design where each proxy only knows part of the total requestor / request information. And in both cases these proxies must be operated by separate entities that do…
>However, the key difference is that in OHTTP the end destination is known, because there is a 1-1-1 mapping between OHTTP Relay -> OHTTP Gateway -> Target. This could become more generalized in future revisions to OHTTP, but right now it's all hardcoded behavior. So the Relay knows the requested URL? That’s not masked by the client?
Earlier quoted context omitted.
>However, the key difference is that in OHTTP the end destination is known, because there is a 1-1-1 mapping between OHTTP Relay -> OHTTP Gateway -> Target. This could become more generalized in future revisions to OHTTP, but right now it's all hardcoded behavior. So the Relay knows the requested URL? That’s not masked by the client?
The Relay doesn't know the requested URL or the request body -- but it does know the next-hop destination (the OHTTP Gateway), and by virtue of the way most OHTTP services are currently deployed this tells you the destination service. It does not tell you the specific details of what is being asked for / returned by that service.
Mozilla and The Tor Project have been collaborating for years. Mozilla does not have the backbone to implement Tor Browser as Private Browser mode in Firefox. Do better, Mozilla.
Now just do native vertical tabs and I'll have 0 problems with FF
Now just do native vertical tabs and I'll have 0 problems with FF
I’d settle for being able to turn off the unreasonably huge pane header that comes with extensions that implement vertical tabs via the sidebar. Yes it can be hidden with userchrome mods, but it shouldn’t be necessary to resort to that, plus we don’t know how long userchrome mods will continue to work…
Now just do native vertical tabs and I'll have 0 problems with FF
I’d settle for being able to turn off the unreasonably huge pane header that comes with extensions that implement vertical tabs via the sidebar. Yes it can be hidden with userchrome mods, but it shouldn’t be necessary to resort to that, plus we don’t know how long userchrome mods will continue to work…
#TabsToolbar {visibility: collapse;} #sidebar-header {visibility:collapse;}
Missing from this article is: How do I disable this. My initial thoughts are: I don't have any reason to trust fastly or their motivations. I certainly don't have any desire to use them as a proxy server for all of my HTTP traffic. I'll review the OHTTP spec carefully, which seems to have been put forward by mozilla (who I have limited faith in) and Cloudflare (whose motivations are suspect), and evaluate this in dep…
Without going into trust / motivation / etc. of various organizations, OHTTP is not used for general purpose web browsing. This Fastly service is used by Mozilla in conjunction with their own origins, not to random origins on the Internet.
Now just do native vertical tabs and I'll have 0 problems with FF
Native would be great, but for my use case the Tab Center Reborn extension for Firefox is the best implementation of vertical tabs I've used on any browser, native or otherwise. There's other extensions like Sidebery and Tree Style Tabs, but I haven't really tried them.