Alma is on a mission to simplify access to high-quality, affordable mental health care

Alma

I recently spoke with Matan Almakis, the Head of Project at . In our conversation, we discussed the challenges of transparency in systems, balancing privacy and compliance, and ensuring ethical governance in a decentralized ecosystem. We also touch on the future of the crypto industry and what it will look like in the next five to ten years. I hope you enjoy it. Data Ownership Protocol blockchain Hello Matan. It’s great to have you for this conversation. Let’s begin with your origin story. Thanks for inviting me. I’m stoked to share my story and talk about all the cutting-edge work we’re doing at Data Ownership Protocol (DOP). My professional journey began in the blockchain space around 2021. At the time, I was a researcher at Lamina, Israel’s first IoT-focused Layer-1 blockchain. You could say this was also when I truly explored my knack to drive growth for pioneering blockchain startups and help them reach their full potential. As someone with a B.A. Degree in Social Sciences and Sociology, I’m always looking to solve real-world problems through whatever I do. And then, I did an M.A. in Organizational Development and Consulting, which gave me the skill set to build companies. By combining the two, I could embark on a journey to build startups that solve problems for the masses, as we’re doing at DOP. I’ve been with them since July this year. It’s great to be a part of something big, something so visionary. We’re transforming data ownership completely, and that’ll impact many lives in many different scenarios. And part of my job role is to make sure this happens the way it’s supposed to. Okay. So, transparency is often hailed as a USP for crypto and web3 protocols—it’s pretty much the holy grail for many. But resonating with Vitalik, among others, you point out the problems of over-transparency. Can you please elaborate on that? Sure. That’s a great question. First of all, transparency has its merits. The on-chain visibility that blockchain systems enable is indeed groundbreaking in many ways. It prevents black boxes, for instance. Plus, you can avoid manipulations or, for that matter, trace criminals. The Ilya Lichtenstein and Heather Morgan case is an example here. But from a privacy and autonomy perspective, transparency is a two-way sword. Because anyone can watch your on-chain activities, even with ‘ ’ identities, digital privacy effectively goes for a complete toss. pseudonymous More so, with advanced analytics and sleuthing tools available in the market now. Joining the dots to link users and transactions, despite using privacy solutions like ZCash or Tornado Cash, has become pretty easy nowadays. Above all, as Vitalik highlighted in a recent research paper, existing on-chain privacy mechanisms are often in conflict with emerging compliance obligations. This compels users to play a zero-sum game: all or nothing. You either reveal everything or don’t use blockchain-based systems at all. That’s not done. Compliance and privacy can very well work together—we have proof. To continue that point, how are you solving the compliance-privacy conflict, and what does it mean for end-users? We’re pioneering user-controlled selective disclosures for on-chain data. That’s basically turning Vitalik’s theoretical vision into a practical solution for the mass market. Moreover, it’s about taking crypto privacy to the next paradigm, i.e., data ownership. Contrary to existing privacy solutions, DOP will help end-users access full data control, zero-knowledge KYC, and customized data disclosure. DOP users can also participate in the ecosystem’s development, building on top of our open-source framework. DOP is a way to empower crypto users by enabling them to only disclose as much information as they deem fit. For example, while paying a merchant, you can only show what coins you hold in your wallet without revealing the exact balance or past transaction details. Because your transactions aren’t altogether exposed to the public, you face lower risks of front running, social pressure, phishing scams, extortion, data scraping, etc. But the best part is that this doesn’t hurt compliance. Counterparties can verify whether the coins they’re receiving came from any known exploit or sanctioned entity. We can achieve this using ‘association sets’ and advanced zero-knowledge cryptography. It’s thus a win-win situation where we serve both ends: privacy and compliance. No conflict. No harm. Dealing with user data is tricky terrain where you have to ensure you are meeting ethical standards. How do you ensure that? Centralized control over the process of creating association sets and storing data are two of the biggest ethical concerns in our domain. We’re addressing both from the very beginning. DOP is committed to adopting decentralized frameworks to build a fully self-governing ecosystem where the community has the final say. We will further establish a DOP DAO to nominate a rotating committee of node operators, algorithmically, to monitor the platform for risks. Maintaining a shared blacklist of prohibited wallets will be a key responsibility of this committee. External entities and users can also flag concerning activities, submitting proposals, and investigation requests via dedicated channels. Finally, DOP will implement a token-based governance mechanism to let the community participate in the decision-making process. This crowd-sourced approach will ensure that DOP mitigates threats and risks without any centralized points of failure or control. You couldn’t have built something like this without facing technical challenges, could you? Please tell us about the major ones and how you’ve overcome them. Of course not. We faced not one but many challenges. Balancing privacy and compliance—the very basis of our solution—is a massive challenge in itself. No one has ever done that before, really. At least not at scale. But we found a way to make this possible with ECDSA hashing and zk-SNARKs, among other elements. Anyone interested in the details can read our white paper. We also had to ensure seamless cross-platform interoperability so that DOP is relevant across the board. Restricting users to a proprietary wallet would have been restrictive. Multi-wallet compatibility was thus a must-have for flexibility, familiarity, accessibility, and, most importantly, a rich user experience. That’s why we embedded universal compatibility into DOP’s technical architecture, making the protocol future-proof. Before parting, where do you see the crypto industry in the next five-ten years, and how does DOP fit into this roadmap? Crypto is still in its early days, and there’s a long road ahead. But despite all the noise naysayers create, especially when something negative happens on the fringes, this is the best time to be bullish. I see a very bright future—something altogether different from what we’re used to, something user-centric. And I say this with such conviction because the tools and systems we need for such a future are already coming around. From robust proof systems to data ownership solutions like DOP, most of the core stack will be ready in the next five to ten years. That’s when crypto and blockchain-based systems will become what the Internet is today, minus the flaws and faults. As for DOP, we’re super excited now that our technology is ready. We’ve recently deployed the Testnet for the public to get a glimpse of what’s coming. Starting off with Phase I—Private Transactions—this is the beginning of a revolution. The Testnet phase will be live till Q1 2024. We invite users and developers to explore the protocol, check for bugs, and provide feedback about the experience in general. We’re testing features that’ll be live on the Mainnet as well, so you get a complete picture from the get-go. Plus, to incentivize testers and early adopters, we’re distributing 1% of DOP’s total supply as testnet tokens. This will have a 2-year vesting period with monthly claims, which each unique tester will receive based on their wallet and IP address. There’ll be no double counting. We’ve worked hard to ensure a fair game. Happy testing. Happy building.

