marchukov
Joined 9 years ago
Karma
70
Submissions
15
Member since
Jan 14
Recent submissions
Comment · 2 years ago
Comment · 2 years ago
Issues with our upstream network provider is causing intermittent outages. We are having an issue with our upstream network provider which is causing intermittent outages. We are investigating the issue. (08:50 UTC — Jan 10)
We are unable to reach our emergency NOC. We have been attempting to reach the emergency datacenter operations contacts for the past hour without success; there is an issue with their emergency ticketing system. We will have to wait until their non-emergency line is available, which should be at 9 AM EST (ETA 4 hours). (09:56 UTC — Jan 10)
Comment · 3 years ago
Hm. Apparently I was wrong. They indeed "temporarily" disabled it after the credential stuffing attack [1].
[1] https://customercare.23andme.com/hc/en-us/articles/212196868...
Comment · 3 years ago
They still do (update: not they are not). It is not and was not a full genome sequencing, but rather a SNP genotyping. Current 23andme raw report (using their v5 chip) contains around 24K SNPs.
Comment · 3 years ago
Due to legal troubles with LBRY, Odysee is collaborating with Arweave, a decentralized and censorship-resistant storage protocol, to fully decentralize Odysee on top of Arweave. Additionally, they are working on developing new non-tokenized products.
Comment · 3 years ago
From what I was able to read previously, it has no ability to spread by itself and has to be installed by a targeted attack. There is also a tool from Amnesty International that can detect it (or was able to): https://github.com/mvt-project/mvt
It is a race though, so past info may no longer be valid. However, I doubt it will ever be able to spread by itself, since it uses very expensive zero days to infect and they will be quickly fixed after detection.
Comment · 3 years ago
Can anybody recommend an alternative with the following:
1. EU/EEA/Switzerland
2. DNSSEC
3. DNS hosting (with DNSSEC support)
4. WebAuth/FIDO2 2nd factor (with ability to add multiple keys and recovery codes)
Comment · 3 years ago
Exercism have paused community contributions. All PRs are closed by a bot.
TL;DR; We're spending a few months redesigning our volunteering model and giving our key volunteers a break from the work of reviewing community contributions. If you use Exercism purely to learn or mentor, there’s nothing here you need to know (although please read if you’re interested!). If you are a track maintainer, wish to contribute to Exercism, or wish to report a bug/problem, then consider this essential reading
"We are preparing a migration. We do not see a near-term resolution being possible with our upstream network provider and we are preparing to restore service from backups in a new installation. It will take a while, but we are all-hands to address the issue."