@mesh4545 So it's a bit tricky if you want a particular brand.. a shell game.
@mesh4545 Every state is potentially different. In my area you can often get an appointment ~1 day in ahead if you call around but you often don't know in advance which brand it is. Shipments are chaotic. Pharmacists don't know what's coming or when it will arrive. Many are out of stock or booked up & don't know if they'll get more at all. It's all spontaneous.
Some #covid19 vaccine sites are maintaining brand-specific waiting lists, so you can e.g. be on a call list only for Johnson & Johnson, or only for Moderna, if you want. But most don't offer that & no one publishes this. And vaccinefinder.org is not keeping up with the stock availability data. We need some crowd-sourcing on this data.
@jalvarez The beauty of getting spam through these aliases is you know who leaked it. Consequently, I've discovered & reported breaches on banks. E.g. if you give Chase bank "chase.yadayade@simplelogin.eu" & no one else, and you start getting spam there, it's a strong indicator that Chase was breached. There are orgs you can contact that will do all the legwork of forcing Chase to confess.
@jalvarez Other FSPs are one or the other. on-the-fly: 33mail.com, erine.email, anonaddy.com. generated: simplelogin.eu, burnermail.io, anonaddy.com. (notice anonaddy.com is in both groups) Anonaddy.com is also the only FSP that supports #PGP. So you can give anonaddy your PGP pubkey, & every msg will be encrypted from their server to your inbox.
@jalvarez Some FSPs issue generated addresses instead of on-the-fly. It's more hassle because you must login to generate a new address, but the advantage is that your UID is not in the address, so an attacker can't create aliases for you, and it also protects from your different addresses being tied together. Anonaddy.com supports both generated addresses and on-the-fly addresses.
@jalvarez If you only register for one of the forwarding svc providers (FSP), I'd favor anonaddy.com above all. Some FSPs support on-the-fly aliases, which means you need not login to create a new alias. E.g. you can just spontaneously start using my-github-proj@jalv.33mail.com. on-the-fly FSPs are less hassle, but OTOH your userid appears on every email address, so spammers can abuse that.
@Coffee My Ungoogled Chromium profile doesn't have the same addons that broke this on Firefox, so that's still a mystery.
@Coffee apparently it's different causes for the same behavior on different browsers. I was able to render the page in Firefox after disabling a couple anti-CloudFlare addons, but the search results are still unusable, as it still gives "We’re sorry, the website is temporarily unavailable now. Please try again later" within archive.org. Perhaps my zip code must be 1st saved w/out tor
@fsf is there a way to tune in live, or do we have to wait until an edited version is posted?
@pamaca @themactep@fosstodon.org @jalvarez I should also mention that every git commit potentially has an email address on it. My git config has a different forwarding alias for every repo which I only exposed through git pushes. One of those unique addresses is now getting spam. I'm guessing the attacker simply did a "git clone" to get the address.
@Br0m3x Of course wearing a mask is still necessary b/c the vaccine only reduces transmission risk.
@Br0m3x It's always been known that symptoms increase viral spread, esp. coughing b/c you blast that junk further into the air. The vaccines reduce the viral load & symptoms, which in itself reduces chance of xmission. There are a couple studies that confirm this wrt Pfizer & Moderna: https://www.vox.com/future-perfect/22291959/covid-vaccines-transmission-protect-spread-virus-moderna-pfizer
@Coffee it's the same problem whether I use Firefox over Tor or Ungoogled Chromium over Tor. js enabled.
@Br0m3x I was a bit overboard to say "nearly risk-free" but chance of transmission drops greatly. I would think that should be sufficient for border crossings. If a vaccinated person takes a table in a restaurant, they reduce the chance of xmission for the whole restaurant because they block potentially unvaccinated carriers from the table, plus the ingress transmission risk is negligible.
@Coffee I'm surprised that works for you. when I try to search the db, I just get a spinning circular mahoochy.
@nanook @jsparknz @aral @hypolite Mass surveillance would require #Hushmail to push malicious #javascript to everyone, which would work right up until just one user decides to audit the js code one time. I'd say that's unlikely. Targeting is a risk, so HM is not useful if your threat model includes targeted surveillance.
@josias Actually I think it was 90/10, but anyway.. the docs in the study were embarrassed when they were given the results.