Solving the Hard Problems: A Conversation with Matan Almakis, the Head of Project at DOP

include aarch64 support for AWS AMIs, support for OpenNebula x86_64 and aarch64, and aarch64 support for Generic (cloud-init) Cloud images/OpenStack. AlmaLinux Cloud Images Links for downloads: https://wiki.almalinux.org/cloud/Generic-cloud.html General fixes and updates made across all cloud images: Added IPv6 support: https://github.com/AlmaLinux/cloud-images/issues/20 Fixed Ansible leftover files and directories: https://github.com/AlmaLinux/cloud-images/issues/24 AWS AMIs ARM64/Graviton support added to AMIs. AMIs are available both via the as well as . AWS Marketplace Community AMIs The following issues have been addressed for AWS AMIs: Fixed incorrect SELinux type on interface files and other system files after vmimport. https://github.com/AlmaLinux/cloud-images/issues/23 Fixed Machine ID duplication Added QEMU support for image builder Added Installed and configured AWS Systems Manager Agent Microsoft Azure AlmaLinux images are on Microsoft Azure including a global in-network set of mirrors. You can get more information on the . wiki Generic (cloud-init) Cloud Image/OpenStack include support for aarch64. You can read more about those, and how to download and verify those images, on the wiki. Generic cloud/OpenStack images You can also find information on how to . run the generic cloud image on your local machine OpenNebula Support is available for the cloud platform for both x86_64 and aarch64. See the for info. OpenNebula OpenNebula page Community Submit issues and pull requests to the . To learn about Cloud images and how to contribute, visit the and the . Cloud Images Repository on GitHub wiki Community Chat The Cloud Images are made possible by the community with their contributions, feedback, and bug reports. Ask any questions on the for any help and assistance. c ommunity forums

