

Anyone else notice that a large flat rate box has the same limit and the post only counts a small flat rate box?
Anyone else notice that a large flat rate box has the same limit and the post only counts a small flat rate box?
Building electronics can be a long process. The FW16 itself experienced many months of delays before it was finally released to preorder. Also, the 13" board that runs the same generation as the FW16 came out before the FW16.
As a FW16 owner, I’d love some news myself, but they did just add two whole new SKUs which is going to take up some component of R&D time. They may be working at a tick/tock cadence for updating small devices then coming back to the large device.
Typically the same level of permissions needed to load drivers - which if they’re attacking the system using custom out of date drivers is relevant.
Having users and services at least privileges is one step of attack surface area reduction, but the “better” solution is to make sure that revocation check is enabled and that the compromised cert is revoked by its issuer. Or if it’s an old, unused root, you can ban that root at the machine level.
I suspect you may have meant to respond to the speed comment rather than root?
“The only difference between science and [messing] around is writing stuff down”
From memory I can only answer one of those: The way I understand it (and I could be wrong), your programs theoretically should only need modifications if they have a concurrency related bug. The global interlock is designed to take a sledgehammer at “fixing” a concurrency data race. If you have a bug that the GIL fixed, you’ll need to solve that data race using a different control structure once free threading is enabled.
I know it’s kind of a vague answer, but every program that supports true concurrency will do it slightly differently. Your average script with just a few libraries may not benefit, unless a library itself uses threads. Some libraries that use native compiled components may already be able to utilize the full power of you computer even on standard Python builds because threads spawned directly in the native code are less beholden to the GIL (depending on how often they’d need to communicate with native python code)
TIL that exists, I thought you were talking about an actual flippy disk (lower case) until I got here.
The could be using .js and .py files directly as config files and letting the language interpreter so the heavy lifting. Just like ye olde config.php.
And yes this absolutely will allow code injection by a config admin.
Found the FF14 fan lol
The release names are hilarious
Does that still happen if you use the merge unrelated histories option? (Been a minute since I last had to use that option in git)
fail2ban isn’t a WAF?
Out of curiosity why would you call Ceph a fake HCI? As far as I’ve seen, it behaves akin to any of the other HCI systems I’ve used.
Not all of them. Ceph on Proxmox and (iirc) VMware vSAN run bare metal. That statement was a call-out post for Nutanix, which runs their storage inside a VM cluster. Both of these have been doing so for years.
Reddit is large enough that this would usually have ended up on one of the anime subs or technology joke subs rather than the general comics community.
Remember us… Remember that we once lived
Kupo? [Woop woop woooop]
Depending on the corruption/compression, or some combination thereof, yes. Usually it’s supposed to correct that issue with a key frame every few seconds, but if the source data were corrupted (or poorly generated/enhanced) it could happen.
Based on your other picture’s aspect ratio, it looks like you zoom enhanced a highly compressed frame. Image enhancement doesn’t work like it does in the movies.
The Netgear M4300 I got works like that, it’s a feature not a bug. There’s no link lights on the bottom, so the top row does the ports in alternate left/right patterns matching the label on the case right above the light.
Edit: a word
I work in IT. If someone came to ask me if they could install this on their system I’d tell them no, based only on this trailer. You’ve got to give us more info.
I’m all for open source and open systems that can be built up as needed, but people like me would need information to make decisions. Unlike your typical corporate executive or manager, technical people aren’t as easily conned by hype videos. I’ve seen more information published from a game company that’s trying to hide spoilers. The only technical information I could spot was that neofetch like screen, so I know you’ve got something Unix-like.
Also, if you’re going to be coy and post publicly but then send people on a treasure hunt, pick a less generic name or else you’re going to get lost on page 3 of Google. You list “Open Systems OS 1.0” on one slide, and that search for me returns OSF/1 (1990s), OpenKylin (a Chinese Linux), and classic Mac OS as the top results.
I get that software development takes time, and good software development takes even longer, but if you don’t have the info it’s too young in the development cycle for a hype video. It also tells me that if you’re using semantic versioning you’re using it wrong, because v1.0 of semver implies to be your first stable API, which you either have and are hiding or don’t have so you shouldn’t be at 1.0.
Even just one sentence “I am building a Unix-like operating system using a [custom|Linux|BSD] kernel which is designed to [fly model airplanes]” would be better than a void. That kind of sentence will get the right people interested in you project and asking the right questions. For example, if you’re about model airplanes or server hosting, I might be interested. But if you’re building an OS around someone who wants to use their computer like a VN, that’s not my cup of tea personally. You haven’t dis-proven the latter yet, though I assume it’s an unlikely occurrence.
I have 4 characters (past and present) that all occupy the same “party role” for this reason. They each have their own back stories sure, but their decision-making process is essentially the same because it’s how I would solve that given problem. The same set of equations, just with different source data.
I hadn’t thought about over-exaggeeating a trait before to differentiate them, I may have to use that trick going forward.