Zum Inhalt der Seite gehen

Wilhelm hat dies geteilt


We are a Union of 27 countries and 450 million people sharing one future.

Diversity is what defines, unites us.
Diversity is also what makes us love the Fediverse.

As we mark two years on Mastodon, thank you for enlivening the conversation with insightful comments and content.

Love does not increase after the first day, but it deepens.

Let's make this journey even more engaging!

What topics did you like the most and would like to see more often 👇

Als Antwort auf European Commission

I know that legally we are no longer part of the EU but in our hearts and mind we never left 🏴󠁧󠁢󠁳󠁣󠁴󠁿🇪🇺
Als Antwort auf European Commission

"If Putin is weaponizing migration, then Europe, in a very real way, is channelling ammunition to him."

opendemocracy.net/en/beyond-tr…

I think that the European Union has to accept migrants coming through the southern border. There will be more and more people coming as climate changes. We have to accomodate them.

Ignoring it doesn't make it go away. It only makes it worse for everyone.

Dieser Beitrag wurde bearbeitet. (34 Minuten her)

Wilhelm hat dies geteilt


Last Friday, the US House of Representatives renewed Section 702 FAA, which authorizes the NSA's PRISM and Upstream collection. However, the renewal is only for 2 instead of 5 years: cbsnews.com/news/fisa-reauthor…

Wilhelm hat dies geteilt


Since I see that a notable VC-famous jerk is now telling us that he wish he'd "stood by" Eich way back, I'd like to tell you a true fact that situation: Eich didn't lose the CEO's job for his (reprehensible) Prop-8 donation.

Everyone wants to believe that's true, because fits nicely into narratives a number of invested camps want to believe, whether it's somebody being ousted for reprehensible views the woke SJW mob somehow pulling down a great leader (tm) but that's not what happened.

Dieser Beitrag wurde bearbeitet. (3 Tage her)
Als Antwort auf mhoye

At the time, maybe still today, the largest-by-far donors supporting the Foundation were a financially-very-successful gay couple, I believe New York-based financiers whose names escape me, and who IIRC had the ears of a number of other prominent donors. A significant chunk of the Foundation's even-then modest budget came from that, and when this blew up, it put the entire financial structure of Mozilla as not-beholden-to-shareholders, privately-held-by-a-not-for-profit entity at risk.
Als Antwort auf mhoye

After what I'm told was a few days of very difficult negotiation under extraordinary pressure, both internal and external, a deal was struck. and the plan was that Eich make an announcement, apologizing for his "mistake" and making some public-benefit commitment about inclusivity, importance of diversity, etc.

Half the board resigned.

He takes his public drubbing, and he gets his company. The structure of the organization survives, the mission lives.

At the last minute, he reneged.

Dieser Beitrag wurde bearbeitet. (3 Tage her)
Als Antwort auf mhoye

Now, I have some feelings about the situation. That bullshit graph he's aired out about Mitchell's salary versus market share carefully omits the fact that he was CTO for most of that time, presiding over a long period of technical stagnation, and had never directly managed more than a handful of people in his career. It wasn't until new leadership and Firefox 57, the Quantum release, that Firefox became performance-competitive again.
Als Antwort auf mhoye

But the real reason wasn't that he made a donation to some reprehensible cause. The real reason he lost his job was because he showed everyone who mattered that when the chips were down - and I mean, 100%, the whole table has pushed their chips the way in down - that he'd put his own pride or vanity who gives a fuck what ahead of the continued existence of the company and the mission.
Als Antwort auf mhoye

When he later announcing his resignation as Firefox module owner and mentioning Brave, he sent mozilla.governance email about how he'd compared other engines to Gecko on all sorts of axes and how Electron/Chromium was superior on all of them, and I can still remember staring at my reply, at the words "if only we'd had somebody at Mozilla for the last fifteen years, in some sort of technical leadership capacity, who might have been able to do something about that. Too much to wish for, I guess".
Dieser Beitrag wurde bearbeitet. (3 Tage her)
Als Antwort auf mhoye

Do you have a copy of that email? I don't remember receiving it, but what I'm sure is that the first versions of Brave were actually Gecko-based (using browser.html as the frontend), then Electron then Chromium, but never WebKit.

About Firefox becoming competitive only with Quantum... man, it was so cringe at the time to see the desktop team rediscovering what we learned from the work on b2g (both UI and platform) and that the desktop team fought so much against at the time.

Als Antwort auf Fabrice Desré

> and that the desktop team fought so much against at the time.

Citation needed? Desktop had _no resources_. (Almost) everybody was working on b2g. We were begging for scraps of people's cycles to work on our flagship product.

