bblb

I would say Pgpool-II is still the best we got.

This video covers pretty much all the practical stuff. I timestamped the parts in a comment.

PgPool II Performance and best practices https://www.youtube.com/watch?v=bMnVS0slgU0

> how RDP work

Uses a combination of different tech [0]. MS-RDPBCGR is at the base of it all, sort of like the main event loop [1]. MS-RDPEGDI looks into the actual drawing commands and optimizes them on the fly [2]. Then there's the MS-RDPEDC for desktop composition optimizations [3]. Also a bunch of other bits and pieces, like MS-RDPRFX which uses lossy compression optimization [4].

In RDP you don't get to play only with the bitmap or image stream data, but the actual interactions that are happening on the screen. You could say for example that the user right clicked a desktop item. Now send and render only the pop-up menu for this, and track and draw the mouse actions inside that "region" only.

[0] https://learn.microsoft.com/en-us/openspecs/windows_protocol... [1] https://learn.microsoft.com/en-us/openspecs/windows_protocol... [2] https://learn.microsoft.com/en-us/openspecs/windows_protocol... [3] https://learn.microsoft.com/en-us/openspecs/windows_protocol... [4] https://learn.microsoft.com/en-us/openspecs/windows_protocol...

IT is ~2% of the US workforce. 'Professional and business services' at 14% might be a target for work from home?

https://www.bls.gov/emp/tables/employment-by-major-industry-...

PowerShell.[0]

We have used it years on Linux in production. I would assume the MacOS version is just as first class as the Linux version. We are not using to replace Bash as a login shell, not just yet, but a simple pwsh-command and boom, welcome to the future where you're not tied to the 50 year old antiquated idea of 'everything is a file' and it's 40 year old codebase. PowerShell is just a shell for dotnet, so you could say it's idea is 'everything is an object'. For example, JSON is just a datatype in PowerShell world. You don't need jq and it's horrible syntax.

Sorry if that's too confrontational, but I've been using PowerShell as my daily driver for the past 17 years, and Bash+grep+whatnot feels just as antiquated as cmd.exe.

[0] https://learn.microsoft.com/en-us/powershell/scripting/insta...

Hmm...

Isn't that kind of against the whole "FIDO" thing that I've been personally trying to deploy company wide as much as possible. That you have in your person some actual physical object, what ever it is: YubiKey, SmartCard, a laptop with a TPM chip, a phone.

And your personal private key inside that specific physical object is your "password" that only you can access by PIN or biometric identification.

If you lose access to that physical object, you lose access to the services also. That's the whole point! You can replace it, but then you go through the whole "enrollment" process again. That's another very important point also.

Sounds like a requirement from governments or LEOs. They need access to your private keys and it's much simpler if it's not bound to a physical object anymore. From now on it's just a plain text file on some server, when you backup your phone to the cloud.

450 million is a ridiculous amount of money for any software product. It breeds internal bureocracy and lost focus. They must have 100 or more C-level people by now.

But maybe I finally got it after all these years. It's not about the software or the playable game. It's about storytelling. That's what the whales are addicted to.

It's "VXJunkies", but with big bucks. I don't blame them. I also find it fascinating to watch and read about the latest technical details about some specific tech that they came up with.

S42 and PU will never happen. But what might happen is, that some of the employees take all that knowledge and skill they've been gathering all these years in CI. They will setup a new indie game studio and will release something actually viable and playable. Maybe a new "No Man's Sky" with a cool tech stack.

PowerShell is "Python interactive done right". It's too bad it has a bad rap in open source community and it might never get the traction it really deserves. Sure it has it's downsides, which tech doesn't, but PowerShell has solved so many issues and annoyances with the shells that we've been used to, that it still comes out as the winner.

I've been using it since day one from 2006, every single day. It has come a long way and the current PS7 is the best shell experience there is. Hands down no contest.

Snover's passionate early presentation about the PS pipeline is a pretty cool tech video. https://www.youtube.com/watch?v=325kY2Umgw8

SRV solves so many issues. It was codified as a standard 22 years ago. Maybe because it was invented at Microsoft, and the "year 2000 M$" was evil, the free software/open source people weren't interested in it and now it's mainly used by Microsoft products; as far as I can tell from my own experience with it.

I'm just a "user" aka sysadmin who sets up stuff, so can't really comment on the Golang. Even just the fully automated LE cert magic in Caddy is a win in average on-premises environment, where TLS certs are still a big pain and massive manual work drain. And the JSON API automation is a big plus also. At least for our use cases Caddy resolves one of the biggest issues.

Caddyserver is Apache/Nginx killer and we will talk about Caddy in a couple of years as if it's been always the default ("why did we kept fighting with apache/nginx all those years, silly us"). Seriously. It's just a completely different way to think about web servers and automation. I'm just amazed it took all these years to emerge.

I work in IT Operations of a big IT house. 100% local gov customers. We fully manage around 5000 pet servers. ~30 sysadmins and some of us do architecture designing also. There's also a separate networking team of about 10 network specialists.

Senior sysadmins are really hard to come by today, not to mention someone who wants to do architecture also.

My hunch is that the 5000 onprem pet servers are not going away any day soon, because a massive amount of it is legacy systems that take a long time to migrate to cloud, if ever. Also the work stress is just ridiculous. So much stuff to do, even with automation. Only reason I still do this is that I like the "old school" tech stack vs. cloud IaaS/PaaS alternatives.

>your storage may then be used for illegal material

Then forget about the anonymization features of Freenet, and build something that ties to your Google Auth, Facebook ID, Government ID, whatever.

And let LEA access all of the content and seize/prosecute illegal content. Really not that different than storing your content on any of the cloud storage providers. With the exception that your data would be always guaranteed to be highly available, and not on just one or two centralized cloud storages.

>But getting people to install apps today to donate their bandwidth and disk space

That's just a marketing headache. ;)

>IPFS guarantees that the owner can host their own NFT forever

I always thought IPFS just as a BitTorrent but with blockchainy tech stack.

But if it can indeed guarantee that my content would always be available, then IPFS is the answer.

>Nah, it just doesn't work.

This is why we can't have nice things. :D

We need a version of Freenet, where the network _guarantees_ that your content is always highly available. Well, at least as long as the tech/network itself is still alive.

Every user of the network has to provide some storage for the network itself. If there's not enough storage to safely store your new content on the network as highly available, the network would just say sorry, can't do right now, please wait on the line while we get new storage (users).

Sure, it would need some massive network effect to work at scale, but we have now, what, billions of devices connected to Internet? That ought to be enough.

I never really understood this current "decentralized" tech. Decentralized hashes with centralized gate keepers, and mixed with "old school SPOF tech", e.x. the VPS's that store the actual content. wat.

edit: 10GB per device/user and 1 billion devices. That's 10 exabytes. https://www.wolframalpha.com/input/?i=10GB+*+1+billion