The README states:
Proudly written without AI.
HN user
The README states:
Proudly written without AI.
For Apple Business Manager, Apple forces you to create a separate new account.
Tests are called "evals" (evaluations) in the AI product development world. Basically you let humans review LLM output or feed it to another LLM with instructions how to evaluate it.
https://www.lennysnewsletter.com/p/beyond-vibe-checks-a-pms-...
Scroll down to the third photo. The article is about this design.
A similar thing is the ULANZI TC001 (50€ on Amazon), with the firmware AWTRIX 3 (https://blueforcer.github.io/awtrix3/).
From the article:
The mobile phones were tested by an accredited laboratory, which allows the ANFR to ensure that the SAR values comply with European regulation.
No, it was 48°C air temperature. The "Debunking" was a hoax and this explained in the article you linked.
You are wrong, the idea is much older and the idea for the current version (initially called 1-2-3 Ticket) was suggested by the green party in 2013 already.
More Infos in the history (in German): https://kurier.at/politik/inland/gruene-spoe-oder-oevp-wer-h...
It's handled by the GDPR. Companies are forced to report a leak to the authorities and the max. penalties are very high.
Jitsi does not re-encode video streams on the server, it's a SFU (selective forwarding unit) and just forwards (some) video streams to the other participators. When Simulcast is enabled, multiple resolutions of your video are streamed to the Jitsi server and it only sends those streams to clients which they asked for (participants can choose the quality of video they receive, in the UI)
can someone go back in history and still find the registrant?
Yes, there are some services which offer this, e.g.:
Note: there is a website that shows the real ip addresses of (some?) cloudflare customers: http://www.crimeflare.com/cfs.html
OTR is something a lot of people use and trust. It also makes it easier for users to use our service with third-party clients later that already support OTR. Plausible deniability might not be very important for companies, I agree. We are also looking into other protocols, for the same reasons TextSecure decided to modify OTR: both parties need to be online to exchange keys.
Stefan (ChatGrape)
We started with the GitHub integration but there's a lot more to come. Also see Leo's comment: https://news.ycombinator.com/item?id=8312356
Backend: Django 1.7, Postgres, ElasticSearch, Redis. Running on hetzner root servers in germany.
Frontend: component (https://github.com/componentjs/component) with a lot of custom components, no frameworks.
Using https://codeship.io/ for continuos integration/delivery
Stefan (ChatGrape)