This falls in the category of “looks shitty, but could be pretty good”.
I once had a variation of this with devilled eggs with minced chicken cooked in a broth mixed in. It was fantastic, so meat in devilled eggs could probably work?
This falls in the category of “looks shitty, but could be pretty good”.
I once had a variation of this with devilled eggs with minced chicken cooked in a broth mixed in. It was fantastic, so meat in devilled eggs could probably work?
I mean, for 10 bucks anything is a decent deal. Those specs are pretty decent for a simple home server. I’m not familiar with HP thin clients, but I assume you can install a Disdro of your choice on it? My big reason to avoid HP is their crap software and warranties, both of which are moot here.
I would say relatively light software like tailscale, pihole and such would be fine. Docker containers might be pushing it, but that depends largely on what containers you want to run, same goes for nginx; by itself the requirements are fairly low, it depends on what you want to run on it.
Jellyfin might be a stretch, and as you alluded to, real-time transcoding is probably out. It strongly depends on the decoding capabilities of that chip and wether it does hardware decoding or if it all happens in software. The latter might be too much for it. If it can handle it though, it might be interesting as a media player hooked up to a TV, rather than acting as a transcoding or DLNA-esque server.
Oh absolutely. The reason isn’t financial, the reason is cruelty. It always is with this shit.
The original Test Drive Unlimited was great, but it rightfully bombed in reviews due to some really bad technical issues. Some of the car characteristics were really bad and off the mark, and the game suffered from an engine issue that was a problem other racing games had solved long ago;
On long slopes, the geometry of the road didn’t curve properly; the angle would have a polygonal jagging issue. This was most likely to shave off performance cost on the 360. Other games had already solved this issue by effectively smoothing angle changes, but TDU did not do anything of the sort. The result was that on hilly terrain cars would constantly bump around and lose traction due to weird unexpected air-time. Some cars were affected far worse than others, particularly super cars had a bad time.
I loved TDU, I loved cruising around in my Shelby Cobra and doing the one-hour tour around the island for decent money.
But the list of flaws is pretty long, and the technical issues made it a nonstarter for anything competitive.
The effect you are describing is “viral load”; the degree to which a virus is present in the body. This is an indicator of how infectious you are. It is especially important for people with HIV to see if they are “safe” or need their medication adjusted.
However, an at-home test will not be a good indicator of this. These have too many variables such as the site that was swabbed, time delays from the various biological functions, how well you used the kit and even variability in the kit itself.
To properly test for viral load, a blood test should be used. I worked with a company that tested for viral load via expelled breath, and while this was a good indicator of infectiousness y/n, and was faster than a PCR, it was not more accurate.
I switched to using Moonlight to stream rather than Steam’s built-in RemotelyPlay months ago. It was just absolutely unusable; not a bandwidth issue, had that in spades. The problem was that it would either not connect, connect to a blank/green screen or the audio/video would randomly cut out. It would work maybe a fifth of the time, and if I had to reconnect for whatever reason, it would absolutely always fail.
Moonlight? It worked out of the gate, and has never failed despite running on some beefy encoding settings since I have very good WiFi with next to no interference from neighbors.
I desperately want Steam’s own offering to be better though. Not having to install a second tool, and to just connect from Steam directly would be a much more polished experience.
Thanks! I will pass it along and hopefully we can push for a change. I can’t guarantee that anything will happen in the short term, but at the very least we can create some bad publicity for them.
I’m mildly autistic, to the point I do have to put on a “face” and try to act “normal” in social situations. I am generally quite sociable and outgoing, so I don’t feel it’s held me back. It’s just different.
Both socially and through work I interact with a diverse range of people, and I don’t think I am any more different than a British person is from an Italian. I’ve taken the mindset that if someone has a problem with that difference, it’s merely an excuse for their bigotry that would’ve surfaced for a different reason either way.
On the flip side, it’s been incredibly helpful in my career. I have an affinity for processes and an analytical brain, as well as the ability to disconnect from any discussion emotionally. I have always felt that this stems from my autism and it’s allowed me to have business discussions about difficult topics while leaving Ego at the proverbial door.
So I would say that for me in particular, it’s been a positive. Someone having a problem with me being different is just that; their problem, not mine.
Hey Op, since you appear to be somewhere in the EU based on your mention of Euro pricing, would you be willing to name and shame the wheelchair manufacturer and/or model?
Without giving too much of my own personal information away, I might be in a position to cause a bit of ruckus for this particular company in terms of bad PR, possibly legislatively. I work for a company that profiles itself on doing this stuff “the right way” (secure practises, not screwing users this way, etc) and we are working on building a list of practises we are hoping to root out EU-Wide with some examples that are clearly exploitative.
I need nothing personally identifiable, just the brand and model, and I can pass it along to the team that can investigate further.
Tell me you’ve never used PHP without telling me you’ve never used PHP.
It’s known for giving a complete stack trace, it’s nearest neighbours and their god damn grandkids the moment it so much as coughs up a warning. For the longest time it was notorious for doing this as the default error logging level.
I’m aware it’s cool to hate on PHP, but it has plenty of things to dislike without straight-up inventing nonsense.
My tried-and-tested method has saved my (company’s clients) ass a few times.
Every Mysql/MariaDB server has at least one replication target. This replicant is not used for access by the infra, and can be paused, restarted, etc with no issue and is configured with this in mind.
We run a mysqldump on the replicant. Depending on the resiliency required, we store the dump on the replicant and/or a third location.
The tools differ, but the practice applies to pretty much every database system and the database has the benefit of not being interrupted during the backup (replication is paused during the backup, and resumed after completion). This also has the benefit of already having replication configured, and adding a secondary redundant instance you can swap out for the master (or using the backup replicant in a pinch) means disaster recovery is much faster.
Also, I dislike many things about Azure’s offerings, but their Flexible Database for MySQL does the above for you as one nicely packaged solution for a reasonable-but-not-cheap price.
I frequently amaze new colleagues when I show them that deploying an update for our backend application is a sub-second affair. Our pipeline keeps track of what git tag was deployed last, diffs between that tag and the new release, and uploads the files to each of the deployment targets. It takes longer for the pipeline agent to spin up from Cold on a Monday morning, than it does to actually deploy.
The core of the application is just php scripts, and those are either immediately up to date whenever the next call is, or swapped out the next time that component finishes a processing cycle.
Docker containers are nice, but nothing beats the cause of a stack trace being fixed, tested and deployed to the acceptance environment within minutes of it arriving.