• 0 Posts
  • 178 Comments
Joined 2 years ago
cake
Cake day: April 3rd, 2024

help-circle
  • In theory:

    Player: “Copilot, give me a list of all orifices I can fuck xXx_360noscope_xXx’s mom in. Assume I have an extremely small penis.”

    Copilot: “You exclusively play the multiplayer mode of AAA games so that’s already assumed. Here’s your list…”

    In practice:

    Player: “Copilot, give me a list of all orifices I can fuck xXx_360noscope_xXx’s mom in. Assume I have an extremely small penis.”

    Copilot: “I can’t help you with that but did you know you can subscribe to Microsoft® 365™ Copilot® for as little as $19.99, getting access to the industry standard in office productivity tools? Certainly xXx_360noscope_xXx will be impressed by your professional Outlook® presentations and seamless integration with Teams®.”

    Player: “My penis isn’t that small and neither is his.”

    xXx_360noscope_xXx: “Yeah, dude. That was uncalled for.”












  • Yeah. 60% more responsive for something infamous for taking multiple seconds to launch is depressingly bad. That’s “not even trying” levels of improvement.

    The start menu should open essentially instantly (excluding optional animations) – 100 ms is good, 200 ms is somewhat adequate. They’re aiming for somewhere between 400 and 1200 ms.

    I hope for them that they underpromise and overdeliver because this does not inspire confidence.



  • So your argument is that since you are opposed to the app’s very existence it’s immoral to test it for security flaws.

    I’d like to argue against that with the principle of defense in depth. I’m also not a friend of OS-level age verification and would like it to be dropped. But if it is implemented I want it to be implemented in a way that isn’t wildly insecure. I can simultaneously argue against the principle as a whole and insist that any implementation of it be secure. If it does come I at least want the damage from a botched implementation to be mitigated.

    To use your cage analogy, I can both complain about the principle of caging people and about the fact that the cage is badly made and poses an injury risk to the people inside it. Neither is acceptable.



  • Dev: Why was my app rejected?

    Apple: Your app was rejected because it uses a payment processor that is not allowed on the App Store. Is there anything else I can help you with?

    Dev: My app doesn’t contain any payment functionality at all!

    Apple: I’m sorry, I made a like mistake there. Please contact the App Store support team to help you with this kind of issue.

    Dev: You are the App Store support team!

    Apple: That is entirely correct! Please allow me to refer you to section 14 of the Apple Developer Agreement to show why your payment processor is not supported:

    [Link: to the Apple Developer Agreement, section 14: Disclaimer of Liability]