Sorry, I thought you were enumerating gerivances against Microsoft and not better alternatives. Pluton has been controversial because it's been marketed as a "security" solution when in reality is's just doing DRM. Originally greated for the Xbox, it's kind of the antithesis of Valve's Proton.
I don't know of one that covers everything. Treasury's War is a sort of auto-biographical insider oriented history written from the perspective of someone in the Treasury Department, using the system to chase "terrorists" (often just random Muslim NGOs or orgs with zero evidence of terrorist involvement). Other books cover parts of the system incidentally, like the Banker's Plumbers Handbook (warning: self published, roughly edited).
A lot of what I learned about it, I learned by reading random documents published by governments designed for people working in regulated industries. Or by talking to people who worked in banks or regulators themselves. AML doesn't just cover banks but also in some countries casinos, car dealerships, lawyers, auction houses... it's like trying to push down on mercury so the scope of the rules constantly expands.
That's some amazing work in the quantum feild. I'd like to highlight this poignant quote towards the end of the article:
Knowing that you don’t even need to consider that a solution won’t exist can be very helpful. Often the hard part is just knowing to work on a problem at all!
Like GridLion, there are a handful of macOS space organizers that attempt to confine specific apps to specific spaces.
What would be most helpful for my workflow is something slightly different. I need to be able to launch specific browser profiles/windows in these workspaces. One space with all of the tabs for project X, another space with all of the tabs for project Y, and then another with all of the tabs for project Z. These might be in different browser profiles.
I don't see how I can achieve this under the common per-app paradigm of macOS space organizers unless macOS has some notion of Windows/Linux style shortcuts whereby command line arguments can specify the exact things that need to be in the browser window.
Under the bill, companies selling digital games released or resold after January 1, 2027, must provide at least 60 days' notice before terminating service. Furthermore, they must ensure that purchasers can continue to access the game—such as by providing an alternative version or a patch—and must offer refunds if doing so is not possible.
I'm excited about what this could mean for Bethesda games like ESO and Fallout. These franchises have historically been single player. The single-player focus is directly connected to the rich modding communities behind these games.
When online-only ESO and Fallout 76 were released, many longtime players were frustrated at the total lack of control they've enjoyed with prior titles. On top of this, the games are practically impossible to complete when attempting to play them like a single-player game. It makes these games far less immersive compared to their older single-player counterparts.
Looking forward to the far away day when these alternate/patched versions allow Elder Scrolls / Fallout fans the opportunity to fix mistakes made by Bethesda/Zenimax.
Ambitious idea. I have trouble understanding how the author wants space-tree to avoid persistance while simultaneously solving "a weeks-long investigation into a sub-system might want a whole subtree." Are they banking on never rebooting?
I defer persistence to other packages like the built in bookmarking system in Emacs or activities.el. Basically, the only concern I want in the workspace manager is within-session workspace creation and navigation.
For those super complex workspaces, I'll persist and restore them with a separate package, although I usually never do this. I usually don't do this for an entire subtree though.
I imagine this will be the number 1 feature request, so I may add in cross-session persistence. I have to wait and see how many people request it!
Have there been any improvements to the Syncthing conflict situation over the past several years?
Syncthing conflics were such a pain point for me that I abandoned it 5 years ago in favor of application-specific synchronization protocols. Joplin for notes, Ente for photos, and Bitwarden for passwords.
Most conflicts I encountered seemed like they should have easily been handled with something designed to merge text files. Syncthing isn't designed for that.
Commonalities between Syncthing and application-specific solutions:
- Sync
- E2EE
Pros of application-specific sync:
- Works more reliably with the application data.
- Many solutions come with a web interface that makes them usable from platforms where software cannot be installed.
- Not having to clean dozens of sync conflics piling up over time.
Cons of application-speciifc sync:
- Syncable data is limited to application-specific stuff.
- Applications are bloated compared to simple filesystem sync.
- Supply chain risk goes from well-tested solutions like KeepassXC/Syncthing to things built with ‘No Way To Prevent This,’ Says Only Package Manager Where This Regularly Happens[0][1]. Exacerbated by limited ability to control software versions of distributed services, apps, browser extentions, etc.
IMO, this is last Con is significant. I'd like to return to Syncthing, but only if the conflict resolution has improved.
reply