Dieser Beitrag wurde bearbeitet. (3 Tage her)
Als Antwort auf Mike Conley (:mconley) ⚙️

@mconley That's not true. Who from the desktop team was pulled into b2g? Your "flagship" still has no good distribution channel and is losing users, not just market share. That won't be fixed by making it a better product unfortunately because *users are somewhere else*.

Killing b2g after only shipping it for 2.5 years was so stupid for all of Moz, including Desktop.

(disclaimer: Fx Nightly is my default browser).

Als Antwort auf Fabrice Desré

@fabrice
Front-end engineers were being yanked in to work on Gaia. The entire Graphics team was so focused on b2g that the Australis re-theme was delayed by _months_ so we could work through graphics performance issues with them. You have no idea what it was like to work on desktop during those years.

I know you're bitter about b2g at Moz, but it happened. Take the L. Move on.

Disclaimer: I used a reference FxOS phone for a year as my primary.

Als Antwort auf Mike Conley (:mconley) ⚙️

@mconley I'm bitter about people defending Baker/Mayo/Bryant blindly without realizing how much damage they did, yes. Had they honored their word to keep it as a community project / Tier3, they could have reaped the India market a mere 2 years later.

Complaining about months of delay on gfx is ridiculous in the grand scheme of things, and you know it.

Als Antwort auf Fabrice Desré

@fabrice @mconley
From the 1.0 push up through the disastrous Florida all-hands the majority of engineering resources were dedicated to b2g projects.

My team of about 8 was down to 1 person each working on Firefox for Android and Firefox iOS. Even then myself and Aaron would be pulled into b2g testing for weeks at a time.

Similar sort of story for our contracting team.

Als Antwort auf Kevin Brosnan

@kbrosnan @fabrice I remember sitting in a meeting with Mark Mayo with a graph showing us that 40% of Mozilla's resources were dedicated to b2g at its peak. The picture you and @mconley are painting sounds more like 90%. Either way this means that top management was completely out-of-the-loop both with regards to b2g and desktop.

I've always attributed our failure to mismanagement and now I'm even more convinced of that.

Als Antwort auf Gabriele Svelto

@gabrielesvelto @kbrosnan @fabrice @mconley

I realise this thread has strayed way off its original topic, but... hot take:

Mozilla should bring back Firefox OS.

Putting decade-old company politics aside it was the most innovative and potentially disruptive thing Mozilla ever built, before and since, and is needed now more than ever.

For smartphones maybe, but also all manner of other smart devices where owning the OS is the only effective way to disrupt the incumbents.

Als Antwort auf Ben Francis

@benfrancis @gabrielesvelto @kbrosnan @fabrice @mconley

Counterpoint: FirefoxOS was a misguided project cancelled far, far too late. It had no shot whatsoever, and its principal utility was letting phone OEMs get an extra two years out of existing product lines at the low end. CPU performance curves made investing a ton of effort to make things work on the low end something that Apple could ignore entirely and Android could wait out, changing nothing.

Dieser Beitrag wurde bearbeitet. (2 Tage her)
Als Antwort auf mhoye

@benfrancis @gabrielesvelto @kbrosnan @mconley Google tried again recently on the low end with the "Jio Next" device based on Android Go. Guess what, it failed because Android Go is still bloated compared to b2g.

FxOS failed commercially because we could not get WhatsApp on board, and no WA meant no sales through carrier distribution channels. Then we gathered tons of ideas for a v3 that would be more "Mozilla centric" but the leadership chickened out.

Als Antwort auf Mike Conley (:mconley) ⚙️

