• 0 Posts
  • 679 Comments
Joined 1 year ago
cake
Cake day: July 18th, 2023

help-circle

  • Outlook is garbage. Everything Microsoft does is garbage and consumer hostile, except for visual studio code. Anyone who’s used Google business apps knows this. Teams is such an unproductive joke I refuse to work for any company that uses it. It’s evidence a company is cheap and values cost cutting more than efficiency.

    I had a family 365 account to backup my parent’s shit. Even though their PC’s were logged into their fucking Microsoft accounts, and backed up to OneDrive, Outlook displayed ads and couldn’t be linked to their subscription without changing their account emails. Ads were also re-inserted into their OS, even though I already ran multiple scripts to disable them all previously. Complete joke. Cancelled that shit.



  • Custom domains mean that if the alias provider enshittifies, you can switch to any other provider near-instantly. As long as you never use the domains to host illegal or dodgy shit it’s extremely unlikely you’ll ever lose them — far less likely than losing a gmail or whatever.

    With SL you can avoid spam by using the “beta” (been beta for 3+ years lol) “auto create” option instead of a catch-all, meaning that you can direct emails to different inboxes (or do nothing) based on specific regex strings you control — up to 100 of them. I had a catch-all regex (.*) as my # 100 and it took 2 years to receive catch-all fishing spam. Then I removed it and now have only random strings (e.g. .*fgyu.*) so new emails must have them if they want to get somewhere. Everything else bounces. All previous emails continue to work until you disable them individually.

    I use a mix:

    • SL-domains: anything I don’t give a shit about.
    • Non-PII domain: anything I would want to persist if I changed provider, but don’t need my identity, or can give out a unique email in-person.
    • PII-domain: banks and all other services tied to my identity.
    • Top-Secret-PII-domain: critical services that could compromise all others (password manager, email/OS accounts, domain name registrar).














  • The obvious solution to me is sponsorblock switching to sampling pixels out of each frame, like that project that encoded data into video streams (yet resilient to compression), there are algorithms that could fingerprint any ad with an extremely high degree of accuracy. It’d be more complex than the current implementation, but it’d also be more resilient. I’d settle for it hiding the video and suppressing the audio for the ads duration, possibly displaying a countdown timer, vs actually watching the ad. Then Youtube would get paid, but have no way of knowing you haven’t seen the ad, and the metrics around their ad effectiveness would ultimately suffer, so users still win.

    You could even go so far as to have the client cache the video, several minutes in advance, dropping all the ad frames, so it’s a seamless experience for the user. I got money, but will spend 10x as much ensuring Google gets less from me. It ain’t about money. It’s about sending a message!