> Conventional contact tracing methods also haven’t been faring well.
Despite this, it doesn’t even bother to identify the many reasons tracing apps might not be widely adopted yet, in particular privacy concerns (although it does mention that “draconian” approaches are the only ones proven to work so far, as if that proves that privacy respecting approaches can’t be useful at all.)
Even more fundamental than privacy, though, is do people even know that these apps exist? Personally I’ve only heard some rumblings about the Google/Apple api, and not much more, and I’m guessing I’m far more aware of the existence of these apps than many people.
Ultimately, it’s far too early to declare “failure” on this front.
Edit: According to 9to5 Mac, there are still no apps in the U.S. using the Apple/Google API as of June 18. https://9to5mac.com/2020/05/19/how-to-turn-on-off-covid-19-c...
Speaking for Ireland the app was heavily publicised, and there's even a prominent "Share app" feature in the app itself.
https://www.bbc.com/news/technology-53525712
It was also donated to open source.
https://www.nearform.com/blog/ireland-donates-contact-tracin...
While that is useful I think each country will face its own challenges with adoption.
From the article:
> It also reveals that, whatever the people of Ireland have been told, their app is collecting centralised data on them.
The signup flow has a very obvious and well written opt-in for collection of anonymised data to help track how well the app is working, which was mentioned by the BBC article linked. I don't think people are being mislead.
I personally decided not to enable that, but did give the app my phone number to be shared in the event I'm a close contact.
> it has been in use, it is claimed to have resulted in 91 “close contact exposure alerts”, which is remarkably few.
That they know of, as those users either opted in to the anonymous tracking or (possibly) gave their phone number. It'd be useful to know how the install base per the usual Android/iOS stats compare with the anonymous tracking enablement, but those numbers haven't been shared as far as I'm aware.
Right now our overall case numbers are low enough (around 20 per day) that it's likely hard to tell how effective the app is. However our R is currently estimated at 1.1, so even a little help from the app could help keep us below 1.
Taking your example you could push without sending a packet on every event by instead accumulating a counter in memory, and pushing out the current total every N seconds to your preferred push-based monitoring system. You could even do this on top of a Prometheus client library, some of the official ones even as a demo allow pushing to Graphite with just two lines of code: https://github.com/prometheus/client_python#graphite
In my personal opinion, pull is overall better than push but only very slightly. Each have their own problems you'll hit as you scale, but those problems can be engineered around in both cases.
Disclaimer: Prometheus developer
If you like this kind of game, but would want something not as demanding, try Rimworld. Out of all dwarffortresslikes (I don't think that calling them Dward Fortress clones is fair), it's got a good amount of polish, reasonable 2d graphics (nothing too fancy, but looks nice) and most importantly, you don't feel as if you have to manually tweak every little thing. You still can, you just don't have to.
It allows you to layer your inputs and different overlays together to create a single video output that includes things such as video games, webcam feed, etc. The video output is typically either recorded straight to video file for upload to youtube, or for streaming directly to a supported streaming service.
It's not purely used for video games, mind you.
In this case I believe the idea is that you would use OBS on your local workstation to setup your own web cam and a view of your desktop / work space for the purposes of peer development etc, and then pipe that out as a virtual webcam to other software that only support webcams as inputs.
That's my guess for what's going on here. Hope someone gets some good money from this.
Indeed. I also use it to stream sports with the scores as an overlay, and to record training videos.
Basically if you're doing anything "live" with video, it's the tool you want.
What's the problem with it?
For a small team/company, what are some good tips or resources on how to start an engineering blog? We've worked on many interesting challenges and I know the team would have a lot of insights to share, but it can be difficult to find and justify the time that writing a good article takes, and it's not something that everyone is necessarily interested in doing either.
I'm curious about the mention of Cloudflare's culture of "internal blogging". That seems to me like it could be a first step in that direction.
I'd still keep the repo wide tag for opt-in, but also optionally provide issue level opt-in.
Alternatively, you can provide a platform where participants can self regulate...e.g. like spammers called out on r/programming or maybe a spam detection algo.
Edit: maybe the incentives can also be altered. E.g. sticker for non opt-in repos, t-shirt for opt-in ones. Hmm solving bad actor behaviour is an interesting problem
At least for Prometheus the ones we tagged with hacktoberfest are ones we'd expect a new developer to have a good chance to be able to complete.
I don't think we should be disincentive people who attempt to instead tackle more thorny issues.