5,208 karma · joined December 15, 2021
> Under the new rules, Google will have to provide data to other search firms transparently and for a reasonable fee. Google will also have to treat AI chatbots as search services for the purposes of data sharing.
> The company must be ready to start sharing search data with other companies in January 2027. The Android platform must be updated for deeper integration with AI apps by July 2027.
1. Load about:keyboard
2. Find "Close tab" and click "Clear" or "Change".
1. Load about:keyboard
2. Find "Close tab" and click "Clear" or "Change".
There doesn't appear to be any other way to directly address this issue within ff, short of modifying the source and recompiling. According to MDN[0], manifest.json does not support changing internally defined keyboard shortcuts:
>If a key combination is already used by the browser (like "Ctrl+P") or by an existing add-on, then you can't override it. You can define it, but your event handler will not be called when the user presses the key combination.
0. https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
>The paper shows how an LLM can hide a full message inside another text of equal length.
>It runs in seconds on a laptop with 8B open models.
>First, pass the secret through an LLM and record, for each token, the rank of the actual next token.
>Then prompt the model to write on a chosen topic, and force it to pick tokens at those ranks.
>The result reads normally on that topic and has the same token count as the secret.
>With the same model and prompt, anyone can reverse the steps and recover the exact original.
>These covers look natural to people, but models usually rate them less likely than the originals.
>Quality is best when the model predicts the hidden text well, and worse for unusual domains or weaker models.
>Security comes from the secret prompt and the exact model, and it gives the sender believable deniability.
>One risk is hiding harmful answers inside safe replies for later extraction by a local model.
0. https://news.ycombinator.com/item?id=40856791 1. https://ladybird.org/
awesomekling does monthly progress recaps, January's[1] shows LB as the fourth most standards compliant browser, just behind Safari. For example, GMail, Google Calendar, and Figma all fully load now, though usability is not at 100% yet.
The updates also have video versions[2], which include demos of Ladybird's rendering.
Last year, Ladybird became an official non-profit[3] and received a $1mm donation from Chris Wanstrath (a Github founder). There's an optional Donorbox link in the upper-righthand corner of ladybird.org[4].
0. https://github.com/LadybirdBrowser/ladybird/blob/master/LICE...
1. https://buttondown.com/ladybird/archive/this-month-in-ladybi...
2. https://www.youtube.com/watch?v=-l8epGysffQ
I wish Mozilla the best. It would be great if they could be successful in advocating for web ads that consist of, say, a jpeg and an href, but I don't think that's ever going to happen.
Here's hoping AKling & Co ships an Android version of Ladybird. I'll happily pay for a browser developed by a team that cares about creating a quality product. That's vastly preferable to suffering the constant contempt that the people at Firefox seem to have for their ~~most ardent~~ few remaining supporters.
Edit: The Ladybird faq[0] says:
>Will Ladybird work on mobile devices?
>We don't have anyone actively working on an Android or iOS port. More effort will be put into mobile once we have the desktop versions in a good state.
>While there is the start of an Android port in the project repository, mobile is not a priority at the moment.