• 0 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle






  • Your dad is right. On desktop, navigation is on the left. On tablet, you shrink it to a rail. On mobile it should be a dismissible nav drawer.

    The top menus, especially the flyover(on mouse hover), are bad for accessibility because they convert a non-committal action (hover) to a context changing one (focus). It’s a uniquely web-only invention and thankfully falling out of usage. (Unless you mean menubar/toolbar. Those are fine but extremely rare on Web.)




  • Maybe I misunderstood the point of data, but I was making the point that they don’t need to perform complex tracking or rely on non-anonymized data. Invading privacy isn’t a very important part of their business model. People still freely feed them data either directly (captcha with OCR scan or Street View images; adding location reviews, photos, and details; YouTube likes and subscriptions) or indirectly (searches and links you click after; YouTube views; places you navigate to and what time; your location when you request navigation directions).

    The tagging of data around specific people (privacy) which the EU is very concerned about, I feel, is grossly overemphasized. Just counters on what gets pinged and when on a transactional basis is very much good enough for Google’s business model.


  • As you continue to use their services you are shown ads or use services other companies have paid to have linked to. Even when things seem “free” they are never free. Google Maps makes money off charging their API for businesses. They charge what they do because their data quality is high. Their data quality is high because they track usage as well as ask users to improve their data (like ask if a restaurant has table service). Every time you search for a business or call a business because a Google search that gets tracked and compared. Businesses can also pay to appear higher in advertised search rankings.

    TL;DR: You are given free access to improve Google’s data and they sell off that improved data to companies, or charge for higher visibility to their potential customers.


  • I still code with the mindset of “I need my software to be good or my clients will leave.”

    Google no longer operates like this. None of what you listed has any financial benefit to Google. You’re not going anywhere. All they stand to do is make more money off of you. If they can simplify the software, from being handcrafted by humans perfectly for you, to, instead, generated by an unsalaried AI, they’ll do that. They stand to lose mostly nothing and gain by reducing their workforce.

    The competition for quality doesn’t exist because the money they save by moving to AI is apparent across the industry. Everyone is looking to use it meaning the only competition is who can provide better cheap AI, not who can make a better product for their users.


  • Years (decades) ago it wasn’t uncommon to create self-signed/local CAs for active directory, but it’s really uncommon today since everything is internet facing and we have things like Let’s Encrypt.

    It’s so old, the “What’s New” article from Microsoft references Windows Server 2012 which is around when I stopped working on Windows Server. I kinda remember it, and you needing to add the server’s cert to your trusted roots. (I don’t know about Linux, but the concept is the same, I’m sure. I never tried generating certificates, but know all the other client -side stuff. Basically you need a way to fulfill CSRs.)

    https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/

    What you’d want to do it in Windows is all there, and Microsoft made that pretty easy back then to integrate with all their platforms and services, but I’d caution, do you really want to implement 10+ year old tech?






  • You’re mostly right, if not completely right. VPN is encrypted with SSL so the ISPs only see that you exchanged information with a VPN, but not what is being exchanged.

    You may consider that maybe the ISPs can also figure out who else connects to the VPN and maybe deduce some information that way, but they can’t know everyone who uses the VPN, only those on their ISP that use it. So you can exchange information with somebody in Antarctica and the ISP has no way of knowing if it’s somebody outside or inside their ISP.

    Also, on the point of services that are not HTTPS, don’t confuse encrypted protocols with the SSL of the VPN. Your ISP will not see your unencrypted packets either if you tunnel it through your VPN. They can’t see your DNS or ping requests (assuming you are using an IP based proxy, not using a SOCKS proxy). But your VPN provider can see those unencrypted requests. So you’re choosing to trust the VPN provider with those opaque requests over your ISP.

    And last, about DNS-over-HTTP, a reverse DNS is enough for your ISP to know what domain you’re connecting to in a lot of the cases, regardless if you hide the domain name resolution. Of course, sites using shared CDNs mitigate this, but not all do.