Also if you tap on the ‘kebab’ menu and press View Source, you can copy the message.

I swear Lemmy comments for YouTube had a feature that let you open it for any page, but it seems the GitHub and Firefox page been deleted.

Edit: Looks like I’ve still got a fork: https://github.com/Steve-Tech/Reddit-Comments-for-YouTube (it says Reddit, but works for Lemmy too)

To their partners*. Which I believe are companies that help out with support or something.

The HTTPS certs are designed to prevent MITMing, but if it’s still a worry or the domain is blocked by DNS, you can manually find the IP and add it to your hosts file instead.

For ergonomics, the plugin should be able to spot cuts in the video so you can easily select the correct frames.

This shouldn’t even be too hard, I doubt YouTube is completely rerendering every video with ads, they’d just insert the ad in before an I frame in the video. So each ad will start with an I frame, and the video will resume on an I frame, meaning just let the user select all the I frames, no fancy cut detection algorithm is needed.

I have no idea how to do this from JS though.

Also I mean video I frames, not HTML iframes.

AFAIK fast startup only affects shutdown, clicking restart will always do a full reboot. Shift clicking shutdown will do a full shutdown like you said, but shift clicking restart will start recovery mode.

Not sure if it affects that, but you can disable Alcohol ads on the Google Ad center.

ADCs, DACs, IO extenders

These should all work without kernel drivers. For example, here’s a user space python library for ADS1*15 ADCs, or Nuvoton MS51 IO Expanders. Unless you need very specific timing or require the kernel to know about it, you shouldn’t need a kernel driver.

Idk, with I2C if it’s not something that needs a kernel level driver, there usually isn’t a problem with interacting with it from user space, for example basically all RAM RGB controllers are I2C and OpenRGB has no problem with them. I’m pretty sure I’ve only ever used an I2C device tree overlay for an RTC.

Also I2C/SMBus is present everywhere on x86, like some graphics cards expose it through their HDMI ports, even some server motherboards have a header for it; but for GPIO I’m unaware of any motherboards that expose it, so good luck researching the chipset and tracing out the pins.

Google does too, although I only know of it being used for domains.google, which got killed.

They were expecting it to not be Android, but something more custom. Like I feel even just bare bones Linux would’ve been more acceptable.

Ampere CPUs use normal DIMMs, and don’t have integrated storage, like any other CPU. So you can have the best of both worlds (although idk about power conservation, they are efficient though).

I might be completely wrong, but I’ve heard that a key is only a few hundred dollars, and once you’ve got it you can sign whatever you want. I think ReactOS also used to offer free driver signing for open source projects.

So I guess if ReactOS can afford one, so can most anti-cheat companies.

ZLUDA originally only supported on Intel since it was designed by an Intel employee, but AMD hired him to make it work for AMD instead. So in a way Intel is somewhat important here.

Some discord servers can require a verified phone number, not any I know of, but it can be enabled.

Yeah, sorry I wrote the comment before I watched the video.

I’ve looked into getting one for my AMD laptop but I haven’t actually got one yet. Some models are locked, some are not, here’s my research:

• The common BE200.NGWG is a CNVi module and everything except the radio itself was moved into Intel’s CPUs, for cost savings.
• The BE200.NGWG.NV is a normal NIC and should support AMD.
• The BE200.NGWG.NVX - same as above but with an X?
• Anything starting with BE202 sucks, avoid it.

I definitely agree with automatically configured stuff, but I enjoy setting link-local static IP address with IPv6, like my home server is fe80::bad:c0de or 192.168.0.2, and my NAS is fe80::coo1:da1a or 192.168.0.3. I’ve definitely mistyped the IPv4 a few times (see your 169 typo), but the IPv6 always delivers hackerman vibes.

I have also set <prefix>::bad:c0de and have my IPv6 prefix on a keybind, but I understand that’s a bit of a stretch.

Yep that was exactly the issue I faced before giving up with NVMe.

I haven’t completed read through the tutorial, but UEFITool does exist for Linux. (I had unsuccessfully added NVMe support to an old motherboard previously)