taleodor

Check ReARM we're building for durable tracking of releases, software updates and fulfilling 10+ years obligations - https://rearmhq.com

Small and cheap cloud VM, preferably on a separate account used for this purpose specifically.

This is more about understanding the big picture and architecture of what's going on (the part about the diagrams / blueprints). One practical thing actually that may be useful to you - try thinking and testing in terms of "what can go wrong" rather than "is this prod-ready".

If you're planning to put it into production anything you do outside of bringing somebody qualified at this point is likely a waste of time. Highly recommend this recent talk by Kelsey Hightower on the subject - https://www.youtube.com/watch?v=A7WFt2JQ5sg

Full CRA requirements kick in in December 2027. Reporting obligations kick in in September 2026. Would probably make sense to update the website timer to reflect December 2027 deadline which is more relevant here.

Did you try working with CycloneDX AI/ML BOM group? This would be good place to contribute.

We support this with ReARM - https://rearmhq.com/

It's an open-core product (there is an option to self-host FOSS ReARM CE yourself) that gives you per-release vulnerability posture. It consumes various artifacts (e.g., SBOMs) generated during CI phase and does scan on them, doesn't need access to source code. Apart from SBOMs it consumes files with findings from other tools (reports in SARIF format, VDRs, VEXs).

Very cool, we're doing similar except we let agents open PRs as well + we track release metadata and agentic sessions via our ReARM system + we've recently launched an option for agents to track helm-based deployments via ReARM - https://docs.rearmhq.com/workflows/devops.html

It's not about that we should drop LLM completely from the mix, but something like AI -> LLM control -> old-school classifier control -> script / human oversight is the way. If something has potential to cause millions in damages, it should be subjected to human oversight (likelihood / impact analysis needs to happen early in the system design).

Frankly I don't buy atrophy argument at all. I (and I believe many other people) switched multiple frameworks and languages over the years. I.e., I was an expert in Chef more than 10 years ago, and nowadays I hardly remember anything about it. Calling this a cognitive decline is a significant stretch.

If you're afraid of cognitive decline - try to get to proper orchestration using multiple agents. That's a fun exercise.

If you're looking for practical recommendations how to work with npm maintaining reasonable safety expectations, my post here mostly covers it: https://worklifenotes.com/2025/09/24/npm-has-become-a-russia...

I have completely opposite experience. To me Traefik is the easiest thing to work with on the market. It should be even easier now to setup using Agentic AI.

Packaged version of Verdaccio that includes quarantine filter over npm - https://github.com/relizaio/dockerfile-collection/tree/main/...

I generally like analogy between technology (software and hardware) and construction, but I don't think it holds in regards to security - and real-world examples periodically prove that.

Hi all, we just launched Community edition of our tool to manage Bills of Materials. It supports storage of Bills of Materials on any OCI-compatible registry with rich support for branching and product-component composition.

Product website: https://rearmhq.com

This link you are sharing is an example of low quality journalism or propaganda - whatever you want to call it.

I'll give you some context - in 1948 Egypt declared war on Israel, which ended with a cease fire in 1949. From this context, it should become obvious that Israeli espionage operations in Egypt in early 1950s are warranted.

Even Avi Shlaim referenced in your article admits that it was mainly Arab nationalists who were driving the Jews out. These reactions are very similar to modern day shootings at Jewish schools in Canada or airport pogrom in Dagestan - https://www.bbc.com/news/world-europe-67258332

Pro-Palestinian crowd is unable to admit that they have imperfections and blames all these events on Israel / Zionists as well (I read a lot of forums from both sides). A common reference is "they made us do it" / "it was a Zionist school / plane". Drawing parallels between today and 1950s, it becomes very clear that it's old propaganda playbook trick. I would go even further and say it's a millenia-old antisemitism, where people would blame everything on Jews / witches / etc.

Now, back to the article you shared - "undeniable proof" - is an interview of a 89-year old man, who did not even hold the leadership role in an underground Jewish cell and did not claim first-hand participation in any of the events. More so, his interview is full of contradictory statements, including dates and attributions of who did what - I encourage you to do more research on that.

So on one hand, you have this "undeniable proof", and on the other hand you have many well documented actions of Arab nationalists and Iraqi government. And you choose to believe (even contradictory to Avi Shlaim) that it's all Zionists.

Next, thinking logically, there was no need for Mossad to do false flag operations, because there were enough actions by Arab nationalists and before 1950 there was a policy in place by Iraqi government banning Jews from emigrating to Israel - like if Jews didn't want to emigrate, why would they ban this? Once they lifted the policy, everybody left. This is very similar to USSR where millions of Jews left in early 1990s after the fall of the USSR. Probably propagandists will soon be explaining that this was Mossad false flag operations or some other Zionist tricks - I wouldn't be surprised.

> It would be fantastic to see a single Israeli/Palestinian state with a slight arab majority, but everyone with their voice represented, all living in peace and harmony.

Single state is a construct of few people with far-left views. They already tried something like that in USSR where they put for example Armenians and Azerbaijanians in the same state (and many other smaller examples within USSR). Look what happened.

I don't see even a single chance this will ever work, also it has zero support on the ground by both sides.

> More generally, the demographics around the Eastern Mediterranean have changed surprisingly little since the Bronze Age.

This type of claims only shows lack of understanding of history as a science. It is actually impossible right now to make claims about this with any significant degree of confidence.

A system to manage software metadata and SBOMs in particularly. This is based on our existing relizahub.com and will implement upcoming Transparency Exchange API - https://github.com/CycloneDX/transparency-exchange-api/

A lot of people are in lower income brackets and don't have the means nor understanding where and how to leave the country.

Another big factor is that many countries have essentially closed borders for Russian nationals - i.e. US is now deporting those who are fleeing - https://www.theguardian.com/us-news/2023/mar/18/biden-admini...

There are also few people who do want to stay in Russia and try to fight Putin there (like Navalny or Yashin).

Their bank accounts were frozen for torturing Ottawa downtown residents and lawlessness that ensued. Not for protesting lockdowns.

Look at https://spectre.app/

Currently there are no flights and frequently no way to get visas, also MasterCard and Visa cards are no more in Russia.

DevOps and DataOps discord - https://devopscommunity.org

About 300 thousand Russians fled the country recently. There are almost no Russian tourists anywhere at the moment.

Thanks, I'll explore if this works for all standard use-cases, will update recommendations accordingly if all is good there.

Part of the functionality we built in Reliza Hub is to generate automatic version increments that are guaranteed to be unique on each request and have special rules for versioning on feature and release branches.

My usual versioning convention for a feature branch is BRANCH_NAME.PATCH

Generally, I believe getting versioning right requires an external versioning service that ensures uniqueness and routing between branches. Otherwise there will always be "gotchas".

We work on a solution - https://relizahub.com

Our community Discord Server (questions on DevOps and DataOps, not limited to Reliza Hub) - https://discord.gg/UTxjBf9juQ

Cheapest would be Google App Engine - see more detailed comparison here - https://worklifenotes.com/2020/05/24/google-app-engine-githu...

This one is pretty great - https://www.coursera.org/learn/crypto

Unfortunately, they never released the 2nd part on Coursera - so you'll still have to research for a lot of concepts after this course. But nonetheless, this 1st part provides a solid foundation.