0x12B might help reduce instability after you get it.
More important question is - how this nitter instance is still working!!
The Wall Street Journal reports a deal was discussed, but is "far from certain."
shh..it's a spyware and adware!
"Partners cited miscommunication, unfulfilled promises, and generally poor treatment, reminiscent of Intel’s behavior during its dominant years." - AC Analysis
Hong Kong-based retailer Synnex straight-up offers the Core i9-14900K owner a refund.
> A Real-Time Website Privacy Inspector
>Who is peeking over your shoulder while you work, watch videos, learn, explore, and shop on the internet? Enter the address of any website, and Blacklight will scan it and reveal the specific user-tracking technologies on the site—and who’s getting your data. You may be surprised at what you learn.
What Firefox provides here:
A connector to LLM providers.
Accelerators (context menu options).
From a coding perspective, this should ideally be a very lightweight functionality.
This feature is very analogous to options to add a search engine, and also to provide accelerators via context menu.
While it can be done via third-party or Official Mozilla add-ons, but (to me) it still makes sense to have it part of the product.
If you're using a VPN at the OS or browser level, just like any other traffic, your query to the LLM service will be routed via the VPN. That VPN could be any VPN of your choice - Firefox VPN, Mullvad, or Proton etc.
The only problem is that most LLMs require a profile/login to work with. In such cases, using a VPN will be useless, as the LLM server will know who you are.
It's just a plain integration with 3rd-party or self-hosted LLM service.
I'm not sure if Mozilla will make money from this feature in any way.
Have you read anything about it anywhere?
It's just an integration with LLM services and not AI baked-in the browser code. You can even self-host any such service (Ollama) and integrate Firefox with it. That will make sure your query is not leaving your network.
A few things to keep in mind:
-
This feature is just about working with existing AI models.
-
People who worry about privacy can still use it by connecting with an LLM on their own computer (like a local version of Ollama).
-
Whether this feature helps or not depends on how each person uses it.
Rustdesk controversy
The whole discussion on that pull request is extremely sketchy, IMO.
A list of Free Software network services and web applications which can be hosted on your own servers - awesome-selfhosted/awesome-selfhosted
It’s about their FakeSpot subsidiary.
https://support.mozilla.org/en-US/kb/review-checker-review-quality#w_protect-your-privacy
Protect your privacy Firefox is committed to empowering you with information about review reliability while respecting your privacy. We use Oblivious HTTP (OHTTP) for Review Checker. When Review Checker is turned on, we use information about the products you visit on Amazon, Best Buy and Walmart to analyze the reviews, but by using OHTTP we ensure Mozilla cannot link you or your device to the products you have viewed. OHTTP uses encryption and a third party intermediary server to offer a technical guarantee that this is the case: all Mozilla learns from this network request is that someone, somewhere, looked at a given product.
Also not what I said.
Source: 2022 Hey look, years ago. And your other page was 2018.
Mozilla started selling private data to advertising companies in 2023
(Assuming this is about Pocket) Is it too much to expect from you to know the difference between aggregated non-PII data vs PII data?
Yes, like publishing a new article every day just to prove their commitment to end-users' privacy.
Incremental updates to articles, hosted literally on home page, with details of newer privacy features is so old school.
Got it. Thanks for the clarification.
Source: 2022
Incorrect, that's actually from 2022 B.C.
And your other page was 2018
Correct, the snap of article from 2018 looks exactly identical to 2024 instance with ZERO modifications. Mozilla finally gave us on Privacy it seems, as no one bothered to update that page since 2018.
Wait a sec, they also haven't updated this article as well since 2020. https://www.mozilla.org/en-US/firefox/browsers/compare/chrome/
/s
Seems to have some severe bugs: https://github.com/wasi-master/13ft/issues
but Mozilla itself doesn’t want to broach the topic.
Again, a reminder that Mozilla plans to continue support for the Manifest Version 2 blocking WebRequest API (this API powers, for example, uBlock Origin) while simultaneously supporting Manifest Version 3.
Years ago, Mozilla would explicitly call ad blocking a privacy feature, and proclaim it explicitly.
Ahem! https://www.mozilla.org/en-US/firefox/features/ > https://www.mozilla.org/en-US/firefox/features/adblocker/
Cooking up conspiracy theory instead of research is easy, is not it?
... because Mozilla already clarified their position on this last year.
TL;DR
No, Mozilla is NOT ditching manifest v2.
Well what’s happening with MV2 you ask? Great question – in case you missed it, Google announced late last year their plans to resume their MV2 deprecation schedule. Firefox, however, has no plans to deprecate MV2 and will continue to support MV2 extensions for the foreseeable future. And even if we re-evaluate this decision at some point down the road, we anticipate providing a notice of at least 12 months for developers to adjust accordingly and not feel rushed.
Source: https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update/
It might be a while before we find out.
>A federal judge has ruled that Google has an illegal monopoly in the US. “The market reality is that Google is the only real choice” as the default search engine, Judge Amit Mehta said in his decision, and he determined it had gotten that way unfairly. It’s a ruling that could portend big changes for the company, but we yet don’t know how big, and we might not for years.
>Mehta declared on Monday that Google was liable for violating antitrust laws, vindicating the Department of Justice and a coalition of states that sued the tech giant in 2020. The next step — deciding on remedies for its illegal conduct — begins next month. Both parties must submit a proposed schedule for remedy proceedings by September 4th and then appear at a status conference on September 6th.
Intel is committed to making sure all customers who have or are currently experiencing instability symptoms on their 13th and/or 14th Gen desktop processors are supported in the exchange process. To help streamline the support process, Intel's guidance is as follows: For users who purchased 13th/...
In a rather stark turnaround, Google is no longer ending support for third-party cookies in its Chrome browser...
>For those wanting to build a Wayland-only Linux desktop experience without carrying any aging X11 baggage, GNOME 47 will be able to optionally offer Wayland-only support without carrying X11/X.Org support. This Mutter merge request landed today that allows compiling Mutter with X11 support disabled. That landed today along with this GNOME Shell merge request for being able to disable X11 support too.
NVIDIA 555.58 Linux graphics driver is now available for download with explicit GPU sync support for NVIDIA GPU users on Wayland.
Japan has taken a leaf out of the EU’s regulatory book.
Canonical announces the general availability of an enterprise-grade real-time Ubuntu kernel for Ubuntu 24.04 LTS (Noble Numbat) systems.
>To get started with the real-time kernel for Ubuntu 24.04, check out the official documentation. One thing to keep in mind if you’re an NVIDIA GPU user is that the real-time Ubuntu kernel does not support the proprietary NVIDIA graphics drivers.
Rival coders must have Europe-based staff to build and test non-WebKit surfing
>The Register has learned from those involved in the browser trade that Apple has limited the development and testing of third-party browser engines to devices physically located in the EU. That requirement adds an additional barrier to anyone planning to develop and support a browser with an alternative engine in the EU.
>It effectively geofences the development team. Browser-makers whose dev teams are located in the US will only be able to work on simulators. While some testing can be done in a simulator, there's no substitute for testing on device – which means developers will have to work within Apple's prescribed geographical boundary.
>... as Mozilla put it – to make it "as painful as possible for others to provide competitive alternatives to Safari."