Exploring Updates to AlmaLinux's Open Source Project, Cloud Images

have been hard at work lately on a project surrounding container updates, new images, new registries, and distribution. Cloud and Containers SIG : All container images are available for both the x86_64 and arm64/v8 architectures. FYI Full UBI Compatible Container Set for Red Hat Universal Base Images (UBI). AlmaLinux provides fully compatible alternatives What is you may ask? UBI is meant to be OCI-compliant container base operating system images with complementary runtime languages and packages included. UBI Prior to UBI, developers would need to package their containerized app depending on the deployment target. This essentially made those containers not really all that portable. UBI allow you to essentially have a standard, repeatable build, and deployment for your code and application, regardless of deployment target. The UBI compatible images come in four variants: Minimal, Base, Micro, and Init. Here is a quick summary of what they offer: : The container image isn’t going away; it’s been updated. FYI Default : A minimal, compacted image that contains a limited package set and uses the microdnf package manager as a replacement for DNF. A minimal DNF uses libdnf and therefore doesn't require Python. This image is 52% smaller in size (37MB download, 102MB expanded). It is designed for applications that come with their dependencies bundled like GO, NodeJS, Java. Minimal Container image tag for Minimal (Platform): almalinux:minimal Container image tag for Minimal (UBI alternative): almalinux/8-minimal : An image designed to be a base for your containerized applications, middleware and utilities. The Base image includes some helpful OS tools like find, tar, vi, etc., and a full DNF stack. The systemd initialization system and access to free dnf repositories are fully available. Base Container image tag: almalinux/8-base : An even more minimized image. It is distributed without any package manager. The Micro image uses the package manager on the underlying host to install packages, typically using Buildah or Multi-stage builds with Podman. The Micro image is 82% smaller than the Base image and 68% smaller than the Minimal image. Since this image has only very few packages, it is more secure compared to other images. Micro Container image tag: almalinux/8-micro : For running multiple applications with an init system. As a default, systemd is enabled for use. Init Container image tag: almalinux/8-init Container Security/Package Updates, New Registries and Distribution In addition to all of the above, two of our images are available as images: and . Both of those have now been updated with the latest security fixes and package updates. Official Docker Hub Default Minimal : A general purpose (platform) container image that contains default packages and can be used as a drop-in replacement for the CentOS 8 image. Default Container image tag: almalinux:latest : A minimal, compacted image that contains a limited package set and uses the microdnf package manager as a replacement for DNF. A minimal DNF uses libdnf and therefore doesn't require Python. This image is 52% smaller in size (37MB download, 102MB expanded). It is designed for applications that come with their dependencies bundled like GO, NodeJS, Java. Minimal Container image tag for Minimal (Platform): almalinux:minimal Container image tag for Minimal (UBI alternative): almalinux/8-minimal All images are available at AlmaLinux's and . Docker Hub quay.io All AlmaLinux images will be published to AWS' Service in the future. If you're running container-based workloads on AWS on either ECS, EKS, or anywhere else really, AlmaLinux containers are available to you locally on AWS. ECR Container Registry More information coming soon about additional container registries and application specific images like Java JDK, NodeJS, and more. To learn more about AlmaLinux container images, you can check out the containers section of the . There you can find helpful information, details about each container, container tags, and links for the repositories for each image. AlmaLinux Wiki Containers are a lightweight version of the OS with an essential base for you to build upon. AlmaLinux container images are a method of building a containerized application and pushing it to the registry server to share and collaborate with others. Containers also provide some additional advantages for users like high reliability, security, and performance. Community Excellent work from an incredible Community on their contributions, questions, and comments on the issues. Especially two immortal community heroes, and putting in a lot of work. Bala Raman , Elkhan Mammadli You can join the community on the and the for any help and assistance, or to discuss anything mentioned here. AlmaLinux Community Chat AlmaLinux Community Forums You can also join the if you are a DevOps doer, containers are your A-game, you live in k8s, or just want to have a lot of fun building more containers, kubernetes operators, and a whole lot more! Cloud and Container SIG

