Norwegian proot with a taste for shitposting Deeply sorry for my photoshop creation

Former account at Kbin

aspe:keyoxide.org:JYRRSWIKLZWX366Y4DONCIEYAE

  • 4 Posts
  • 58 Comments
Joined 5 months ago
cake
Cake day: June 7th, 2024

help-circle




  • I’m currently using a Samsung s21 ultra, and it’s kinda meh. The compass is not bad, it’s horrendous. It used to be offset by say 90 degrees, but nowadays it seems more likely that it’s a random number generator from 0 to 360 degrees, making any maps app bacically unusable unless you look at road markings, and other buildings to guess which way you’re facing. The main camera has over time developed a hardware issue that makes all pictures always out of focus, unless you hit the phone on a hard surface to dislodge the focusing mechanism. From a software standpoint it’s a good device. No major bugs, and it’s pretty stabile.

    My favorite phone was a used Samsung s6 as it felt kinda “flawless”. Battery was good, camera was great (for the time), and hardware was pretty awesome. It was a great phone while it was still getting updates.












  • I was mainly thinking of making some recursion hence why all the subclocks mirror the parent clock (for that given hour). Also I called it clock squared because I didn’t think the resolution would be high enough for people to actually notice the 3rd level of clocks.

    You might notice that some dials don’t really align with the hours they’re supposed to show. That’s because I had to place a bunch of clocks at varying hours with a viewport rendering the parent clock at an angle that probably made it difficult to spot the errors. I rendered it once and didn’t bother re-rendering it once I saw the errors :)