saint

joined 3 years ago
MODERATOR OF
 

Movies mentioned:

  • Black Orpheus
  • Bruce Lee (Box Set) -Battle of Algiers
  • Sambizanga
  • Muna moto
  • Drylongso
  • Watermelon Woman
  • Saint Omer
  • Emitaï
  • Xala
  • Ceddo
 

Nobody seems to notice... nobody seems to care..

 

Russian leaders and propagandists have at once denied the existence of a Ukrainian nation and called for purging or cleansing the Ukrainian territory, in terms that often mirror rhetoric preceding past genocides. In this report, the authors seek to shed light on how Russia's extremist, hate-peddling narratives deployed in the war have spread online through social media.

Russian propaganda is making inroads into some of the major European languages—Spanish and German, as well as French and Italian.

REMVE narratives are also finding more-receptive audiences among relatively small linguistic communities in Eastern Europe. Serbian- and Bulgarian-language communities emerge as particularly vulnerable to cross-language and cross-cultural transmission of REMVE messages on both X and Telegram.

However, Russia's ability to successfully mainstream its propaganda and mobilize its audiences against Ukrainians is limited: The most virulent REMVE conversations on these two platforms remain highly Russian-language dominated, are concentrated in specific communities, and do not draw much attention from others in the networks.

Full research report: https://www.rand.org/content/dam/rand/pubs/research_reports/RRA3400/RRA3450-1/RAND_RRA3450-1.pdf

[–] [email protected] 3 points 1 month ago

no, no and no, but you will have to find an answer if your decision to have or not to have kids was the right choice in any case.

 

If you left alone in the office and have nothing better to do..

 

The incoming Trump administration has been supportive of this European initiative. It is consistent with the president-elect's stated desire to disengage the United States from security matters on the continent, and instead have the European Union and the United Kingdom take the lead. But a deployment of European forces to Ukraine will inevitably entangle the Americans. European militaries depend on their U.S. allies for out-of-area operations. Inevitably, a large deployment to Ukraine will once again expose this dependency when they turn to the United States for help with critical tasks such as air lift, logistics, and intelligence that they cannot conduct alone.

 

The Ukrainian military faces critical challenges that demand immediate, honest evaluation:

  • Infantry roles becoming increasingly unsustainable

  • Recruitment system disproportionately burdens vulnerable populations

  • Command structures trapped in outdated bureaucratic frameworks

  • Morale gradually eroding under prolonged combat stress

  • No clear exit strategy for frontline soldiers

  • Commanders prioritizing reporting over human lives

  • Declining Western support momentum

  • Deeply entrenched leadership inefficiencies

Suggested changes:

  • Implement merit-based officer promotion systems
  • Establish fixed, transparent service terms
  • Rebuild trust between military leadership and soldiers

More in the article.

 

According to the article, Danieli continues to operate in Russia despite EU sanctions, collaborating with steel giants like Severstal and MMK, both linked to military production. Danieli reportedly uses its Chinese subsidiary to bypass sanctions, enabling the supply of equipment to Russia. In 2023, its Russian subsidiary’s cash flow increased 35-fold, contradicting claims that the business is unprofitable or disconnected from the military sector. The company’s justification hinges on technicalities, but the financial and strategic realities suggest complicity in sustaining critical industries that support Russia’s war economy. At what point does this move from legal maneuvering to outright enabling?

 
  • Companies are earning billions while pushing for automation that cuts jobs.
  • Automation is replacing workers across industries, from shipping terminals to retail. “Who pays taxes when machines replace workers?”
  • A dockworker strike could halt the economy.

I think automation is unavoidable, but what is next?

 

The CALEA system, designed in the U.S. for mass surveillance, has become a global threat. Telecom equipment with "back doors" isn't just an American issue—it's a worldwide risk. Trusting the "good guys" is naive; any end with "back doors" can be a target. Encryption is our defense, and we must be careful about what we buy. #security #technology

 

How Base 3 Computing Beats Binary

Metadata

Highlights

Three, as Schoolhouse Rock! told children of the 1970s, is a magic number. Three little pigs; three beds, bowls and bears for Goldilocks; three Star Wars trilogies. You need at least three legs for a stool to stand on its own, and at least three points to define a triangle.

If a three-state system is so efficient, you might imagine that a four-state or five-state system would be even more so. But the more digits you require, the more space you’ll need. It turns out that ternary is the most economical of all possible integer bases for representing big numbers.

Surprisingly, if you allow a base to be any real number, and not just an integer, then the most efficient computational base is the irrational number e.

Despite its natural advantages, base 3 computing never took off, even though many mathematicians marveled at its efficiency. In 1840, an English printer, inventor, banker and self-taught mathematician named Thomas Fowler invented a ternary computing machine to calculate weighted values of taxes and interest. “After that, very little was done for years,” said Bertrand Cambou, an applied physicist at Northern Arizona University.

Why didn’t ternary computing catch on? The primary reason was convention. Even though Soviet scientists were building ternary devices, the rest of the world focused on developing hardware and software based on switching circuits — the foundation of binary computing. Binary was easier to implement.

 

Highlights

The first scaling crisis happened in 1996, when Linus wrote that he was "buried alive in emails". It was addressed by adopting a more modular architecture, with the introduction of loadable kernel modules, and the creation of the maintainers role, who support the contributors in ensuring that they implement the high standards of quality needed to merge their contributions.