@mconley @fabrice and not just firefox. Support teams like RelEng were pulled in over and over as well (in combination with b2g having their own folks doing things that we weren't equipped to do).
Als Antwort auf Mike Conley (:mconley) ⚙️

@mconley @fabrice from the "outside" that's how things looked and felt. From b2g the perspective was probably very différent.
Fabrice there's a post on linuxfr I can't fond right know from one of the Benoît explaining how things were. Try to fond it.
Als Antwort auf Mike Conley (:mconley) ⚙️

@mconley @fabrice
I recall Desktop/frontend (Firefox but not Gecko) being less than 10 people at the time, though both my memory and understanding at of the time were fuzzy. Once I understood the actual team distribution it seemed totally nuts how small desktop was.

I don't know what the right way would have been to run Firefox desktop and b2g in parallel, but whatever it was that wasn't it.

Als Antwort auf Fabrice Desré

@fabrice @ianbicking You're not listening. All resources were committed to b2g. We were in full-on skeleton-crew mode. There was _no budget_ to hire more people because b2g was taking all of the budget.

Complaining about Firefox Desktop not hiring enough people is ridiculous in the grand scheme of things, and you know it.

Als Antwort auf Mike Conley (:mconley) ⚙️

@mconley @fabrice @ianbicking Can confirm that if you weren't part of b2g, even if you were on a not-Firefox team like webdev/web prod, you basically got ignored. It was a superb waste of time born of thinking that Mozilla was a great generalized tech company and not just a great browser and developer tooling company.
Als Antwort auf mhoye

@freddy Too much bile and obvious hate for this to read as a credible account
Als Antwort auf Nadim Kobeissi

@nadim I worked there back then. I know Mike. You know me. 🤷
At the same time, everyone has their biases and gripes and opinions. That’s OK.
Als Antwort auf Nadim Kobeissi

@nadim
It reads as perfectly credible to me. People are allowed to have negative reactions to bad experiences. Expecting them to conceal their legitimate feelings for some kind of faux-neutral performance may be to your tastes, but to me it diminishes trust.

@mhoye @freddy


Wilhelm hat dies geteilt


As the last U QPR2 shipping blocker has finally been resolved, we are resuming LineageOS 21 builds starting today!
Als Antwort auf Thomas

@cantences it's up to device maintainers to sign off on devices that have been dropped.
Als Antwort auf Thomas

@cantences in xda xdaforums.com/t/official-linea… @luk1337
Als Antwort auf Kurt

@Kurt

Sadly, this device utilizes android.hardware.radio@1.3 (or below).

This means that the March security bulletin - known as #QPR2 - fully killed this device.

We (LineageOS) are trying to write a wrapper to make older radio HAL versions compatible with newer radio HAL versions.

With that said, we may or may not be successful and we're entirely unsure how long it would take.

So, sadly, for now, this device has 21 builds disabled - I have deployed one final February ASB unofficial build people can use in the intermediary (or you can use the final official build).

I will announce here if/when the device is re-added to the roster.


Wilhelm hat dies geteilt


A hacker group called Cyber Army of Russia posted videos in which it tampers with control software for US water utilities, a Polish wastewater plant, and a French hydroelectric dam.

Now a report from Mandiant ties the group to Sandworm, a unit of Russia’s GRU military intelligence agency. wired.com/story/cyber-army-of-…

Als Antwort auf Andy Greenberg

We updated this story with absurd news from Le Monde: The French "hydroelectric dam" Cyber Army of Russia claimed it targeted was in fact a small water mill in a village of 300 people.

More evidence this is likely not Sandworm proper, but a loosely linked junior varsity team.

Als Antwort auf Andy Greenberg

Cyberattacking the right dam is hard, apparently. Back in 2013 Iranian hackers famously hacked the control systems for the 22-ft tall Bowman Dam in New York State, probably thinking they were attacking the 240-ft tall Bowman Dam in Oregon. newyorker.com/tech/annals-of-t…
Als Antwort auf Andy Greenberg

obviously they should just do what sysadmins do when they can't figure out where a system is: run a command to eject the CD-ROM drive.
Als Antwort auf Dave Wilburn :donor:

@DaveMWilburn you do that on the wrong dam though and water shoots out through the little hole in the tray and makes a big mess
Als Antwort auf Andy Greenberg

It should not be possible to hack this Dam via the internet.

Everyone involved in decision making, leading to this, needs to add to their list of questions.

Why would controlling critical infrastructure, from anywhere in the world, be a thing anyone but a bad-person needs to do?

It'd also be way too much stress to manage all the worlds critical infrastructure.


Wilhelm hat dies geteilt


What kind of User Interface are you using?

  • Classic Toolbars/Menus (54%, 272 Stimmen)
  • Notebookbar Tabbed (24%, 123 Stimmen)
  • Other Notebookbar variants (1%, 8 Stimmen)
  • Didn't know of any alternative (19%, 100 Stimmen)
503 Stimmen, Abstimmung endet: in 3 Tage

Als Antwort auf LibreOffice Design

Standard works well for me. I am not so keen on Tabbed interfaces, I don't think they are practical when a window size changes.
Als Antwort auf LibreOffice Design

I use Classic, except when I switch to only showing my document's contents...

Wilhelm hat dies geteilt


Mozilla Firefox 125 Released with Added Conveniences

You know the drill by now: a new month rolls around, and a new version of the inimitable Mozilla Firefox rolls off the release server for us all to enjoy. And bang on cue, Firefox 125 has arrived. The big-ticket new feature in this update is URL paste suggestions: Mozilla says this feature “provides a convenient way for users to quickly visit URLs copied to the clipboard in the address bar of Firefox.” How does it work? If you copy a URL to the system clipboard and then focus the URL bar (in Firefox 125, that is) you will see :sys_more_orange:
#News #AppUpdates #Firefox

:sys_omgubuntu: omgubuntu.co.uk/2024/04/mozill…



Good #LibreOffice news:

"Patrick Luby (NeoOffice) fixed issues related to the transparency-to-alpha rework, fixed a Skia issue related to a changed default, fixed horizontal swiping and scrolling when using an RTL UI, made it possible to encrypt files with using public GPG keys with unknown Ownertrust on macOS and fixed macOS crashes"

This is item # 27 in the monthly dev / qa report: qa.blog.documentfoundation.org…

And it means that for the first time for as long as I can recall, #OpenPGP in @LibreOffice on #macOS is in an actual usable state 😮

Kudos Patrick for your persistence in addressing the nasty issues around this implementation.

Dieser Beitrag wurde bearbeitet. (4 Tage her)

Wilhelm hat dies geteilt


#Apple and #Google have hijacked passkeys to keep users locked into their walled gardens.

Here's how we can make #passkeys work for everyone: proton.me/blog/big-tech-passke…

Als Antwort auf tim cappalli

@timcappalli Are they?

Are we sure it's not just cloud sync for that vendor's platform? Ex: Apple to iCloud and Google to Google Drive?

Last I heard/read was that users would still have to create another passkey for new "custodians."

fidoalliance.org/passkeys/

Als Antwort auf Avoid the Hack! :donor:

@avoidthehack there are two standard protocols being developed for migration between passkey providers, with over 10 providers involved in the work, including Google and Apple. It is not related to sync.
Als Antwort auf tim cappalli

Interesting. I wonder if you'll be able to export the passkey to your own storage or if it has to be custodian-to-custodian port.
Dieser Beitrag wurde bearbeitet. (1 Woche her)
Als Antwort auf Avoid the Hack! :donor:

@avoidthehack you should pick a passkey provider that allows you to do that. I doubt that secure by default passkey providers would allow regular consumers to shoot themselves in the foot like that. If you're a power user, use a provider that gives you more knobs.
Als Antwort auf tim cappalli

We wouldn't know until they actually roll it out to be fair, I am just spitballing considering the closest thing I can think of to something similar we have now are ssh keys.

In theory custodians could never allow an unencrypted export of the key per protocol, who knows.

Edit: Meant to say I use Bitwarden so it is a non-issue currently.

Dieser Beitrag wurde bearbeitet. (1 Woche her)
Als Antwort auf Avoid the Hack! :donor:

@avoidthehack there are providers who are waiting for the credential migration protocol to finalize and there are some providers who are unfortunately just dumping to plain text with no protections, which is irresponsible.
Als Antwort auf tim cappalli

I find this argument a bit problematic. Just because software like @Team KeePassXC gives users control and choice over their passkeys, which Apple / Google / ... currently don't, doesn't mean they are irresponsible. From what I can tell KeePassXC devs were not involved in the discussions around transfer of passkeys.

Big tech wanted to get passkeys into user hands, which is a great thing, as are passkeys in general. But the statement that it is somewhat of a lock-in situation currently is not false.

And finger-pointing at software that does give users the option to transfer passkeys at their desire is not helping I think. Especially when that aspect has not yet been standardized.

If transfer can happen in encrypted form, that is clearly preferable. You filed github.com/keepassxreboot/keep… which is a good thing. The discussion shows however, that the way the debate was going on so far was not ideal.

#passkeys #security #passwordless

Dieser Beitrag wurde bearbeitet. (1 Woche her)
Als Antwort auf tim cappalli

@timcappalli glad to hear that! As portability is one of the larger dealbreakers for a lot of people, I'm really looking forward to reading it!

Wilhelm hat dies geteilt


In case anyone from @1password is reading this, you may want to get in touch with me. I have reported a security vulnerability via their bugbounty program, and bugcrowd's staff thinks it's "not applicable", in my view clearly misinterpreting the program's rules. I am pretty sure it's something they want to address. I may consider other means of disclosure if this is "not applicable" for their bugbounty program..
Als Antwort auf hanno

Hey Hanno! 1Password is committed to strong security practices. This is why our Security team leverages BugCrowd escalation paths and our own regular internal review of submissions to ensure we are continually assessing the safety and security of our solutions.

Researchers with questions or concerns can email bugbounty@agilebits.com to directly reach our security team responsible for the program.

For more details check out our program brief at bugcrowd.com/agilebits