AlmaLinux Container Images with Full RHEL UBI Compatibility

ANN Years of work and we’re ready to announce a product for you: Trader’s Almanac. I made 11% on six 3x ETFs in the last 22 days... ...and my boss is up literally 80% in a few months ;) Hey folks! Whatever taste you have in the back of your mind about Jare’s work, you should give special consideration for when I collaborate (and have my code reviewed, yadda yadda). You should also seriously consider Trader Almanac’s signals that are generated by the neuro-evolutionary artificial intelligence :) While we haven’t announced the launch of our first SaaS (which may not be the prettiest… but ‘tis functional) yet on our Discord, I thought I’d give my email subscribers and Hackernoon readers an exclusive first-chance to come onboard :) Hey! Mark! Guess what we’re trading? 3x ETFs of indexes n sh#t. Yesterday, the AI told me to close my open positions. Since then, the markets have gone insane and these instruments saw a 4-5% loss AFTER the AI told me to exit. Word to the Wise Now, I’ve since learned that I can instruct the SaaS to ONLY email me when there’s a change in the signals - truth be told, my total returns were hit by me not noticing the changed sentiment until after it hurt my total returns. What did it look like, after the dust settled? We’re $1500 USD up (even after down 4-5% in the last day) on $17649 CAD (or 13828.34 USD) - just about 11% over 22 days, or 11/22*365=182.5% APY Look We’re really, really excited to start all of our non-correlated strats in production, and get this thing rollin’. We care about regular people. As crypto enthusiasts, we believe that our efforts should benefit everyone. Bank the unbanked. Empower every (wo)man. Our retail offering is smarter, faster, and has higher yields (potentially) than the markets. So Sign up here: , before we’re forced to make the barrier to entry more than $49.99/mo lol. Seriously, after we hit 100 paying subscribers the price increases to some magical and as-yet undetermined new pricepoint. https://tradersalmanac.ai Get in while this is hot, folks! I’ve been trading Genome 9. You can check n compare the results of the different genomes with the performance charts option, note that ‘live’ data only exists from Aug 2020 onwards. Note Final Thot Have some juicey pre-alpha sh#t to look forward to: ( : Trader Almanac) Disclaimer The author works at

We Built A Trader's Almanac And The Results Are Promising