The second scaling crisis lasted from 1998 to 2002, and was finally addressed by the adoption of BitKeeper, later replaced by Git. This distributed the job of merging contributions across the network of maintainers and contributors.

In both cases, technology was used to reduce the amount of dependencies between teams, help contributors keep a high level of autonomy, and make it easy to merge all those contributions back into the main repository, Bernhard said.

Technology can help reduce the need to communicate between teams whenever they have a dependency on another team to get their work done. Typical organizational dependencies, such as when a team relies on another team’s data, can be replaced by self-service APIs using the right technologies and architecture, Bernhard mentioned. This can be extended to more complicated dependencies, such as infrastructure provisioning, as AWS pioneered when they invented EC2, offering self-service APIs to spin up virtual servers, he added.

Another type of dependency is dealing with the challenge of merging contributions made to a similar document, whether it’s an illustration, a text, or source code, Bernhard mentioned. This has been transformed in the last 15 years by real-time collaboration software such as Google Docs and distributed versioning systems such as Git, he said.

Anyone trying to scale an agile organization should study lean thinking to benefit from decades of experience on how to lead large organizations while staying true to the spirit of the agile manifesto, he concluded.

 

Good slides on how to reduce risks

[–] [email protected] 3 points 3 months ago (1 children)

Būtų įdomu paskaityt tai kas ten iš tiesų įvyko ir kaip buvo tvarkoma, bet turbūt Cloudflare lygio post-mortem analizės tikėtis neverta.

[–] [email protected] 1 points 3 months ago

What about it? ;)

[–] [email protected] 1 points 4 months ago

Not anymore, nowadays, I feel guilty reading non-fiction and understand Lindy effect on books much better (be it fiction or non-fiction).

[–] [email protected] 26 points 4 months ago

They cut all such scenes and pasted into The Boys, in a Mark Twain style “Sprinkle these around as you see fit!”.

[–] [email protected] 2 points 5 months ago

I liked the book as well. The show had some similar feeling in some ways, but also had a distinct character for itself.

[–] [email protected] 2 points 6 months ago

A Tomb for Boris Davidovich - Danilo Kiš

[–] [email protected] 1 points 8 months ago

Reread today again, with some highlights:

Lessons Learned from Twenty Years of Site Reliability Engineering

Metadata

Highlights

The riskiness of a mitigation should scale with the severity of the outage

We, here in SRE, have had some interesting experiences in choosing a mitigation with more risks than the outage it's meant to resolve.

We learned the hard way that during an incident, we should monitor and evaluate the severity of the situation and choose a mitigation path whose riskiness is appropriate for that severity.

Recovery mechanisms should be fully tested before an emergency

An emergency fire evacuation in a tall city building is a terrible opportunity to use a ladder for the first time.

Testing recovery mechanisms has a fun side effect of reducing the risk of performing some of these actions. Since this messy outage, we've doubled down on testing.

We were pretty sure that it would not lead to anything bad. But pretty sure is not 100% sure.

A "Big Red Button" is a unique but highly practical safety feature: it should kick off a simple, easy-to-trigger action that reverts whatever triggered the undesirable state to (ideally) shut down whatever's happening.

Unit tests alone are not enough - integration testing is also needed

This lesson was learned during a Calendar outage in which our testing didn't follow the same path as real use, resulting in plenty of testing... that didn't help us assess how a change would perform in reality.

Teams were expecting to be able to use Google Hangouts and Google Meet to manage the incident. But when 350M users were logged out of their devices and services... relying on these Google services was, in retrospect, kind of a bad call.

It's easy to think of availability as either "fully up" or "fully down" ... but being able to offer a continuous minimum functionality with a degraded performance mode helps to offer a more consistent user experience.

This next lesson is a recommendation to ensure that your last-line-of-defense system works as expected in extreme scenarios, such as natural disasters or cyber attacks, that result in loss of productivity or service availability.

A useful activity can also be sitting your team down and working through how some of these scenarios could theoretically play out—tabletop game style. This can also be a fun opportunity to explore those terrifying "What Ifs", for example, "What if part of your network connectivity gets shut down unexpectedly?".

In such instances, you can reduce your mean time to resolution (MTTR), by automating mitigating measures done by hand. If there's a clear signal that a particular failure is occurring, then why can't that mitigation be kicked off in an automated way? Sometimes it is better to use an automated mitigation first and save the root-causing for after user impact has been avoided.

Having long delays between rollouts, especially in complex, multiple component systems, makes it extremely difficult to reason out the safety of a particular change. Frequent rollouts—with the proper testing in place— lead to fewer surprises from this class of failure.

Having only one particular model of device to perform a critical function can make for simpler operations and maintenance. However, it means that if that model turns out to have a problem, that critical function is no longer being performed.

Latent bugs in critical infrastructure can lurk undetected until a seemingly innocuous event triggers them. Maintaining a diverse infrastructure, while incurring costs of its own, can mean the difference between a troublesome outage and a total one.

[–] [email protected] 0 points 9 months ago

This is what you get when are not sleeping during biology classes.

[–] [email protected] 2 points 9 months ago

not a bug, but a feature :))

view more: next ›