4,235 karma · joined September 10, 2015
It uses that to install new applications and update applications installed by other app stores without the OS-level confirmation, probably can't be uninstalled on most Android OSes and perhaps some other things.
Is there any >=100W (actual, not equivalent) sunlight-like bulb available that is dimmable and programmable via ZigBee or other means?
"The condition fails for i=1 since 1 does not divide p+q unless p+q is a multiple of n, which is not generally true" (1 divides everything)
In the second it gives up:
"However, this conclusion is based on heuristic reasoning and examples"
Third attempt it makes this mistake:
"If the immediate next divisor, di+1 , is not a multiple of p (for instance, it could be q or a product involving q), then p does not divide di+1. Hence, p will not divide the sum di+1+di+2 in such a case, violating the condition." (the fact that p does not divide d_i+1 does not imply that it does not divide d_i+1, d_i+2)
Then it gives up again: "However, this conclusion is based on heuristic reasoning and examples"
Then it makes this basic logic mistake: "However, since p and q are distinct primes, p does not divide q, and it's not guaranteed that p divides q+d_i+2 , especially if d_i+2 is not a multiple of p. Therefore, for such n, the condition fails." (the fact that "it's not guaranteed" doesn't imply that it's false)
Overall it proves that prime powers have the property, conjures that non-prime-powers don't, proves that p*q doesn't have it, but completely fails at coming up with a proof strategy that proves that non-prime-powers don't have the property.
The concept of "window position on screen" makes no sense, since a compositor is allowed to display windows arbitrarily, and doesn't necessarily display them as 2D rectangles (for instance, they could be displayed in a VR environment at arbitrary 3D positions, or they could be warped arbitrarily, etc.).
Also, the window layout belongs to the user and compositor and it would be a security hole to let applications affect it.
If you want to position subwindows, you need to draw the subwindows yourself inside a main window like e.g. VSCode does with its various panes.
You need to use VM-based isolation to have good security with Linux beyond that (i.e. use Qubes or a similar alternative).
Considering that current aggressive quantization for LLM transformers uses 4 bits, does such a 0.5-bit quantization produce an effective neural network?
Does the scheme stay competitive if it is changed to use 4-bit quantization instead of 0.5-bit?
There doesn't seem to be any particularly compelling reason to use it, and note that, unless they can use libraries from an existing language, there needs to be a really MAJOR reason to use a new language to compensate the lack of libraries.
But the solution seems to be to have the desktop client request data from the phone.
In fact I'm not sure how it can possibly work otherwise (what if someone just uses their phone for years and then opens the desktop client for the first time ever? does that not show any old messages? seems a terrible design).
Photos are generally <1MB in size and I think have a single photo sent but not received on average per user seems reasonable (most users probably almost never use Signal, and of those that do probably most only use text, and those that use photos probably most don't send more than one or a few per day).
Videos are probably relatively rare and if not maybe they should do something about them, like not storing overly large ones them on servers and requiring both phones to be online to transfer.
There's a 500x margin between the estimate and their costs anyway.
Maybe the problem is that the Signal app doesn't eagerly download messages upon notification? They should start doing that given the money issues.
For instance, 1.3$ million per year for storage??? Apparently, they have 40 million users, so 1 MB per user (seems reasonable for Signal) means 40TB. You can buy a 4TB SSD for $200, which means you need $2000 one-time for 1MB per user.
How they get from $2000 to 1.3$ million is a mystery.
As for SMS registration, if they are spending 6 million, maybe they should find some way of doing it for free, e.g. Google might be offering it with Firebase, Twitter used to have it, etc. It's not great for privacy, but if they care about that they should just stop using phone numbers.
Routing video calls through a server to obscure IP address seems totally pointless while you are revealing the phone number anyway. And again there might be a way to do this for free, e.g. perhaps using one of free WebRTC STUN/TURN servers that e.g. Google seems to run.
As for bandwidth, a very conservative estimate seems 100 MB per month for each of 40 million users, giving 4 PB per month (though I guess the real usage is 1/10 that at most). Hetzner charges $1/TB, so that gives $4000 per month or $40k per year, overestimated.
Again a mystery how they get from $40k per month to $2.7 million.
Maybe the problem is that they use AWS/GCP/Azure/etc.? They have to be real idiots to use them since everyone knows they are insanely overpriced and should never be used unless a large corporation or deep-pocketed investors are footing the bills or they is no other possible solution.
Perhaps they need to consider stopping dumping money down the drain before asking for donations.
However, usually CPUs don't have enough cores and execution units to compete with GPUs, because they spend the transistors on out-of-order execution, cache and other features instead.
Intel Larrabee was the only attempt to actually make a CPU with a GPU-sized vector unit and they dropped it.
I guess there's reason to wonder whether malware might also be able to set the whole machine on fire.
If you use a normal stroke width (one that makes the empty space in the "m" as wide as the stroke) and width/height ratio for all characters, the problem naturally disappears, and in fact this is not a problem for instance in Linux terminals with the default fonts (normally DejaVu Sans Mono), where the characters look perfectly natural and fine.