blog.nightly.mozilla.org

wolf, to linux in Firefox Nightly Now Available for Linux on ARM64

Wow, only took them … years!

If perhaps pretty please Mozilla realizes that an official ARM64 Flatpak is the perfect distribution channel for their nightly (and hopefully soon stable) ARM64, I’ll be happy and they did a great service to the Linux community. (Especially regarding Fedora Atomic Desktops / Aeon.)

ricdeh, to linux in Firefox Nightly Now Available for Linux on ARM64
@ricdeh@lemmy.world avatar

So Firefox Nightly on the Raspberry Pi?

wolf,

So Firefox Nightly for Linux on top of Arm64 hardware, like Apples, Lenovos, a whole bunch of Chromebooks etc.

bamboo, (edited )

Raspberry Pis have been arm64 since at least the 3, but raspbian was armv7 for a while longer. So yeah this would work on a raspberry pi with a aarch64 OS.

Gormadt, to linux in Firefox Nightly Now Available for Linux on ARM64
@Gormadt@lemmy.blahaj.zone avatar

Always nice to see more ARM support from things

boredsquirrel, to linux in Customizing Reader Mode – These Weeks in Firefox: Issue 158 – Firefox Nightly News

I just want a OLED black mobile version.

fossphi,

What colour do you have your text on OLED black?

boredsquirrel,

White, so that brightness can be low

fossphi,

Isn’t the contrast too high? Or maybe that’s just my astigmatism, but white on pure black isn’t very pleasant to read

boredsquirrel,

Yeah that may be true. On Florisboard I experimented a bit with light gray but havent bothered as much.

And as I said, OLED with lower brightness is basically grey

fossphi, to linux in Switch to Container Tabs – These Weeks in Firefox: Issue 157

Backup up a profile to a file project

This is some good stuff!

lemmyreader, to linux in Switch to Container Tabs – These Weeks in Firefox: Issue 157

Daisuke fixed a 22-year old bug and we now prevent passwords in URLs from being saved in history!

Interesting.

catloaf,

That’s good, but out of scope for a browser, really. Also there shouldn’t be passwords in URLs!

PlusMinus,

It is not out ot scope. Basic auth exists: username:password@example.com

____,

I have this exact use case on a work machine, because the proxy flat refuses to prompt for the login, just goes straight to deny.

I own neither the proxy, nor the steaming heap of code that lives behind it, and I’m grateful for that every single day…

catloaf,

I forgot about that. It shouldn’t, these days.

bmarinov,

It is one of the easier ways to globally configure git auth for private Go packages.

flashgnash,

That just seems like crappy website design

strcrssd,

It has nothing to do with website design. It's part of the HTTP protocol. A poor part in today's understanding and use cases, but in the 90s it would have made sense.

flashgnash,

We’re both talking about route parameters right?

Ghoelian,

I think they’re talking about basic Auth, with which you can pass credentials in a URL like this:

username:password@website.com

flashgnash,

I thought basic Auth was where you base64 encoded the username and password and sent it as the Authorization header

Ghoelian,

That is also a form of basic auth, you still pass the credentials like “username:password”, optionally base64 encoded but I don’t believe that’s required.

Edit: actually, after looking into it a bit more, it seems like passing credentials in the url will actually cause the browser to send it as an authorization header instead. So in essence it’s doing the same thing.

xlash123,
@xlash123@sh.itjust.works avatar

RIP that one guy who relied on this bug. He’s gonna have to create a bookmark now, which will ruin his whole workflow.

AnUnusualRelic,
@AnUnusualRelic@lemmy.world avatar

Oh wow, I’m pretty sure I reported this for Navigator.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • fightinggames
  • All magazines