Privacy Notes: Markdown Editor With Built-in Encrypted Vault

There is no dearth of note taking apps for Linux. There are tools like Obsidian that are local first, tools like Joplin that are both local and cloud but not encrypted. There are also collaborative tools like Etherpad that put encrypted notes on a remote server.

And then I come across a new tool this week called Privacy Notes. It mixes several things at once and tries to be the "one note app to rule them all". It is Markdown-first with WYSIWYG editor, vault for storing passwords, ssh keys etc, journal and more.

Privacy Notes

The idea of Privacy Notes is to give you an application that is primarily aimed at keeping your most important documents safe on their server by providing client side encryption.

This means that the notes and files are encrypted on your device first and then they get uploaded to Privacy Notes's servers. Privacy Notes website mentions that their servers are hosted in Switzerland.

This is zero knowledge encryption which means you have to save your key or phrase somewhere safe because if you lose that, not even Privacy Notes can give the data back as everything is encrypted.

Privacy Notes is developed by Lifetime Labs and they have the motto to provide software but NOT as a service.

In that regard, Lifetime Labs offers a lifetime price for Privacy Notes. You get 500 MB of encrypted storage for $48 (early adapter price, and it rises to $89 later). If you want more storage, extra storage is self-serve from $4.80/GB per year.

Note that server storage is a recurring cost, unlike desktop software. That's why extra storage has a recurring subscription fee.

Privacy Notes apps are open source and the source code is available on their GitHub repository. This includes the web, desktop and mobile clients and even their encryption and threat model.

More than just plain note taking

While the name suggests it is another Markdown based editor focused on privacy, it does offer a few things different than most other editors in this category. Let me share them with you.

Store your passwords and keys in vault

Privacy Notes has the option to add sensitive information in a predefined template and in its own dedicated section in the sidebar.

This is a feature password managers like Bitwarden and Proton Pass offer. Merging it in the notes is a good move, especially when the idea is to have secret, encrypted notes. Login passwords, credit card information, SSH/GPG keys are the common secrets people store.

You can also generate and save new Ed25519 SSH keys and passwords in the app. I think it can also store TOTO 2FA keys.

You can also import your passwords from your browser or other password managers:

Import passwords in Privacy Notes

📋

Privacy Notes encourages users to verify that the data is actually encrypted before it leaves your device. This puts trust in your zero-knowledge encryption claim.

Tasks

Since the idea is to provide a full-featured note apps, there are also tasks here. Now, there is no Kanban-styled task board here. Tasks are just regular notes but if you click to create a new task, it starts with a checklist. You can still add text and other markdown formatting in the tasks.

You can add checklists in regular notes as well but when you go into the Tasks view, it shows all the notes that have any kind of checklist in it.

I think the idea to give a separate view for all to-dos in one place. Which is a good thing as to-do list may get buried in the pile of notes.

More note types

There are two more note types. Bookmarks and Journals. Both are evident from their names.

Bookmarks type of notes are for saving bookmarks. It's okay to have such a feature, but to me, the place of a bookmark is in a browser or in a dedicated bookmark manager.

It would have been better to have a quick note field in the bookmarks to quickly know or search what the bookmark is about.

And there are journals. Logseq and some other personal knowledge base tools have the concept of journal entries. Which is like having a personal diary.

Each new note in the journal automatically gets the day and date as its name. You can create a new journal note the same day only when you rename the existing entry of the day.

You can also upload images, audio and any other file type via the Files option. This is good. Important documents can also be in image format. Like, I could save my passport and other official IDs in image format.

