And a \n.

Nice riposte, OP.

Either do a left join and repeat all the post values for every tag or do two round-trip queries and manually join them in code.

JSON_ARRAYAGG. You’ll get the object all tidied up by database in one trip with no need to manipulate on the receiving client.

I recently tried MariaDB for a project and it was kinda neat, having only really messed with DynamoDB and 2012 era MsSQL. All the modern SQL languages support it, though MariaDB and MySQL don’t exactly follow the spec.

When I document code I have this problem with indices vs indexes.

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

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.)

Burn-in is a misnomer.

OLEDs don’t burn their image into anything. CRTs used to burn in right onto the screen making it impossible to fix without physically changing the “glass” (really the phosphor screen).

What happens is the OLED burns out unevenly, causing some areas to be weaker than others. That clearly shows when you try to show all the colors (white) because some areas can no longer get as bright as their neighboring areas. It is reminiscent of CRT burn-in. LCDs just have one big backlight (or multiple if they have zones) so unevenness from burnout in LCDs is rarely seen, though still a thing.

So, OLED manufacturers do things to avoid areas from burning out from staying on for too long like pixel shifting, reducing refresh rate, or dimming areas that don’t change for a long time (like logos).

There is a secondary issue that looks like burn-in which is the panel’s ability to detect how long a pixel has been lit. If it can’t detect properly, then it will not give an even image. This is corrected every once in a while with “compensation cycles” but some panels are notorious for not doing them (Samsung), but once you do, it removes most commonly seen “burn-in”.

You’d have to really, really leave the same image on your screen for months for it to have any noticeable in real world usage, at least with modern OLED TVs. You would normally worry more about the panel dimming too much over a long period of time, but I don’t believe lifetime is any worse than standard LCD.

TL;DR: Watch RTings explain it

Phone material stopped mattering the moment camera bumps became a thing. Now, nearly everyone slaps a case to balance out the bump.

That said, I miss my completely mirrored-back Sony Xperia Z5 Premium.

People can beat this game with their eyes closed.

I didn’t really care about this thread until I read this comment.

The Who were kinda silly (eg: Boris the Spider) in their early years.

VSCode will add a yellow box around the character and tell you it’s an uncommon glyph.

https://code.visualstudio.com/updates/v1_63#_unicode-highlighting

To note, this came about because it could be valid code and it’s a security risk from copy/pasting malicious code. See:

https://certitude.consulting/blog/en/invisible-backdoor/

AmazFit BIP series watches are pretty good. It’s amazing how horrible the Android OS is for watches but Apple set the tone saying 18 hours is enough.

Somebody face-swap them all.

Steam has limited rollback support from the command line which we had to do plenty of times for Starfield when working on Luma. Sometimes updates are small. Sometimes the entire exe gets reshuffled so you have to find where to patch the exe all over again.

All the versions are apparently there. You just need to download the “depot” and it’ll dump into a folder. From there you copy that folder over your game directly.

It also works the other way around. I can download the depot for the latest version and stay on the version I’m at. It’s useful to pick apart and diff what was actually changed.

Why they can’t add that as an option I’m not sure. That seems more of a UX/UI issue rather than a technical one (like avoiding people using old versions on the web server).

I was about to mod the game for HDR and then found out news of FO4 getting updated.

Updates break mods. Just how it is. Though, after seeing the work needed for modding Starfield after each exe change, I’m doing shader replacement now. As long as they don’t change from DirectX, I should be good.

Edit: Nevermind. Somebody asked me for help and got roped in. Got HDR working. Let’s see if it actually lasts.

Edit2: Just gotta fix TAA. Source

Your dad is right. On desktop, navigation is on the left. On tablet, you shrink it to a rail. On mobile it should be a dismissible nav drawer.

The top menus, especially the flyover(on mouse hover), are bad for accessibility because they convert a non-committal action (hover) to a context changing one (focus). It’s a uniquely web-only invention and thankfully falling out of usage. (Unless you mean menubar/toolbar. Those are fine but extremely rare on Web.)

Also you’re supporting modders through Donation Points. Creators get real money proportional to mod download count. The mods are still free, to clarify.

I’m enjoying my Plex one and Nexus Mods. The latter one was in 2013 and cost me $40. Today the yearly subscription is $70.

The entire Material Design framework in JS and Web Components in 80kb

https://clshortfuse.github.io/materialdesignweb/components/buttons.html

JS and Web Components are not the problem. Poor design is.