Markaos

joined 1 month ago
[–] Markaos@discuss.tchncs.de 5 points 2 days ago

As far as I know, bootloader locks are done by the manufaturer not by the provider.

Verizon requires the phones they sell to NOT have the ability to unlock the bootloader. That's why there are separate factory images for Verizon Pixels.

[–] Markaos@discuss.tchncs.de 1 points 1 week ago* (last edited 1 week ago) (1 children)

The package name is visible in App info, no need to install anything - just long press the app icon, pick App info and scroll down to version

1000025523

[–] Markaos@discuss.tchncs.de 1 points 1 week ago

Google Drive app -> New (in the bottom right corner) -> Scan. It's not supposed to be a part of the camera app, that's just a useful shortcut.

[–] Markaos@discuss.tchncs.de 2 points 1 week ago

Yeah, stock Google voice recognition also works offline if you download the language model beforehand.

[–] Markaos@discuss.tchncs.de 3 points 1 week ago

Indeed, try switching your smartphone to airplane mode and see how far your voice commands get you.

Did that (or rather disabled mobile data and WiFi, because airplane mode would still keep the WiFi on), and then I dictated this sentence after the parentheses. So Google's voice input works offline just fine.

Or do they mean something like a smart assistant? In that case fair, but it's not like it will work with text input either.

It is true, however, that Google Translate doesn't do offline voice translation even if the language you're trying to translate from is downloaded for system-wide voice recognition.

[–] Markaos@discuss.tchncs.de 2 points 2 weeks ago

Don't be ridiculous - this is a lab environment, they can faithfully recreate the suffering as long as the ethics committee doesn't get notified.

[–] Markaos@discuss.tchncs.de 6 points 2 weeks ago (1 children)

That sounds like Xiaomi. The best price to performance ratio of any OEM, but at the cost of terrible software and this... experience... when you want to get rid of it.

Worth noting that not all OEMs are like this.

[–] Markaos@discuss.tchncs.de 10 points 2 weeks ago

That's a reasonable per-core size, and it doesn't make much sense to add all the cores up if your goal is to fit your data within L2 (like in the article)

[–] Markaos@discuss.tchncs.de 0 points 2 weeks ago

Please don't pretend as if OpenSource Devs don't constantly complain about pesky PRs😅

I've seen much more complaints about people constantly demanding their specific annoyances to be fixed without ever submitting a single line of code. Maintainers are pretty much universally welcoming to code contributions

I soooo hope this does something funky with someone's Lemmy client

[–] Markaos@discuss.tchncs.de 3 points 2 weeks ago

Maybe the management hasn't decided on the exact promises they're willing to make? Also there's two years left before it becomes important, while previously there was always a generation going out of support within a year.

[–] Markaos@discuss.tchncs.de 4 points 3 weeks ago

That's more of a storage thing, RAM does a lot smaller transfers - for example a DDR5 memory has two independent 32bit (4 byte) channels with a minimum of 16 transfers in a single "operation", so it does 64 bytes at once (or more). And CPUs don't waste memory bandwidth than transferring more than absolutely necessary, as memory is often the bottleneck even without writing full pages.

The page size is relevant for memory protection (where the CPU will stop the program execution and give control back to the operating system if said program tries to do something it's not allowed to do with the memory) and virtual memory (which is part of the same thing, but they are two theoretically independent concepts). The operating system needs to make a table describing what memory the program has what kind of access to, and with bigger pages the table can be much smaller (at the cost of wasting space if the program needs only a little bit of memory of a given kind).

[–] Markaos@discuss.tchncs.de 4 points 3 weeks ago (1 children)

There's no inherent guarantee that a router has a firewall configured properly, or has it enabled.

If it's not an enterprise router (where you sometimes start with a blank configuration), it most definitely does have a firewall blocking incoming traffic by default.

In the deployments you're seeing, are ISPs handing out /120 blocks to each router?

/120 is not enough for IPv6 to reasonably work. It kinda requires the smallest block to be /64, otherwise half the cool stuff about IPv6 breaks. So you should get something between /48 and /64 (the recommendation for ISPs is /56 for residential users so they can subdivide their network to 256 other networks, and /48 as default commercial allocation).

Does that require the ISP to have access to alter your home router, or do customers configure the DHCP themselves (which seems unlikely to scale)?

There is DHCPv6, but it's not really an important part of a network like DHCP for v4 networks. IIRC Android doesn't even support it. IPv6 uses Router Advertisement (RA) to tell devices what prefix they're in (and a few things that were originally DHCP options, like the preferred DNS servers), and the devices then pick their own address using the SLAAC mechanism (originally it was derived from the MAC address, but nowadays should be a random number). RA supports "multilayer" networks where each following router further subdivides the prefix it got.

If you want a static address (for example for a server), you can either configure it manually on the device (using tokenized addresses, i.e. "static local part with dynamic prefix"), or use a DHCPv6 server to assign the address (in which case the RA responses from your router need to indicate that there is a DHCPv6 server on the network).

Also, you talked about the fc00::/7 (or its locally managed half, fd00::/8) prefix as a proof that NAT is used with IPv6, but... There's absolutely nothing stopping you from having both a globally routable address and a local only address at the same time. IPv6 already requires you to have at least two addresses when you connect to any network - a link local address and whatever other address you get assigned (btw IPv4 never prevented you from doing the same thing, it just wasn't directly encouraged and wasn't widely used, and DHCP didn't support handing out multiple addresses unlike RA).

You can even get a security "improvement" over the claimed scenario with NAT with this - if you don't assign a global address to a node, then not only will it be unreachable from the internet, it will also be unable to connect to the internet itself while being reachable from your network without any issues. "Air gapping" (I know, I know... but people use this term for "no internet" now) for folks afraid of firewalls!

view more: next ›