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

help-circle

  • Don’t use JSON for the response unless you include the response header to specify it’s application/json. You’re better off with regular plaintext unless the request header Accept asked for JSON and you respond with the right header.

    That also means you can send a response based on what the request asked for.

    403 Forbidden (not Unauthorized) is usually enough most of the time. Most of those errors are not meant for consumption by an application because it’s rare for 4xx codes to have a contract. They tend to go to a log and output for human readers later, so I’d lean on text as default.





  • I just recently started working with ImGui. Rewrite compiled game engines to add support for HDR into games that never supported it? Sure, easy. I can mod most games in an hour if not minutes.

    Make the UI respond like any modern flexible-width UI in the past 15 years? It’s still taking me days. All of the ImGui documentation is hidden behind closed GitHub issues. Like, the expected user experience is to bash your head against something for hours, then submit your very specific issue and wait for the author to tell you what to do if you’re lucky, or link to another issue that vaguely resembles your issue.

    I know some projects, WhatWG for one, follow the convention of, if something is unclear in the documentation, the issue does not get closed until that documentation gets updated so there’s no longer any ambiguity or lack of clarity.





  • ShortFuse@lemmy.worldtoMemes@lemmy.mlplease
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    3 months ago

    No. Microsoft is not liable, at least when it applies to HIPAA.

    The HIPAA Rules apply to covered entities and business associates.

    Individuals, organizations, and agencies that meet the definition of a covered entity under HIPAA must comply with the Rules’ requirements to protect the privacy and security of health information and must provide individuals with certain rights with respect to their health information. If a covered entity engages a business associate to help it carry out its health care activities and functions, the covered entity must have a written business associate contract or other arrangement with the business associate that establishes specifically what the business associate has been engaged to do and requires the business associate to comply with the Rules’ requirements to protect the privacy and security of protected health information. In addition to these contractual obligations, business associates are directly liable for compliance with certain provisions of the HIPAA Rules.

    If an entity does not meet the definition of a covered entity or business associate, it does not have to comply with the HIPAA Rules. See definitions of “business associate” and “covered entity” at 45 CFR 160.103.

    https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html


  • ShortFuse@lemmy.worldtoMemes@lemmy.mlplease
    link
    fedilink
    arrow-up
    18
    ·
    edit-2
    3 months ago

    HIPAA doesn’t even require encryption. It’s considered “addressable”. They just require access be “closed”. You can be HIPAA compliant with just Windows login, event viewer, and notepad.

    (Also HIPAA applies to healthcare providers. Adobe doesn’t need to follow HIPAA data protection, though they probably do because it’s so lax, just because you uploaded a PDF of a medical bill to their cloud.)


  • The transmission is still the same with the exception of things like VRR and DSC. We still send a VBLANK signal which is the electronic signal to tell a CRT to move up to the top of the screen. We don’t change the way things are sent. It’s still top down, left to right. VSync and HSync are still used but make less obvious sense on LCDs. Digital displays translate this.

    Because LCDs convert these signals, we call the time it takes to do the conversion “draw time” but this isn’t as important today. What matters now is the time it takes for a pixel to change one color to another (response time). Because a CRT would fire electrons, the next frame would essentially vanish pretty quickly. LCDs don’t do this.

    Conversely OLEDs are plenty fast, but can’t reproduce the same pixel response without inserting a blank frame with Black Frame Insertion which sacrifices brightness and is being slowly removed.

    Still, most “lag” comes from transmission time. It takes 1/60s of a second to transmit a full frame at 60hz. Divide that 2 to get the “average” lag and CRTs would measure at 8.3333ms. LCDs were happy to get to 10ms.

    Now we can do 120hz which is way more important since even if CRTs are faster, you can get the whole image out in half the time, which “averages” at 4.1666ms, making even a “4ms” slow LCD on PC better than the console running at 60hz on CRT.

    And while CRTs could reach high resolution, these were limited by their HSync speed which usually means lower resolution, because a CRT could only move ever so quickly horizontally.

    Today that translates to an OLED is best for emulating any console that ran at 60hz and better or as good pixel response time if you are willing to do BFI. The main reason why the competitive Melee community still uses CRT is mostly pricing, second to FUD.