Dear reader, please note that this article was written anonymously, as I am a person deep inside the Enterprise Linux ecosystem. I know "anonymous" is a big word, and if anyone wants to identify the author, they can. I'm against changes to RHEL code redistribution, and I believe that Red Hat is as much a "freeloader" on open source as any other company is on the RHEL codebase. However, I would like to share reasons why I will never install Rocky Linux on my servers. ever In this article, I would like to share some of the stories, misdeeds, and bad practices that explain why so many people do not like Rocky Linux. I also want to show that things are a bit more complicated than most Linux users think. Story 0: The original founder of CentOS The central figure in the case against Rocky Linux is Gregory Kurtzer. He is, for many people, the hero of the RHEL rebuild world. Many believe he is the father of CentOS, and Rocky is/will remain his beloved and, more importantly, free child. The term "The original founder of CentOS" comes from Kurtzer himself and has been spread like wildfire by PR companies (more on illegal, in most countries, and shady PR practices later). The only problem with this statement is that, in the opinion of many, including myself, it is not true. My doubts about Rocky Linux came exactly from this point, as one of my much older colleagues said that this was "not entirely true" (his exact expression was a “little” stronger). I would like to present some basic but important facts: Rebuilds started on the RHEL rebuilds mailing list. The name CentOS was announced by Rocky McGaugh. The Kurtzer was not interested in building a Red Hat Enterprise Linux (then Red Hat Linux) clone. The idea of creating a true distribution from RHEL was not his and had been discussed much earlier. Well, you can read a bit more on HN. And it's written by quite a famous person in the Linux world :) So why does Gregory Kurtzer claim to be the "original founder of CentOS?" Mainly because he started the Chaos Foundation, which took over the efforts to rebuild under a common name. [1] https://www.mail-archive.com/redhat-devel-list@redhat.com/msg07038.html [2] https://web.archive.org/web/20040630213827/http://www.caosity.org/pipermail/caos/2003-December/001205.html [3] - Gregory Kurtzer was not interested in building a RHEL clone https://web.archive.org/web/20040824032738/http://www.caosity.org/pipermail/caos/2003-July/000701.html [4] - Idea of creating Distribution on it's own https://www.mail-archive.com/rhel-rebuild-l@uibk.ac.at/msg00022.html [5] https://news.ycombinator.com/item?id=33907452 Story 1: The Departure One of the main misconceptions about Gregory is that he left CentOS when, in fact, CentOS left his foundation. The people leading CentOS development didn't want to be part of Gregory's scheme. To this day, some of the "old guard" of CentOS are not "on the best of terms" with him. Fifteen years later, the CIQ CEO is much smarter - but unfortunately for the open-source community, in a very bad way. So, when articles like "What happened to CentOS will not happen to Rocky Linux” make the rounds, I think not only about bad changes to the lifecycle, but also about the fact that CentOS was able to leave the Gregory Foundation, but Rocky Linux cannot. Generally speaking, the person in question himself has a few versions of it; my favorite was presented by himself in the Changelog podcast: I was associated with it until Red Hat sued me. And then he said: It wasn’t a lawsuit, it was a threaten of a lawsuit, which was enough in my book to do it. [1] https://lists.centos.org/pipermail/centos-devel/2005-March/077502.html [2] https://www.reddit.com/r/CentOS/comments/s77p49/comment/ht9v86o/ [3] https://changelog.com/podcast/427#transcript-87 Story 2: Foundation You may know that Rocky Linux is part of RESF—Rocky Enterprise Software Foundation. But if you are familiar with "foundations," especially US-based "foundations,” you know that many of them are broken by design. The Rocky Linux Foundation loosely promised to be a non-profit. But it isn't. It's for-profit and it has a single owner (Gregory Kurtzer). But there is more to the smoke and mirrors surrounding RESF. As you may know, they have governance and bylaws. So look at them and count how many people in that governance are not employed by or connected to the CIQ. By the way, the foundation broke its own statutes by not having a diverse governance :). I'm not going to read the bylaws again to see if they still do that, but if you find it, feel free to comment. Also, remember to read older bylaws and older about pages since it’s changed. The whole story is strong in media and PR. Take, for example, the ITWorld Canada article from 2022 In literally the same paragraph, you have the following sentences: The key for an open source initiative to grow and flourish,
Kurtzer said, is to is to register it as a non-profit organisation,
which is what the cAos Foundation. He did the same with Rocky Linux. And then: The Rocky Enterprise Software Foundation (RESF) is a Public Benefit Corporation (PBC). Do you see the "little" problem here? I do not like to be lied to. And I do not like people being lied to, especially when it is such a primitive lie, literally in the same paragraph. [1] Look at the manipulative language used in this article https://www.zdnet.com/article/rocky-linux-foundation-launches/ [2] https://www.resf.org/about [3] https://www.reddit.com/r/linuxadmin/comments/15p1gbt/comment/jvyat0h [4] https://www.itworldcanada.com/article/what-happened-with-centos-will-not-happen-with-rocky-linux-kurtzer/501239 Story 3: Trademark ownership As I said, have you ever wondered why CentOS could leave the Greg Foundation? Well, one of the main reasons was that there was no clear ownership of trademarks/domains. Unfortunately, for the open-source community, that's not the case with RESF and Rocky Linux. As I said before, RESF has a single owner, and the Rocky Linux project does not have its trademarks. Rocky Linux, as an individual project, if it tries to leave RESF, can't use its name, logo, and other trademarks without permission from the RESF owner. So, good luck. So with CIQ/RESF milking Rocky Linux, there is no way the project can become independent. It's not a community project, it's a corporate project. From this point on, I will use arguments against CIQ/RESF/RL interchangeably. [1] https://www.zdnet.com/article/goodbye-centos-hello-rocky-linux/ [2] https://www.reddit.com/r/AlmaLinux/comments/15dr141/giving_rebuilders_a_bad_name_ciq_and_ansible/ [3] https://www.reddit.com/r/linuxadmin/comments/15p1gbt/comment/jw90zhc Story 4: Buying advertising against community-owned open-source projects These are the early days, and RL is losing to AlmaLinux. AlmaLinux is the first diversely governed foundation (and it is non-profit for real). So, what does CIQ do? They buy ads against several Linux distros, including AlmaLinux and CentOS. Is this legal? Yes, it is! Is this something that a "self-imposed non-profit" (this term is a joke) would benefit from? YES! Is this what the open-source community would do? NO! Buying ads against community-owned non-profit open-source projects while pretending to make one is against the general spirit of open source. Of course, Rocky Linux did not buy these ads; CIQ did, and they did it out of the goodness of their hearts. [1] https://twitter.com/ChrisLAS/status/1460668344156114944 [2] https://twitter.com/ChrisLAS/status/1420123460982894599 [3] https://www.reddit.com/r/linux/comments/qv6mg2/comment/hkw046b/ Story 5: PR without disclosure In many cases, the CIQ/RESF/RL use PR firms to spread the word about themselves. Sometimes, they even sponsor Linux influencers, and they tend to leave out some facts :) (like CentOS leaving the former Kurtzer Foundation or RESF being a for-profit company owned by one person). Anyway, some PR tends not to mention the obvious conflict of interest and that the article is sponsored. And since it's very difficult, if not impossible, to verify the source of the PR, it's very hard to say whether the article is sponsored or not if it's not labeled. In my country and many EU countries, it's legal. Even in the US, it's not a legal problem; it shows poor ethics and morals of the: Writer PR company Publisher The company that sponsored it As I said, it's extremely difficult to catch someone red-handed. However, in the case of RL and CIQ, it has become quite well-known in the Linux community. [1] https://twitter.com/GordonMessmer/status/1675997483573612546 Story 6: Spreading FUD One of the biggest damages done to CentOS Stream has been the FUD spread by CIQ and others. The main point is that CentOS Stream is unstable and will never be production-ready. As someone who regularly compares packages and distributions, I can say this: CentOS Stream is stable and, in many ways, even better than RHEL, and that means it is even better than clones. The number of engineers working on CentOS Stream is greater than that of any other RHEL clone. The amount of testing done on CentOS Stream is orders of magnitude greater than any other RHEL clone. The CentOS Stream gives users real power to fix bugs and influence the future of the distribution. There has also been a lot of FUD spread about AlmaLinux. That AlmaLinux has taken "shortcuts,” especially when it comes to the subscription manager. If you're familiar with Subscription Manager, you know that it's designed to connect to Red Hat infrastructure, and Enterprise Linux clones don't install it by default. So, not including it in AlmaLinux is not a bad shortcut but a good decision. Later, it was added because it might also work with Foreman/Katello/Candlepin. The whole "AlmaLinux takes shortcuts" era was FUD in its purest form. Unfortunately, I can't find the source of this ATM, but I've seen it, and I'm sure one of the readers will be able to add it in the comments section. Other popular FUD spread about AlmaLinux, although I did not find CIQ employees saying it publicly: AlmaLinux uses CloudLinux infrastructure (they used it during the bootstrap phase, and it was very well-known) AlmaLinux is controlled by Russians (this one goes strong after Putler attacks Ukraine). CloudLinux controls AlmaLinux (not that CloudLinux CEO literally stepped down from the foundation; also, AlmaLinux has a much healthier board than RESF) Story 7: Being fu****g hypocrites So, you remember all that Red Hat drama about paywalled GPL sources? When Red Hat a "cancer" on open source? And users were "freeloaders"? One of the people who was very vocal about this was Gregory Kurtzer :). No matter what all the shouting was about: "Rocky going strong." "Protect the community." "Protect open source." Or nice PR from RESF: “I believe that open source should always be freely available and completely stable.
It should never be hidden behind a paywall, nor should it be controlled by a single company,”
states Gregory Kurtzer, founder of the Rocky Linux project and chair of the board of the
Rocky Enterprise Software Foundation, What's worse, they are doing the same or even more restrictive things than Red Hat. And other big words that are not worth mentioning because when it comes to real action, they are not there. Now, CIQ is giving back to the community by putting a paywall around the sources of CIQ Rocky Linux 8.8: Restrictions. The license granted in this Section 3 is conditioned upon
Customer’s and its Authorized Users’ compliance with this Agreement. Customer shall
not and shall ensure its Authorized Users do not: (i) permit any third party to use or
access the Software (except for the Authorized Users as permitted herein); (ii) install the
Software on more than the number of Licensed Hosts permitted under the applicable
Order; (iii) share access to the Software (including log in information or notifications)
with anyone who is not intended to be an Authorized User; (iv) provide, license,
sublicense, sell, resell, rent, lease, share, lend, or otherwise transfer or make available
the Software to any third parties, except as expressly permitted by Ctrl IQ in writing; (v)
except with respect to any access to Software that is licensed under an open source
license, modify, copy or create derivative works based on any content accessed through
the Software; (vi) except with respect to any Software that is licensed under an open
source license, disassemble, reverse engineer, decompile or otherwise seek access to
the source code of the Software; (vii) access the Software in order to build a competitive
product or services; (viii) remove, delete, alter, or obscure any copyright, trademark,
patent, or other notice of intellectual property or documentation, including any copy
thereof; (ix) transmit unlawful, infringing or harmful data or code to or from; or (x)
otherwise use the Software except as expressly permitted hereunder There is more. They made rebuilds of other RH products Red Hat Ansible Tower (or whatever they call it, ATM). They made it closed source. Then, after the community started noticing that it should be open source, after two weeks they decided to release code. So that's it when it comes to open-source heroes and giving back to the community. [1] https://www.reddit.com/r/AlmaLinux/comments/1aurwrr/comment/kri9xpc/ [2] https://www.reddit.com/r/AlmaLinux/comments/15dr141/comment/ju3t9mv/ Story 8: Borrowed content - erratas So the CIQ/RESF/RL use Red Hat content, that's obvious. However, you need to remember that components have different licenses. So, if you are using the source code, the most important and, in many cases, only license is the one that is in the source code. If you are using Red Hat Portal or Support, the new restrictive EULA applies. If you use Red Hat errata, the errata text and content are protected. That's why some vendors have rather empty errata information, including one generated for CentOS. The most important parts of erratas are: List of packages CVEs numbers (for security erratas) The text is not that useful; you should probably read the CVE anyway, but some projects cannot help themselves and cannot be used without any consideration. Have a look at where you can read about it: https://errata.rockylinux.org/RLSA-2023:6818 Rocky Enterprise Software Foundation Satellite is a systems management tool for Linux-based systems. You can also find other examples, such as: Rocky Enterprise Software Foundation Identity Management (IdM) or Rocky Enterprise Software Foundation Entitlement Platform. Is it legal? I do not know. Ask a lawyer. Is it ethical? No. Story 9: Killing Open Source - CIQ versus Sylabs In late August 2023, news broke of a lawsuit against CIQ. Note that if I'm right, it's still ongoing. But for the moment, the court "DISMISSES all of Sylabs' claims WITH LEAVE TO AMEND." I'm not a lawyer, but I am an engineer. An open source engineer who's heard "we won't open it because it might hurt our business" or "it makes us vulnerable" time and time again. And I never liked that, but as I got older and saw people like Gregory Kurtzer, I started to understand. What Gregory did is the worst-case scenario for any company trying to build open-source projects. A company employs Kurtzer as CTO. This company makes software vital to its survival and expansion, just like any software company. Gregory was CTO when the company decided to open source its critical assets. (March 2020). Gregory leaves the company with extensive knowledge of customers, system internals, users, and contacts. As a C-level executive, he literally knows it all. Kurtzer started a new company, took part in the development team, and used it against the former company. Kurtzer profits from the old company code that was open-sourced during his time as CTO. By pulling this kind of stunt, one is killing open source—killing trust in open source companies and developers. You work with people you trust, and you never expect them to be your enemy the next day. It leaves a bad taste in your mouth that's hard to describe. Finally, I do not care about the future of Sylab, CIQ, or who is legally right. I care about the future of open source, and this kind of practice is a mortal wound to open source and free software. [1] https://www.theregister.com/2023/08/24/lawsuit_claims_ciq_was_founded/ [2] https://storage.courtlistener.com/recap/gov.uscourts.cand.408847/gov.uscourts.cand.408847.59.0.pdf [3] https://www.courtlistener.com/docket/66863695/sylabs-inc-v-rose/ Other stories There are other stories, like why EPEL stopped doing count_me analyses for some time and why nobody takes them seriously anymore. Or about some key people officially working in public institutions and de facto doing work for a for-profit foundation. But I think the most important ones are covered. Some of these stories are only known to a small circle of people who go to the conference and know each other. Personally, I have left out some of them because it would literally say who I am or where I work. Summary When Red Hat "bought" the CentOS project, there were many red flags. We all know how it ended. Red Hat was then, and for many still is, the champion of open source. RESF/CIQ/RL was never there and never will be with its current smelly track record. And the sheer volume of red flags regarding them is by far more than it ever was with Red Hat. If you read this and install Rocky Linux, you are not only a fool but a dangerous fool. You are the fool who likes to be lied to and is incapable of understanding the bigger picture. I also omitted the technical part of the CIQ/RESF/RL. Perhaps I will return to this to this topic. In the next article, I will cover the joke called OpenELA.