Since all the files are client side encrypted, this is better than keeping them in Google or One Drive where the images may be used to train AI (we don't know that for sure).

💡

Wiki style links are supported in Privacy Notes. This means if you move from a tool like Obsidian, your links will be preserved.

Burn after reading

Privacy Notes allows you to share links to your encrypted files. Anyone with the link can view the file but here is the twist. It can be viewed only once. The link self-destructs after is opened once.

This burn after reading reminds me of both Victorian era love letters and Ethan Hunt in Mission Impossible.

Local markdown files

Privacy Notes desktop application allows you to view and edit local markdown files. If you have personal knowledge base built on Markdown (like Obsidian) or have GitHub repo, you can use it inside Privacy Notes. It edits the files in place, keeps subfolders, and converts nothing.

Keep in mind that these files stay on your systems locally and they are not encrypted. You can choose to add them to the encrypted , though. This way, the notes will be encrypted first and then saved on to your Privacy Notes account in the cloud.

I like this idea. If you have only 50 MB of the free encrypted cloud storage or 500 MB of lifetime Pro version, you cannot dump all your notes in it. You can be selective and only upload the notes and documents that need to be in the (encrypted) cloud.

But do note that the standard features you saw above—like bookmarks, journals, vaults, etc.—are not stored locally. So you cannot create new passwords or ssh keys using the vault template and store it locally, it gets encrypted and gets stored on the server and gets counted in your storage quota.

Local markdown notes remain local. They don't get the fancy templates. But you can use the editor that works great for markdown files.

You can also mix and match. Store only the most important, sensitive data in the encrypted cloud, while regular files can be synced to a Git repo.

Also, you can export your notes any time.

📋

The free version of the app doesn't allow creating folders in the encrypted section of the app. You will see the pop up to upgrade to Pro if you click on the folder option.

Should you use Privacy Notes?

Privacy Notes is a mix of local plus (encrypted) cloud storage. Now, Linux servers are suggested to follow the classic 3-2-1 backup strategy.

We are not dealing with servers here but personally, I keep multiple backups of my data. Some are in my homelab and some stay in the cloud.

My scanned IDs, warranty papers, insurance documents, and other such important data live in the cloud. They used to be in email 15 years ago.

Privacy Notes can be part of the multiple backup strategy. Since it is especially for notes you cannot use it for dumping GBs of images but you can try using it for storing important documents, notes, passwords, SSH key, 2FA recovery codes etc. The client-side encryption adds a layer of trust.

🚧

Zero knowledge encryption is a double-edged sword. If you forget the recovery phrase, you will lose access to the docs stored in the cloud. That's why I suggest keeping more than one backups.

The free account gives you 50 MB of encrypted storage. Which should be enough for you to try it and also keep on using it if you have limited needs.

The Pro version will give you 500 MB of storage for a single payment of $48. It's a lifetime subscription, something I prefer over a recurring subscription.

The Pro version allows you to use the synced notes on multiple devices (free plan syncs only 2 devices) and keeps upto 20 revisions of a file. You do benefits for the amount you are paying.

📋

Privacy Notes allows importing from Obsidian, Standard Notes, Evernote, Apple Notes, Bitwarden and a number of other note taking apps and password managers. Mostly, you have to export the files from their respective tools and then you import them in Privacy Notes.

Getting Privacy Notes

If you want to take the feel of Privacy Notes, there is a web-based demo here. That gives you an idea of what the tool is like.

And then, when you decide to use it, you have apps available for Linux, Windows, macOS, iOS and Android.

For Linux users, Privacy Notes is available in AppImage and .deb format for for x86_64 and ARM64 platforms so even SBCs like Raspberry Pi are covered here. Every release is signed and carries a SHA-256 checksum on GitHub.

If you are using Android, you can get the app in APK format from Zapstore or Obtanium, platforms that verifies developer signature. Pure APK can be downloaded from the website, too. Google Play store integration is in works.

You can download the apps from the download section of their website:

Get Privacy Notes

Or, check out the source code from their GitHub repo.

from It's FOSS https://ift.tt/aHhmxNd
via IFTTT

FreeCORE is What Your TrueNAS CORE Box Should Have

iXsystems put TrueNAS CORE into what it called a sustaining engineering phase back in 2024. Under this, the open source NAS operating system would only receive security and stability fixes, with new features going to the Linux-based SCALE branch instead.

Even its maintenance releases got axed when iXsystems marked 13.3-U1.2 as the final release for the 13.3 series (or train as they call them).

SCALE has since been renamed TrueNAS Community Edition, and users who didn't want to move to a Linux-based OS were stuck with CORE and no actively developed FreeBSD-based path forward.

FreeCORE looks to be that path.

What is FreeCORE?

FreeCORE's web user interface.

It traces directly back through TrueNAS CORE to FreeNAS, and it's built on the same foundation CORE always used: FreeBSD and OpenZFS. The current stable release is 15.0-U1.3, and it is aimed at TrueNAS CORE holdouts.

Basically for people who rely on features like FreeBSD jails and bhyve virtual machines who have no interest in moving to TrueNAS Community Edition's Debian Linux base.

It's also worth knowing that FreeCORE is a one-person project. Their motivation for creating this was that they needed a FreeBSD way off their own TrueNAS CORE box instead of migrating to Linux.

So they built one, leaning heavily on AI coding agents for the implementation while directing and validating the work themselves.

FreeCORE's FreeBSD 15 base carries along many practical component upgrades with it too!

OpenZFS climbs from 2.1.14 to 2.4.2, Python from 3.9 to 3.11, and the web interface runs on a much newer build of Angular.

WebAuthn security keys now work as a second login factor, and one-time passwords cover console logins. Jails can share the host GPU through a new DRM driver, and rar2fs mounts RAR archives read-only.

FreeCORE also gets rid of vendor telemetry and offers a web interface that lets you manage everything from jails and virtual machines to storage, sharing, and user accounts.

Jails networking runs through VNET, NAT, or DHCP depending on what the setup needs, and an advanced jail creation form exposes every option for admins who want a greater level of control.

Get started

Most of you arriving at FreeCORE are likely running TrueNAS CORE 13.3, and moving is only a matter of taking a backup and running this script:

fetch https://freecore.org/freecore-enroll.sh && sh freecore-enroll.sh

Running it switches the system's update train and certificate away from iXsystems' servers and points it at FreeCORE's.

From there, the upgrade runs through System › Update like any other update. The configuration database migrates on first boot, though not everything makes it across. OpenVPN gets replaced by WireGuard, and enterprise-licensed features don't carry over.

Of course you could always go the fresh install route, where you write the image to removable media, verify it, and then boot from it to install it on a drive.

FreeCORE

The official documentation is a handy resource that covers a range of topics related to FreeCORE installation and usage, while the source code lives on Codeberg.

---

Suggested Read 📖: Here are your choices for an open source NAS operating system if you don't prefer FreeCORE.

from It's FOSS https://ift.tt/lmgQH5s
via IFTTT

Bottles Brings Hope for Windows-only Software on ARM Devices

It's been a while since I last wrote about Bottles. For anyone new to it, Bottles runs Windows software on Linux by hiding most of Wine's configuration work behind a straightforward interface.

Its feature list has been growing consistently too. You can pull common Windows components like .NET and Visual C++ runtimes with a single click, or juggle multiple Wine and Proton runners per bottle.

Additionally, UMU support lets you run Proton games outside Steam, and snapshots give every experiment of yours a rollback point.

With its newest offering, Bottles pushes past x86_64 hardware. Bottles 67.4 is a test release aimed at ARM64 on Linux, which is delivered through an experimental cpak package.

And know that the ARM64 rollout actually spanned two releases. 67.3 added the first ARM64 build of the cpak package, and 67.4 followed hours later with a few misc fixes and Soda 11.0-10.

Must-know bits

Placeholder images of Bottles 67.3 running on an x86_64 system.

On ARM64 systems, cpak now fetches the right build for the platform, while Soda, Bottles' Wine-based runner, carries native ARM64 and ARM64EC support. FEX also comes bundled for running x86 and x86_64 Windows software.

All of that makes Bottles genuinely useful on ARM64 Linux hardware, be it single-board computers or Arm-powered laptops.

What surprised me most was the speed at which this was delivered.

The request to add ARM64 (or AArch64) builds was opened a week ago. Within three days, there was a test candidate, the request poster (TCB13) confirmed Bottles launched on their own ARM64 hardware, and the issue was closed and marked as completed soon after.

The tagged releases followed on September 7.

If you were wondering why they chose cpak for the test run, Mirko Brombin from the Bottles team says that:

Cpak is being used for this test because it is the first packaging path where the application, Wine base and native ARM CI are available together.

The other part of the release is the inclusion of Soda 11.0-10, which comes with a range of updates. Battle.net crashing on startup is the issue that some of you will notice first. It has been fixed, and the underlying problem was XInput starting up without a Steam game ID.

For VR workloads, 64-bit Windows OpenXR apps can now connect to a host runtime such as Monado or WiVRn directly without needing to keep Steam or SteamVR running. You can go through the changelog (linked above) to learn more about this Soda release.

Installing it

Currently, the test ARM64 build ships only as a cpak, the OCI-based package format from the Containerpak project. Work is underway on getting the Flatpak release ready for this platform.

That said, you can quickly install the cpak test release on your ARM64 devices by running the following command:

cpak install github.com/bottlesdevs/bottles

If you didn't know, cpak is a packaging format that treats apps as OCI container images, each paired with a small manifest that lists its permissions and dependencies.

How cpak differs from Flatpak is that it does not lean on runtimes and portals the way Flatpak does. The cpak runtime mounts the OCI image directly, the manifest decides what the app can touch, and packages install from a Git origin instead of a central store.

from It's FOSS https://ift.tt/jmWAve9
via IFTTT

A Clanker Pitted Fedora Against Windows 11. Fedora Won, Mostly

PhoneBuff is a company that built its name by offering lab-tested, standardized reviews for smartphones run by robotic hands. Their YouTube channel showcases a range of assessments that cover speed tests, drop tests, and battery tests.

When viewers started poking them about trying Linux after a recent performance comparison they did between a Dell XPS 13 and MacBook Neo, they responded.

Taking two identical Dell XPS 13s with an Intel Core 5 320 and 8GB of RAM, one on Windows 11 and one on Fedora, the PhoneBuff crew ran the same real-world apps and workflows on each, timed by their robot mouse and keyboard (aka the clanker in question).

By the time testing concluded, Fedora won six of eleven timed tests while four tied, and Windows 11 took home a single win.

Fedora vs. Windows 11 on same hardware

Same settings too! The screens sat at 200 nits, both laptops stood an equal distance from the WiFi point, and the room stayed temperature controlled. Each test was run three to five times, with the median value noted.

Boot from a full shutdown tied at 23 seconds for Windows and 24 seconds for Fedora, too close to call. Restarting did not. Fedora came back in 27 seconds, median; Windows took 61 seconds. Windows' five runs swung 46 to 68 seconds, Fedora's 23 to 34 seconds.

The widest gap was files. Unzipping the same 6GB archive took Fedora's built-in tool 12 seconds. On Windows, using Windows Explorer, it was 57 seconds, and installing 7-Zip only got it down to 17.4 seconds.

Next comes the result that ought to sting Microsoft. Running VS Code, the robot loaded an open source whiteboard project, scanned it for errors, compiled it, and ran close to 1,900 tests. Fedora was done in 2:20.5. Windows 11 needed 3:41.99.

Source: PhoneBuff

The creative apps went the same way. DaVinci Resolve imported two clips, graded one, stabilized the other, and exported in 2:10.9 (Fedora) against 2:49.9 (Windows). A GIMP session on a 4K image, using tools like smudge, heal, and object removal, finished 53.3 seconds against 60.7 seconds.

The everyday apps were mostly a tie. Chrome on a locally hosted page with video, 3D models, maps, and chart math finished in 19.3 seconds on Fedora against 19.8 on Windows.

The same 500-page document opened in ONLYOFFICE in 8.7 seconds against 9.3, while the OCR pass also went to Fedora, 36.6 seconds against 39.8.

Even the Blender render of the same 1080p scene ended even, 44.2 seconds against 43.5.

Idle memory usage was another big gap. Left idle for a minute, Fedora used 32.9% of the 8GB while Windows sat at 85.2%. The video showed 2.27GB being used on Fedora against Windows' 6.47GB.

The lone Windows win was launching Cyberpunk 2077, 54.3 seconds against Fedora's 57.0-second launch. Though remember, that is a launch time number, not a frame rate, and PhoneBuff didn't run any gaming benchmarks.

What do the numbers mean?

Source: PhoneBuff

Do not read too much into it yet. There are no AI workloads here, and as I just said, no gaming benchmarks either.

The presenter for PhoneBuff says at the beginning of the video that Fedora is one of the many Linux distros out there and that "this won't necessarily represent every possible Linux experience."

A different distro running a different desktop environment will definitely move some of the gaps we see here.

The RAM gap comes with an asterisk too. Windows sat at 85.2% with a few Dell utilities, Defender (MsMpEng), and Edge WebView2 running by default, so Windows is not the only thing behind that 6.47GB number. Fedora simply started off with less baggage.

To summarize, the heavy tasks went to Fedora, sometimes by minutes, the everyday ones tied, and idle RAM sat at around a third on Linux against 85% on Windows.

That is all eleven tests can claim, so take them as data points, not a verdict.

from It's FOSS https://ift.tt/pCX87r0
via IFTTT

Ikey Doherty vs Omarchy: Why He’s Building Barney Instead of Another Distro

Ikey Doherty is out of retirement, and Omarchy's funding is why.

In a video posted on YouTube, the creator of Solus and AerynOS called the money behind DHH's distro absurd and promised to do it better with nothing. His answer is Barney, a Rust-based tool for building Linux distros from source.

Omarchy's Omacom Foundation has already crossed $13 million in pledges since its August launch, when eight tech executives, including Michael Dell, put in a million each.

The run has drawn its share of pushback, most recently when 1Password pledged $300,000 and its own employees objected. Ikey's video arrived a day after the foundation announced $1.95 million in AI tokens from Meta, Anthropic, OpenAI, and Fireworks.

Not a distro, but a stance

Barney is a tool meant to help you build Linux distros; the repo describes it as "yet another feckin' tool to build a Linux distro" and notes that delivering a distro is not the intended goal.

Ikey plans to show how distros get built instead of shipping what he calls a "wallpaper respin" via a series on his YouTube channel.

Everything gets built from source, and the outputs are cached against what produced them. Change a dependency, and anything built on top of it gets rebuilt. Layouts stay stateless, a concept Doherty says he helped pioneer on Intel's Clear Linux team and later pushed in Solus and AerynOS (formerly Serpent OS).

Builds run in containers, and the results are stored by content, so identical files across packages only get stored once. The plan even includes rebuilding the toolchain from scratch.

Everything is written in Rust and released under the MPL-2.0 license. The project's name itself is personal to him, as Barney is his son's name.

Work on it has started already. The first episode of the series is live, titled "Episode 0: Getting Ready." For access to the behind-the-scenes content, Ikey has set up a Ko-fi page where people can directly support him.

An Irish Traveller's reply

Don't assume that this is something Ikey has no business talking about.

Omarchy's creator, David Heinemeier Hansson, better known as DHH, had written a post comparing Denmark's wolf population with Romani people camping in Copenhagen parks.

Naturally, Ikey, being an Irish Traveller, a group that has faced discrimination for generations, was bound to react. On LinkedIn, sharing his video (the one linked at the very beginning), he called DHH's comments "horrific" and said the funding and the views together had dragged him back into the game.

His laptop buying plans have changed too. Michael Dell was among the launch backers, and Ikey has put the company on his avoid list, while also calling out Omarchy:

Gonna be honest I won’t buy another Dell laptop after Michael Dell showing support for DHH. Skipping the point of it being yet another wallpaper-respin distro.. I cannot possibly tolerate the comments made by DHH (on a number of topics)

As an Irish traveller, I strongly condemn his rhetoric surrounding nomadic people.

As a former Linux distro developer, I wouldn’t touch his shit if you paid me.

Will it do well?

Only time will tell. Right now, my read is that the question misses the point. Barney is not here to become the distro everyone installs. Success, by Doherty's own framing, is showing how a real distro gets built while the industry watches.

You already know that he has walked away from big projects before. Solus and AerynOS both carried on without him. Barney could be next, sure.

What stands out to me is the timing of it all. Another Clear Linux member, Auke Kok, is building The Ur Project from scratch, and neither of them is waiting for a foundation to get going.

The optimist inside me says that if the two of them ever collaborated, they could deliver something that shows the Linux ecosystem that pouring absurd amounts of money into a project isn't the only way to build well.

from It's FOSS https://ift.tt/ZCRq7du
via IFTTT

Elom Musk's X Tried to Kill Nitter. The Project Just Said It’s Coming Back

Nitter, the open source front-end for reading X posts without signing up for an account, is not going anywhere yet.

Weeks after X Corp's lawyers showed up demanding a permanent shutdown, the project's GitHub repository has come out of read-only mode with an updated README that says:

UPDATE: Following legal advice, the Nitter project will continue. More details will be announced soon.

Now, the repository and the homepage carry the same message, with the latter further stating that the flagship instance of Nitter and third-party-hosted ones will be back up soon.

A proper announcement is expected sometime within the next few days.

What X's letter did

On August 24, X Corp sent out cease and desist letters demanding a permanent takedown of Nitter instances and the project's repository. The deadline was 5 PM EST on August 25.

Nitter complied, and the repo was archived and marked as read-only. nitter.net's content was replaced by a short notice (which has since been updated), and a popular instance, XCancel, halted its operations.

TechCrunch, which obtained the letter, reports that X accuses Nitter of an "unlawful use and circumvention of X's Application Programming Interface (API) and associated data."

X alleges that it has evidence that Nitter scraped X data and accessed X accounts and session tokens in violation of X's rules, citing the Texas Harmful Access by Computer Act and the Lanham Act.

So far, X has not publicly commented on the shutdown or the reversal.

Not the first time

This is not the first time Nitter has been declared dead. In early 2024, X removed the guest account feature the project relied on, resulting in the project's lead, Zedeus, announcing the end.

The project found a workaround and returned sometime in 2025.

Nitter's inspiration, Invidious, a privacy-friendly YouTube front-end that has had its own run-in with big tech lawyers, faced a seven-day shutdown demand from YouTube in June 2023.

Fast forward to now. The project has kept going, and nothing came of the demand.

Makes you think such moves exist to strong-arm open source projects into submission rather than enforce rules. To these companies, any project is worth a lawsuit if there is even a shred of justification.

What remains is that Nitter says legal advice cleared it to continue, but not what that advice was or how instances will operate going forward. The announcement is where those answers come to us.

This could escalate

As far as I can see, X tried to choke such projects by closing the access they relied on back in 2024. It didn't work. Now, in 2026, they tried throwing the book by sending lawyers after them.

Seeing that X leadership has been quite disruptive, I have a feeling that they won't back down this easily, and things will escalate. When they do, I hope the open source community stands behind projects like Nitter.

from It's FOSS https://ift.tt/8rLEMG5
via IFTTT

Switzerland's Federal Government is Replacing Microsoft on 3,000 Computers

Switzerland's federal government has launched a pilot program to replace Microsoft 365 with open source alternatives across 3,000 workstations. That's about 7% of the federal workforce. The target is to complete the migration by end of 2027.

This move follows a successful proof-of-concept and a new digital sovereignty law. A separate fast-track military migration is also already underway.

The great migration goes into the pilot phase

The Federal Chancellery is investing CHF 9 million in an open-source workplace rollout for 3,000 federal employees.

On September 3, 2026, the Federal Council published results of "PoC BOSS", a feasibility proof-of-concept involving 172 federal employees who tested the openDesk suite, a German open-source collaboration platform.

During the proof-of-concept phase, core office tasks like document processing and email received positive assessments, while large-scale video conferencing still showed technical limitations.

Based on the 'success' of the PoC phase with 172 employees, the pilot is now launched for 3,000 employees.

Do note that during the pilot phase, the new system runs in parallel with Microsoft 365 rather than replacing it outright. That's okay, I think. Migration of such kind should be gradual rather than sudden.

If the pilot is successful, we might expect the migration to continue on all the 54,000 workstations owned by the federal administrations. That's my guess.

Why?

According to Matthias Stürmer, professor at the Bern University of Applied Sciences (BFH), Microsoft’s supremacy in public institutions poses three problems that are driving this migration.

First is the risk of foreign access. US cloud legislation could expose Swiss government data to foreign authorities.

Second is the risk to service continuity, as dependency on a single foreign vendor creates operational risk.

The third risk is the escalating costs as proprietary licensing fees are rising with no Swiss leverage.

Swiss Army is already moving faster

Switzerland's military cybersecurity unit, Cyber Command, is not waiting for the civilian pilot. It is already poised to replace Microsoft 365 entirely with openDesk by October 2026.

It is pretty much the same reason. Military doesn't want foreign governments accessing sensitive Swiss data.

Part of a bigger plan

Back in 2024, the EMBAG Law came into effect. It requires all Swiss federal agencies to publish government-developed software as open source by default. The law also aims to promote digital sovereignty and encourage innovation and collaboration within the public sector.

Then in December 2025, the Federal Council designated digital sovereignty as a primary focus theme. It defines digital sovereignty as "the federal government being able to fulfil its essential mission without depending on an external supplier or country."

Which is essentially moving away from big tech companies from the USA.

Neighboring France and Germany have also been trying similar moves. Let's hope that the great Swiss migration succeeds and sets an example for other countries who may speed up their own plan of moving away from Microsoft.

By the way, Microsoft has deep pockets, so they are also investing over CHF 325 million to expand AI and cloud infrastructure in Switzerland, partly to reduce the sovereignty argument.

Let's see how things move from here, but so far, it is looking positive for us open source supporters.

Source: RTS

from It's FOSS https://ift.tt/YLUtR3A
via IFTTT