the overload is right below it

  int StreamReader.Read()
  int StreamReader.Read(char[] buffer, int index, int count)

https://github.com/dotnet/runtime/blob/1ba0394d71a4ea6bee7f6...

Here is what actually happened and the prosecution later admitted it. (they first blamed it on the defense android phone)

1. Prosecution receives the file via airdrop, direct data transfer.

2. Prosecution sends the file via gmail to the defense but it gets compressed in the process.

There are 2 ways to send a vid/pic from ios with gmail

1. from gmail app with attachment function, this pops up a window with "processing" (compresses the video, which is poorly worded imo)

2. from ios photos app > share > gmail, this shows a progress bar at the bottom with "compressing"

both ways are easy to overlook, first one is poorly worded and its a very fast process, my test vid with 25mb took <1s and video in question is only 4s/11mb

the real question is, why is there no proper evidence system in place to submit and review(for all 3 parties), using gmail and dropbox sounds very questionable to me.

> 2. Prosecution sends the file via gmail to the defense but it gets compressed in the process.

Does Gmail automatically compress the video? I would presume it complains about size file first, and an inability to send it via email, and refuses to send.

It did not in my testing with a 22mb file, it directly showed up "processing" or "compressing".

The iOS mail app did the same for my test video 22mb > 458K, no questions asked. (unlike images where app lets you select resize options)

In your testing, did gmail also rename the file? Because Binger's copy, the one that was sent to the lab on a flash drive had a completely different name.

you can set a ReadyToRun flag on publish which pre jits your dlls https://docs.microsoft.com/en-us/dotnet/core/deploying/ready...

yes looks to be polling https://github.com/k3s-io/kine/blob/master/pkg/server/watch....

54,08€ was the pre negotiations price in June. Current price is allegedly 15,50€

Are you aware of the datasheets published by rpi? https://www.raspberrypi.org/documentation/hardware/raspberry...

Those are very far from complete datasheets, covering only a small part of the SoC superficially.

Yep, the 200 pages you get from there is a bad joke. Even a relatively simple ARM microcontroller (the STM32F1 series) has over a thousand pages of documentation in the reference manual. A full set of reference documentation for a SoC like the BCM2835 would probably come out to 5-10k+ pages.

It’s a custom pcb in keyboard format with vents at the back and huge metal heat sink/anti flex plate.

Yeah, so I watched a teardown from one of the sibling comments. Looks like there are vents underneath, but no fan (which would have ruined it for me). Turns out it's got both a huge heat spreader and a newer version of the Broadcom SOC. That's really interesting, because it means they've got the bugs ironed out to be able to do a better pi 4 board which isn't so finicky about its enclosures. And that means I could potentially upgrade the pi 3 that's currently sat in my dusty workshop without caring about fans getting clogged. (yes, I know there are passively-cooled pi 4 cases about. They don't quite do it for me.)

Same as DoH or DoT but using WireGuard as transport.

Right so it just encrypts DNS requests, which is what 1.1.1.1 does. What does this app provide that is additional to that?

"How it works: first, an accessibility user signs up at this URL, which is linked in the hCaptcha widget info page. They are given an encrypted cookie that can be used several times per day, but must be refreshed every 24 hours via login."

https://www.hcaptcha.com/accessibility

How on earth is this considered a reasonable accommodation for people with access needs? Stinks of something created with no consultation whatsoever with the accessibility community.

This is bad on so many levels, for starters that you need yet another account.