The kernel's queuing disciplines (qdisc) can do this per interface. The tc command can manage them at a low level, but it's a bit arcane, so you would probably want a higher-level tool like Wonder Shaper.
Most of us over at !baldurs_gate_3@lemmy.world seem to agree that the author is either trolling or picked the wrong dump stat for an aspiring game critic.
(Context: I haven't read the manga, and have only seen a couple of the anime episodes.)
The live action is goofy, unpolished, sometimes awkward, and in some ways looks like a low-budget college production. But it also has a kind of genuine charm that I don't see every day. Luffy in particular was very well cast, IMHO.
Originally, I believe it was. (Edit: Confirmed by RFC 742.)
FTP, on the other hand, used 7-bit ASCII mode by default; Using 8-bit mode would normally require multiple request-response round trips. (There were eventually servers that defaulted to 8-bit, but they were atypical and arrived later.)
The same “API” would be just as good over olde-schoole FTP instead of HTTPS.
I can't agree with this, because FTP uses separate connections for requests and data, making it significantly more complicated than a single-connection protocol. (Note especially that the conventional default is for the remote host to initiate the second channel, so the requestor must also listen for and accept incoming connections!) If you want to stay old-school, the Finger protocol would be a better example of the point you're trying to make.
Practically speaking, though, HTTPS was an excellent choice here. It provides an appropriate level of data authenticity without needlessly complicating things, and easy-to-use implementations are ubiquitous.
Licensed for use until your individual revenue from C++Builder applications or company revenue reaches $5,000 US or your development team expands to more than 5 developers
Is it just me or is it really fuckin’ easy to not connect your TV to the internet?
I prefer not to reward corporations by buying equipment with built-in spyware.
(Also, "easy to not connect" depends on whether the TV nags you, or disables features, or uses any open wi-fi it finds, or includes a cellular or mesh modem.)
I'm assuming you've already verified that other bluetooth devices work as expected.
A different distro (e.g. Debian Stable) might help narrow down the problem, as their kernels tend to be built with different options and their packages sometimes have different default configurations. Be sure to look for helpful messages in dmesg and syslog/journalctl.
After that, the next thing I would try is a USB bluetooth dongle. Some bluetooth modules don't work well with Sony's controllers, and it's possible that the one on your motherboard is among them.
Hopefully we’ll stabilize around browsers and open standards.
I would love this, but I think it will require major privacy reform. The push toward apps comes overwhelmingly from a single source: surveillance capitalism.
Looks like Hans implemented a workaround in vkd3d-proton 2.10, using the open-source AMD vulkan driver on linux (RADV).
Device generated commands for compute
With NV_device_generated_commands_compute we can efficiently implement Starfield's use of ExecuteIndirect which hammers multi-dispatch COMPUTE + root parameter changes.
Previously, we would rely on a very slow workaround.
NOTE: This feature is currently only enabled on RADV due to driver issues.
I don't imagine it will take long for this to make its way into a Proton experimental release. Folks with AMD graphics who are comfortable with linux might want to give it a try.
The kernel's queuing disciplines (qdisc) can do this per interface. The
tccommand can manage them at a low level, but it's a bit arcane, so you would probably want a higher-level tool like Wonder Shaper.