Just create a pacman hook before install that uploads the package there and aborts installation if necessary. Probably skipping repo packages is a good idea otherwise you're gonna spam the API each update.
I had to move to Brave/Vanadium on Android because Firefox is slow as hell. It happens when you log in, which for me is the whole point, as that's what I use on my computer (Linux).
They really should be a LOT clearer about it on their homepage, 99.99% of "original" browsers tend to be a wrapper around Chromium.
And as someone who actually lived through the "IE is the standard, deal with it" - age, I refuse to use any Chromium based browser out of principle. We need more actually viable engines in use or Google will just keep dictating what's allowed on the internet by the fact that Chrome has something like 90% market share on desktop browsers.
It's a difficult read, so let me paste here what Claude Sonnet 4 summarised:
Based on this comprehensive report on the April 28, 2025 electrical blackout in Spain, I can summarize the key reasons why it happened:
## Primary Cause: Voltage Control Crisis
The blackout was fundamentally caused by *insufficient dynamic voltage control capacity* in the system, which led to a catastrophic "chain reaction" of overvoltages. Here's how it unfolded:
### The Perfect Storm of Contributing Factors
*1. Inadequate Voltage Control Resources*
- Only 11 thermal power plants were coupled with voltage control obligations (the lowest number recorded in 2025)
- One planned voltage control plant in the southwest failed the previous evening and wasn't replaced
- Several connected plants didn't provide expected reactive power absorption during critical moments
*2. System Oscillations Weakened the Grid*
- Multiple oscillations occurred throughout the morning (starting at 5:49 AM)
- Two major oscillations at 12:03 PM (0.6 Hz) and 12:19 PM (0.2 Hz) significantly stressed the system
- The first oscillation was traced to anomalous behavior at a specific photovoltaic installation
- Measures taken to dampen these oscillations (increased grid meshing, reduced interconnection flows) inadvertently contributed to voltage increases
*3. The Fatal Chain Reaction (Phase 2-3)*
Starting at 12:32 PM:
- Voltages began rising rapidly across the transmission network
- Generation facilities started disconnecting due to overvoltages, beginning with renewable plants
- Each disconnection removed reactive power absorption capacity and reduced line loading
- This caused further voltage increases, triggering more disconnections
- The process accelerated into an unstoppable cascade
### Key Timeline
- *12:32 PM*: Sustained voltage increases begin
- *12:32:57*: First major generation loss (355 MW at Granada)
- *12:33:16*: Second major loss (730 MW at Badajoz)
- *12:33:17*: Third major loss (550 MW at Sevilla)
- *12:33:30*: Complete system collapse to zero voltage
### Why Couldn't It Be Stopped?
Once the chain reaction began, stopping it would have required massive reactive power absorption capacity that simply wasn't available. The system's protective mechanisms (like demand disconnection) actually made the overvoltage problem worse by further reducing grid loading.
## Broader Context
The report emphasizes this was a *multifactorial event* - no single failure explains it entirely. Contributing factors included:
- Low electrical demand creating capacitive effects in the highly meshed grid
- Quarter-hourly market changes causing rapid generation adjustments
- Spain's weak interconnection with Europe (only 3% vs. 15% target)
- Complex renewable evacuation infrastructure with inadequate protection settings
The restoration process took until 7:00 AM the next day to reach 99.95% supply restoration, though it was considered exemplary by international standards.
As vanilla Arch is sort of a meta-distro, it would largely depend upon what the user chose to install and use. For any one of the many spins of Arch, maybe? But one would need to audit each individually.
Sure, they exist, but Signal is against them. Look into what they did against LibreSignal.
Now part of the problem with LibreSignal was the trademark violation of using the name Signal. But Moxie is clearly against any third party using their servers, as we can see in this comment: https://github.com/LibreSignal/LibreSignal/issues/37#issueco...
IMO that's an unforgivable stance towards third party clients.
I have read (well, skimmed) through their terms of service and haven't seen anything against using their servers from third party software, yet they'll evidently shut down third party software for interacting with their servers. If you're gonna have policies like that, at least outline them in your ToS.
As mentioned in the thread and expanded on the blog [0] moxie is also against the whole idea of federation and multiple clients.
I think my perception has changed in the last ≈ 10 years, to be more leaning in moxie's direction. It's hard enough to design something secure and usable, having to try and support all different implementations under the sun makes most federated approaches never reach any mass adoption.
Even though it's not a one-to-one analog I also think e.g the lack of crypto agility in Wireshark was a very good decision, the same with QUIC having explicit anti-ossification (e.g encrypted headers). Giving enterprise middle boxes the chance to meddle in things is just setting things to hurt for everyone else.
I don't think it's a problem that they're against federation. I think federation is nice, but it has some clear trade-offs, and I don't feel like it's something Signal needs.
I don't even think they have to officially support third party clients or provide a stable API. I'd have no problem if they just occasionally made API changes which broke unofficial clients until their developers updated them.
But I really don't like that they're so openly hostile to the idea of other people "using their servers for free", with the threat of technical blocks and legal action which that implies. Especially not when their official client is as bad as it is. (Again, it's fucking blurry!)
reply