Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)X

xad

@ xad @lemmy.ml

Posts
0
Comments
6
Joined
2 yr. ago

  • Do you use Pocket or other Read Later App?

    Jump

  • So what's preventing those people from using bookmarks as "check this out later" tool?

    Bookmarking a page does not give you control over its content. So if you bookmark something and the host deletes it, you are screwed.

    If you instead clip the content or save it as a PDF, you retain access regardless of the original host.

    For example, I save every good article I read as a PDF, which I cloud sync to a folder. I have a second folder for stuff I don't want to keep open as a tab but still want to read later. There are probably far better services out there, but I like the lack of technical dependencies and lock-in.

  • Mozilla rolls out first AI features in Firefox Nightly, and theyre actually useful.

    Jump

  • Yeah, just create an entirely new, incompatible extension engine from scratch for this one feature specifically!

    This is absolutely not how any of this works.

    While Mozilla implements the WebExtensions API based on the W3C standard, they are not bound to a 100% verbatim implementation. Like other browser vendors, Mozilla has the flexibility to extend or modify the API as needed, as long as they maintain compatibility with the core standard. Adding new APIs or features to the extension system does not require creating an entirely incompatible engine. Browser vendors often add non-standard extensions to APIs, which can later be proposed for inclusion in the next version of the standard if they prove useful. So, Mozilla can certainly add new APIs to their extension system without making it incompatible with the existing WebExtensions ecosystem. This is not difficult to understand.

  • Mozilla rolls out first AI features in Firefox Nightly, and theyre actually useful.

    Jump

  • Mozilla isn't in charge of the extension API, it uses Chromium's WebExtensions API

    No. They are basing their implementation on that of Chrome, but nobody is forcing Mozilla to do this ... So yes, Mozilla is responsible for all the APIs they integrate. Of course.

  • What are your thoughts on this? "How did Mozilla Firefox go from being the best and most beloved browser to suddenly the worst company and browser according to Reddit"

    Jump

  • Like yea, it'a technically a levie, not a tax. This whole "it's different because it does not go through the budget" is such a learned talking point. We have it in Germany as well with our state funded public media houses. You say something about their bias, count to five and suddenly someone appears and tells you that same story of fictional independence through funding through levie.

  • Mozilla rolls out first AI features in Firefox Nightly, and theyre actually useful.

    Jump

  • Mozilla rolls out first AI features in Firefox Nightly, and theyre actually useful.

    Jump

  • The extension APl doesn't have enough access for this.

    If that's the case, then it's pretty great that Mozilla is also the exact company in charge of the extension API.

    I have only one extension, and I use it longer than I use Firefox. I also trust the developer a lot more than I trust Mozilla.