vasametropolis @ vasametropolis @lemm.ee

Posts

0

Comments

10

Joined

1 yr. ago

He’s mad so it worked.

I do this as well - the only exception is work, where I pin a few tabs. Out of curiosity are you an “inbox zero” person? Because I am, and the only parallel I can draw is between that and my similar tab management.

I agree that, generously stated, “reporting neutrality” is completely bogus these days. Everything is so nonchalant.

Apple Intelligence, but actually this time?

We already know which party has more MAGA sympathizers. This was a nice try though.

Annexation is not marriage. It’s rape.

Glad somebody finally said it out loud.

Problem at the moment is money so it won’t be much of a replacement for some time. Europe is going to have to be the primary replacement right now.

Piracy on iOS? Come on now… what region? 9/10 people do not jailbreak or are in a region where they cannot side load by default.

1 or 4 but wrapped in a top level error object. It’s usually best to not use the top level namespace because then you can’t add meta details about the request easily later without changing the original response schema.

Codes are great but I’m usually too lazy to introduce them right away, so I instead have message (which is guaranteed to come back) and context, which is any JSON object and doesn’t adhere to a guaranteed structure. Another poster pointed out that code is way easier for localization since you are probably not localizing your message.

The HTTP status code is generally sufficient to describe what happened without having to catalogue every error with a unique “code”. A context blob is useful for dumping validation errors or any other details about the error that a human could at least rely on for help.

Putting the status code on the body seems helpful but is actually useless, since the only place you can assume it’s always provided is on the response itself and not the body.

In hindsight he would thank you