The Case Against Rocky Linux

রকি লিনাক্সের বিরুদ্ধে মামলা

Der Fall gegen Rocky Linux

El caso contra Rocky Linux

Le cas contre Rocky Linux

रॉकी लिनक्स के खिलाफ मामला

Rocky Linux に対する反論

Rocky Linux에 대한 사례

O caso contra Rocky Linux

Дело против Rocky Linux

Rocky Linux'a Karşı Dava

Vụ kiện chống lại Rocky Linux

针对 Rocky Linux 的案例

221 Stories To Learn About User Experience

113 Stories To Learn About Ui Design

Investigating Internet Freedom & Digital Democracy with Nicole Scott and Simon Morgan

নিকোল স্কট এবং সাইমন মরগনের সাথে ইন্টারনেট ফ্রিডম এবং ডিজিটাল ডেমোক্রেসি

Internetfreiheit und digitale Demokratie mit Nicole Scott und Simon Morgon

Libertad en Internet y democracia digital con Nicole Scott y Simon Morgon

Liberté sur Internet et démocratie numérique avec Nicole Scott et Simon Morgon

निकोल स्कॉट और साइमन मॉर्गन के साथ इंटरनेट स्वतंत्रता और डिजिटल लोकतंत्र

ニコール・スコットとサイモン・モーゴンによるインターネットの自由とデジタル民主主義

Nicole Scott과 Simon Morgon이 함께하는 인터넷 자유와 디지털 민주주의

Liberdade na Internet e democracia digital com Nicole Scott e Simon Morgon

Свобода Интернета и цифровая демократия с Николь Скотт и Саймоном Моргоном

Nicole Scott ve Simon Morgon ile İnternet Özgürlüğü ve Dijital Demokrasi

Tự do Internet & Dân chủ Kỹ thuật số với Nicole Scott và Simon Morgon

妮可·斯科特和西蒙·摩根的互联网自由与数字民主

ALMA

helloalma.com

-- employees

Since n.d.

COMPANY RANKING

ALMA

EVERGREEN INDEX #1271

Representing this company? Click here to claim and customize this page!

Alma WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

ALMA

helloalma.com

-- employees

Since n.d.

COMPANY RANKING

ALMA

EVERGREEN INDEX #1271

RELATED COMPANIESRANK

STORIES ABOUT ALMA

Representing this company? Click here to claim and customize this page!

Alma WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!