A couple months ago I actually verified a build of Telegram on my friend's phone as he thought something might be off and didn't have any issues there (the build matched).
104 karma · joined October 7, 2021
A couple months ago I actually verified a build of Telegram on my friend's phone as he thought something might be off and didn't have any issues there (the build matched).
Granted yes, the version commits are squashed like you said. [1] However I haven't seen source release to lag behind store releases, any sources on that?
0: https://core.telegram.org/reproducible-builds 1: https://github.com/DrKLO/Telegram
I tested this on the machine with a static executable I compiled it looks to me that memory is not shared when statically linked. I thought the point of dynamic linking anyways was to save memory by sharing it (and disk space, though these days we have more than enough for executable code).
Though it could be just that I misunderstand the output of smaps_rollup.
These extensions are standard PHP extensions, so they are the same for each process and user. Extensions like MySQL driver, Postgres driver, ImageMagick bindings and such.
You are correct that no savings would be possible if these were different across each user.
Dynamic linking also leads to better CPU cache utilization and thus higher performance; provided if multiple applications are actually utilizing the dynamically linked library. While RAM is somewhat abundant these days, L1/L2/L3 cache on your CPU most definitely isn't.
Application startup times are also of higher performance when part of the code is already in memory.
EDIT: Let me elaborate a bit on what I mean by "benefiting greatly" with a real world example.
I have a system with around 300 tenants with a minimum of 500 PHP processes online at any given time. A single PHP process is able to load 70MB worth of dynamically linked libraries (PHP extensions) if so chosen by the tenant. I'll just skip libc and other such libraries to give static linking a chance.
With dynamic linking, the maximum memory requirement is 70MB for said extensions.
With static linking, the maximum memory requirement is 35GB for said extensions.
Dynamic linking thus leads to 99,8% cost saving on memory usage. Bear in mind this is at minimum load: static linking requirements will scale linearly with load.
Not to even get started on the performance benefits this brings...
I find palatability an odd thing in the sense that there's the phenomenon of acquired taste. In my experience acquired taste applies the most towards bitter foods and drinks.
I hated the zero-sugar low-fat yoghurt at first. It tasted horrible. The more I got into it however, the more I liked it's rather unique refreshing taste. It freshens the palate unlike any other food and as such I got used to the bitter taste and started to like it instead.
Same thing with beer, it seems everyone hates beer when they taste it the first time. The more you get used to it however, the more you find the taste refreshing I feel. Nothing more refreshing than a cold beer on a hot summer day.
>We suck all the fiber out of foods and feed it back to animals
Fiber for me is somewhat similar. I really love fibrous, almost rock hard, full-grain rye bread. My jaw will get sore from eating that, but there's something to it to really have to chew it down. However I used to hate it and love soft bread in the past: the texture and it's chewiness is akin to an acquired taste.
AFAIK the issue wasn't with low-fat itself per se, but rather that fat was replaced with sugars for things to be palatable. This ended up being much more harmful than having fats, as sugar takes a toll on blood sugar levels and has high energy content itself.
As things got labeled low-fat, people thought this meant a healthier alternative, when in fact it was worse or similar. The view that it was more healthy led to higher rates of consumption.
I consider fats far more healthy than sugar, main issue with fats is their high amount of energy, but from blood sugar standpoint they're a non issue in my opinion.
So yeah there's nothing bad with say no sugar low fat yoghurt healthwise. I eat such yoghurt sometimes and find the taste refreshing. However most people would consider this totally unpalatable as the taste is bitter, not creamy at all and so on.
>Smarter changes than what?
Smarter changes than calling low-fat same as healthy I guess. Careful as in not labeling omission of some nutrient as healthy outright.
At least from my experience of owning multiple APC UPS devices, they have a customizable acceptable power quality setting. In such cases setting them to accept the absolute worst quality of power could probably stop them from tripping on bad power input.
No idea if this affects the end devices, however there's probably a reason other than simply extra profit for the default power quality tolerance setting on those devices. Generally they are set to rather low tolerance threshold as the expected usage scenario is servers and other relatively sensitive equipment.
The models I own aren't really the most expensive either, some of the lower end tower models and they still have configurable acceptable power input settings available. Regarding them tripping on bad input and being "absolute worst", I consider this tripping a feature more than an anti-feature, especially as it is user configurable.
EDIT: Also wanted to add that it is actually _preferable_ for UPS to trip as immediately as possible on bad power input. That is the only purpose of such product after all: to protect the devices attached to it from bad or otherwise inadequate power input.
Seems quite improbable that would be the purpose of the article. The article is basically saying "buy a single UPS instead of buying two to daisy chain them expecting to get better results". If anything, such advice would lead to people buying less devices.
Of course if one had two UPSes laying around for nothing, then I guess daisy chaining might come to mind to get better capacity or something for no extra price. However, generally people don't randomly have UPSs laying around for no reason, so it would make sense to buy higher capacity UPS than two lower capacity UPSs to daisy chain them anyways (and for probably quite similar total cost of ownership).
Well, depending on how you look at things, it was never their work. Their business is and was exactly the same as AWS. However they paid money for the rights to the Redis name and copyright from the original developer after running their business for years in similar manner as AWS.
Of course they rebranded their company into Redis after acquiring the name.
Also it's not like AWS didn't contribute to Redis. I find it plausible that others might have contributed more to Redis than Redis themselves, if we exclude the contributions by the original developer when he was independent.
Correct me if I'm wrong, but as far as I know Redis (the company) focuses mainly on building custom stuff on top of Redis, instead of Redis itself.
To be honest I found I got much better grasp on the whole debacle by just reading the court papers themselves.
I switched to iPhone 15 Pro recently from Android and after trying to import my data from Android couple of times and iOS failing to import WhatsApp specifically, I had to resort to buying third party software to perform the message transfer via a Windows laptop.
Bear in mind the import process took like 3 hours each time and I had to keep both phones close to each other, couldn't use them while importing and had to keep power supplied to them.
After about 10 hours of trying, I gave in and put 100$ towards proper third party software to transfer my messages. This is ridiculous, as I have Google Drive on my iPhone with my WhatsApp backups from my old phone, however for one reason or another these backups cannot be utilised by WhatsApp on iOS.
Moving between two Android phones "it just works".
Maybe I misunderstood your point, but could you clarify a bit what you mean? If I open App Store on my iPhone, it is full of third-party software advertisements by default and I don't even know if they can be turned off.
In the EU, reverse engineering is allowed by law if the reason for doing so is interoperability by the one who owns a license to the product in question.
"The authorisation of the rightholder shall not be required where reproduction of the code and translation of its form within the meaning of points (a) and (b) of Article 4(1) are indispensable to obtain the information necessary to achieve the interoperability of an independently created computer program with other programs, provided that the following conditions are met:
(a) those acts are performed by the licensee or by another person having a right to use a copy of a program, or on their behalf by a person authorised to do so;
(b) the information necessary to achieve interoperability has not previously been readily available to the persons referred to in point (a); and
(c) those acts are confined to the parts of the original program which are necessary in order to achieve interoperability."
More information: https://www.vidstromlabs.com/blog/the-legal-boundaries-of-re...
The article content mentions driving though.
In VMs as far as I know the attack surface is much smaller as the interaction between the guest and host kernel is limited.
Also we are within the EU, IANAL but to me this seems like an obvious violation of GDPR.
To me it seems Google has given ample time to either migrate off of it or to become a customer.
The first one was pretty bad, high fever (like 104F) for a week or so, lost sense of smell completely for months and had pretty bad coughing for some time. I have asthma, so I had to up my medicine dosage as high as allowed and the residual feeling in my lungs lasted for about 6 months in total.
Omicron last month I had a high 103.28F fever for one day, some cough and that was about it. Very odd fever in that it literally lasted for a little over 24 hours and then it was gone.
This applies to any license. BSD/MIT/ISC rules can be broken as well and the only means to rectify it in the case that the other party refuses to cooperate is to resort to litigation.
Electron apps on the other hand are very obvious from their resource usage, general laggyness and slow startup time. Say compare Discord (Electron) to Telegram (Qt) and it's like night and day.
As someone who has recovered from covid before the vaccines, it feels unfair to be forced to take the vaccine when the risks seem to outweigh the benefits.
No one seems to even notice the people with natural immunity, we are always skipped when having a discussion about vaccines.