So what's 0x89 at the start? It's outside the ASCII range.
3,927 karma · joined October 30, 2012
So what's 0x89 at the start? It's outside the ASCII range.
In ASCII: "[\x89]PNG\r\n[SUB]\n"
Is there any information on the origin of these bytes? Why were they chosen like that?
He fixed all 4 of them in 20 minutes. When he drilled open one of the teeth, he showed me how it looked with one of these small cameras that you could see live on the screen. It was absolutely obvious that there was a considerable cavity.
Explaining to your customers what needs to be done, proving it with pictures and/or x-rays, and explaining the different options generates a lot of trust.
https://www.coredump.ch/2017/04/13/lorawan-868mhz-antenna-te...
https://www.coredump.ch/2017/04/30/lorawan-868mhz-antenna-te...
There are quite a few things wrong with that, first of all the efficiency is terrible (that's why they're banned in Switzerland since 2009), secondly the house installations in a lot of homes would probably not be able to cope with the power required to heat all rooms (in my apartment in Switzerland, the fuse would pop out when I turn on two of those 2000W heaters). Third, it's far less convenient if you need to set the heat in every room separately, instead of turning on/up/down/off the central heating system when the outside weather changes.
Alpine solar power plants are a huge deal right now, and cause a lot of discussions. They provide big benefits over solar on rooftops in the valley, because they are usually above the fogline and provide better efficiency during winter.
This is the first alpine solar power plant that's fully operational since August: https://www.axpo.com/ch/en/about-us/energy-knowledge.detail.... It's mounted on a dam and thus had less issues with permissions (as it's mounted on an already existing structure with existing power infrastructure).
Here's an English article about two big planned projects in Gondo and Grengiols: https://www.swissinfo.ch/eng/mountaintop-solar-farms-spark-t...
Here's an early-morning photo taken with the Fuji: https://tmp.dbrgn.ch/DSCF7064.JPG (Either DR200 or DR400, not sure anymore). And here with the Pixel 3a: https://tmp.dbrgn.ch/PXL_20220709_033446459.jpg Of course, the photo taken with the smartphone has lots of artifacts, looks mushy when zoomed in, and the optical quality is far from the Fuji. In other words, it looks good on the phone, but not on a computer screen. But considering the differences in sensor size, it's still very impressive. (Fuji also has a built-in HDR mode, but so far I wasn't fond of the results.)
On the other hand, my old Pixel 3a delivers much better dynamic range in low-light situations with its HDR mode. (Of course, it only looks good on the phone, not on the computer screen, but I sometimes wish the Fuji hat better HDR.)
- "Organic Maps" (a fork of the old MapsMe codebase) if you want a clean, simple user experience
- "OSMAnd" if you want a very powerful, highly customizable map application, which comes at the cost of a steeper learning curve
Both apps are open source and support navigation, offline maps and POI search.
The things I miss most compared to Google Maps is live traffic information and the powerful search. However, this has a privacy cost, so I generally try to use OSM first, and only fall back to Google Maps (in the browser) if I really need to.
Locally made honey (i.e. not from South America) in Switzerland usually costs significantly more than 10€ :)
Holy moly, what do all these people actually do all day long?
Also, assuming an average annual wage of 80k USD, that would mean 6.8 billion USD of wage costs every year. That's quite something.
I have yet to find someone that can explain me how homomorphic encryption works in a way that I fully understand. And I'm a software engineer. I understand RSA or Diffie Hellman. A lot of people understand RSA or Diffie Hellman. Almost nobody understands homomorphic encryption. This means that almost nobody even has the necessary base knowledge to even being able to review an e-voting system.
Without voting secrecy, I'd say that building a robust system would work reasonably well. With voting secrecy, it's a different story.
In contrast, paper and mail voting are things that are technically less secure than a well-designed e-voting system, but they can be understood by laypeople. In Switzerland, my vote goes into a ballot box, guarded by people from different parties. They are counted by citizens from different parties, with many people in the same room. Manipulation has happened in the past, but it has always happened in a constrained scope (e.g. people fishing voting ballots out of the mailboxes of their neighbors). And if it happens large-scale in a single town, this may be detected by statistical analysis ("the number of votes for a certain party is unusually high or low compared to other similar towns"). If citizens don't trust the count, they can request a re-count of the sealed voting ballots by other people.
Making voting simpler is a good thing. In Switzerland, we have had mail voting for a long time now. Yes, you still need to fill out a piece of paper and bring it to a post box, but the thing that takes the most time is actually informing yourself about the things/laws/referendums you're voting on, not filling out the paper. And the attack vector on mail voting is easy to understand.
The problem with e-voting is not security, it's trust. If we erode trust in our voting systems, we erode trust in our democracy. This has already started to happen in a few places, most notably in some areas in the US where e-voting systems are deployed, and where certain groups of people keep repeating their allegations of voter fraud. (They can claim this about regular voting as well, but it's easier to disprove than with closed e-voting systems that only very few "experts" can understand.)
https://www.srf.ch/news/schweiz/elektronische-stimmabgabe-ha...
https://www.heise.de/news/Schweizer-Post-Hacker-konnten-E-Vo...
Jetbrains make good products. And it's great that they're trying to explore the potential for a more lightweight editor based on their technology.
In any case, a Rust string is inherently a growable data structure. It has a capacity and a size. If the size exceeds the capacity, it is reallocated.
Does Rust for Linux have "mystring.push_str(" and then we ate a whole cake,")"? If yes, why is "+=" implicit and "push_str" is not?
From what I understand, this is an API to write applications against a common interface, which can run on different hardware devices. An abstraction layer for security key apps. Similar to Java Card, but in a more modern way. Is this something that would or could be compatible with Tillitis?