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

help-circle



  • I suppose the last one is halfway true. In the UK before internet access was mainstream, you either had to use the school/work network connection and their weird access control packages, or use the local library. In any case, you actually had to get dressed to use the internet.

    This was when ISDN was a fat pipe, and if you went to the library, had to plan what you was going to look up because you paid for 30mins of access time. After you’d searched for PS1 cheat codes, Ask(ed) Jeeves for a fact to settle an argument, and looked up pictures of the 555-branded Subaru Impreza, it was time to burn off whatever acces time was left on Lycos, Excite, or Google’s directory service to find new cool stuff.

    Old school.










  • Semi-offtopic: my life has gotten a little bit better since I used the Android (other OSes likely have similar functionality) option to block any witheld or blocked caller IDs.

    Partly because it’s rarely anything good these days if it’s a witheld number, but mainly because my workplace’s outbound calls get automatically blocked so work calls don’t get displayed on my phone unless someone uses Skype or a work mobile. Winner.

    9/10 would recommend A+++++ unless you’re on call, of course.




  • Wouldn’t this absolutely hammer the battery though, or at least give the CPU a hard time? My understanding is that offloading the work to a cloud platform means that the processor-intensive inputting, parsing, generating, and outputting operations are done in purpose-built datacentres, and end user devices just receive the prepared answer.

    Wouldn’t this rinse the battery and increase the overall device temperature for “normal” end users?

    Fair warning: I haven’t read the two papers outlined in the article.