Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)Z
Posts
28
Comments
523
Joined
2 yr. ago

  • Today I went to sleep at 7am and woke up at 3pm. Next week I'm just as likely to go to bed at 8pm and wake up at 4am. No real schedule, but I tend to slowly drift forward. Sometimes I get caught on a split schedule where I'll sleep twice a day for half as long.

  • Good to know that's the default. I do definitely see prompts that have "Reject all", plus some banners that only have "Accept all" and "Cookie settings", with "Reject all" or "Necessary cookies only" only visible in the cookie settings. Thanks.

  • Excellent 👍

  • The striking part is that it's so much higher while we're 7 weeks into the year. The other years include all 52 weeks. Also 40 is close to the maximum for previous years on the chart, not the average, which I'd estimate around 25.

  • Pretty striking - I'd add a title to the top and the source in the lower right. Would make it much more shareable.

    Edit: And a note about 2025 only being up to February 17th. Because the graph may outlive the ~next Delta flight~ week.

  • The correct answer in degrees is cos(pi) = 0.99849714986386383364. The correct answer in radians is cos(pi) = -1 (exactly). Any calculator giving you cos(pi) = -1 is definitely in radians mode - and if you mean you're getting cos(pi) = exactly 1, and not 0.998, then that should never happen in any mode, unless it just has two digits of accuracy. Which I doubt any calculator with a 'cos' button has ever had.

    For the record, if using sine, you should have sin(pi) = 0.05480366514878953089 if in degrees mode, or sin(pi) = 0 (exactly) if in radians mode.

  • That comes down to the calculator using radians while you're expecting degrees: cos(0°) = 1, and cos(355/113 degrees) = 0.99849714986386383364. The default for most calculators is to do trig functions in radians, and there we have cos(0) = 1 and cos(π) = -1. π degrees is much closer to 0° than 180° (which is equivalent to π radians), hence the answer for that being almost 1.

    The OPTN button near the SHIFT button will probably let you swap between RADians and DEGrees

  • To be clear, when you say "exactly right", do you mean -1 and 0 or -1 and -2.6776418E-07? Because -2.6776418E-07 is the more accurate answer here. 10+2 digits of accuracy does round the cosine to -1 because its first 13 digits after the decimal are all 9s, while 10+2 decimals of accuracy for the sine should be -0.000000266764 (12 digits) rounded to -0.0000002668 (10 digits rounded), then displayed as -2.668E-07 - so you actually end up with some bonus accuracy in this case. Though that last 8 should round up to a 9.

  • There isn't really an issue here. The reason the cosine value is rounded to -1 while the sine value isn't rounded to 0 is because the cosine value is much closer to -1 than the sine value is to 0. The unrounded (or less rounded) values are cos(355/113) = -0.99999999999996441843 and sin(355/113) = -0.00000026676418906242. So while the sine value is about 10-7 from 0, the cosine value is about 10-13 from -1, 6 orders of magnitude closer. Your calculator's threshold for rounding is just somewhere between those magnitudes.

    As for why the latter two calculations give identical answers, that's just a feature of sine itself: For very small inputs it's an excellent approximation of the identity function, f(x) = x. If you give it any input of similar size to π - 355/113, it'll more likely than not give you the exact same value back out. As x → 0, sin(x) → x. Try it out with other values like 0.0000000123456789.

  • I tried out the 8B deepseek and found it pretty underwhelming - the responses were borderline unrelated to the prompts at times. The smallest I had any respectable output with was the 12B model - which I was able to run, at a somewhat usable speed even.

  • Fair, I didn't realize that. My GPU is a 1060 6 GB so I won't be running any significant LLMs on it. This PC is pretty old at this point.

  • I have 16 GB of RAM and recently tried running local LLM models. Turns out my RAM is a bigger limiting factor than my GPU.

    And, yeah, docker's always taking up 3-4 GB.

  • Expensive or not, we're well past the point where it's optional. Even if 100% of new carbon emissions stopped today, let alone by 2050, we'd need to continue developing carbon capture technologies to take out what we've already put in the atmosphere. Not every part of the fixing process needs to be profitable.

  • I know someone who works in UHC's appeals department. They do in fact overturn the majority of denials which are appealed. Might just be selection bias, though, with only those who have the least ambiguous situations bothering to appeal.

  • Is grandpa's fly open?

  • Hash tables are often used behind the scenes. dicts and sets in python both utilize hash tables internally, for example.

  • And then, to perfectly demonstrate your point: 90% of this comments section!

  • Firefox now includes safeguards to prevent sites from abusing the history API by generating excessive history entries, which can make navigating with the back and forward buttons difficult by cluttering the history. This intervention ensures that such entries, unless interacted with by the user, are skipped when using the back and forward buttons.

    Nice

  • You're right, based on those definitions the word doesn't mean what I intended. I don't know what the right word would be. I used it to mean one who overreacts to relatively minor or inconsequential transgressions, taking drastic, often out-of-proportion or only tangentially relevant actions to rectify perceived harms.

    One example would include people ditching the entire company Proton, an entity with a stellar track record of improving the state of privacy on the internet, after a single member of their board made some dipshit comments. Another example might include the general reaction a few months ago when that misleading story about Mozilla and ad tracking was making the rounds. Other more extreme examples would be the passing of the Patriot Act and invasion of Iraq and Afghanistan following 9/11, or the Israeli response to 2023's attack on them.