Tbh this is a programming community. While yes, a quick summary would not have gone amiss, I don’t fault OP for not including it. RFCs are often pretty dry but this one is reasonably straightforward as a subset of JSON to reduce some ambiguity.
Ok. Can you back that up with a source?
Fast pace tiktok style videos aren’t really great to analyze on a phone, and your clip doesn’t seem to contain any outbound links.
Orange braincell hard at work
Yup. My background is computer science transitioned to IT Infra.
My sister sent me a screenshot of a Spotify one-liner error, white text on black background, captioned “they wrote a lazy error”. I immediately recognized that the actual problem was the load balancer in the front end trying and failing to connect to the backend/middleware in the first error, then in the second it recognized a failed health check and reporting that no back ends were available. Root cause is probably networking issue or actual server crash.
I also have a bonus that in high school I had watched a ton of videos on VFX/SFX and knew a rough way around After Effects and compositing (before I jumped into CS I had considered this as a career path), so now when I watch TV and movies I can also see some of the “layers” they use to compile the on screen effect.
Who am I to judge if the card has sufficient performance, security, cost, and physical form factor for my needs.
That makes sense
I was thinking it was referring to something like a SAS or BIOS firmware update. Which would be impressive if that also ran BSD
Why would that be illegal? Shouldn’t there be some way to plug an older flash drive or console cable into a laptop that doesn’t have a type A port? (Ahem, Mac)
A to B made more sense in a world where devices cannot serve as both roles via negotiation. My android phone when I got it utilized a data transfer method of plugging my iPhone charge port into my Android charge port, then the Android initiated the connection as a host device.
The true crime is not that the cable is bidirectional, the true crime is that there is little to no proper distinction and error checking between USB, Thunderbolt, and DisplayPort modes and are simply carried on the same connector. I have no issues with the port supporting tunneled connections - that is in fact how docking stations work - just the minimal labeling we get in modern devices.
I’d be fine with a type-A to type-A cable if both devices had a reasonable chance at operating as both the initiator and target - but that type of behavior starts with USB-OTG and continues in type-C.
I’d put the deflate algorithm over the LZMA algorithm just because deflate is used by both windows (zip) and Unix (gzip). Windows I don’t think has added LZMA/xz support until recently if at all.
Gotcha. Yeah low level Unix has some weird stuff going on sometimes.
Oh thank goodness, that was one of my main complaints with the system. Did they ever get around to requiring sudo like Macports (and any other reasonable system level packages manager on BSD/Linux)?
After Crowdstrike are we sure it’s not all blue screens in the windows column?
If it’s anything like when I used a Mac regularly 7y ago, Homebrew doesn’t install to /bin, it installs to /usr/local/bin, which only works for scripts that use env in their shell “marker” (if you don’t call it directly with the shell). You’re just putting a higher bash in the path, not truly updating the one that comes with the system.
Oh for sure
I saw a meme somewhere along the line that Excel is the third best tool for every job.
Okay that’s fair. Their pricing is awful in general, and that’s especially egregious for something that used to be free
There’s probably specific ticket queues and wiki/doc spaces for each support team.
Problem with an app? Send it to the internal dev/support team. Then if needed it gets routed.
How was Parsec before the acquisition?
I only really have experience after, and it’s the only Unity product I’ve actually found that I like. My only major complaint is that it’s not compatible with the base configuration of Palo Alto, but that’s really more of a Palo Alto problem than a Parsec problem.
Which is exactly where Sun Unix keyboards place it, in a same spot