afaik onlyoffice is russian, and has contracts with the russian govt and military
yes and no… essentially they’re http services that people run, so they can either be closed or FOSS… i could see a future where there’s like those 1-click “run on <serverless platform>” on github pages and you can audit the code if you want, and self host
they call them “feeds” if you’re interested in going deep
and you’re just using the term accessibility to mean a11y… the word accessibility is far broader than simply accessibility standards for people with disabilities
and bluesky doesn’t have a default algorithm either, but allows you to subscribe to algorithms created by other people
being able to choose how the information is presented is the way
every creator that i’m aware of that has done a “how i make money” video rates adsense very low
a chroot is different, but it’s an easy way to get an idea of what docker is:
it also contains all the libraries and binaries that reference each other, such that if you call commands they use the structure of the chroot
this is far more relevant to a basic understanding of what docker does than explaining kernel namespaces. once you have the knowledge of “shipping around applications including dependencies”, then you can delve into isolation and other kinds of virtualisation
afaik most YT creators get their money from sponsor blocks rather than ads these days, so nothing really changes there… i think the combination of sponsors and some patreon-style system is plenty, so i’m not sure monetisation is the issue
ahhh right! i see! yup that’d ruin everything 😭 you’d have to make some correlations to find the registration then
and worth noting that by “publicly available” here, it’s not like it’s published on some FAA API: ADS-B is broadcast from all aircraft, and anyone can receive its data… these services run by networks for regular members of the public contributing the data from their ADS-B receivers
ADS-B is public broadcast though… if you’re in range of the plane, you can pick up its air traffic control data (elevation, speed, heading, registration, etc)… services like flight radar 24 don’t work on FAA data: they are a huge network of regular people across the globe with ADS-B receivers contributing everything they see
adding so it’s archived in as many places as possible:
the reg is N628TS, and you can track it with any ADS-B service
ADS-B is broadcast from the plane, and able to be picked up by any in-range receiver… services like flight radar 24 aggregate many receivers across the world run by ordinary people
it’s not even innovation at this point… maybe if they didn’t fucking suck harder than a 10yo alternative
equally, please don’t imply that you understand global frustration at the US right now
tbh i find they’re really similar to ANZAC biscuits (but ANZAC biscuits are even better because they’re chewy!)
Resource not found Data not found (client error). Data not found (server error)
they are all the same thing; there is no useful, practical distinction between them
if we request a list of objects and nothing was found, because we asked for a date when there was no data, its not an error. But i suppose many still just throw around exceptions still instead of handle them properly
it’s an empty array: not found when requesting something specific is an error… that’s different to here is the complete set of 0 objects… like like if you have an array and request an index that doesn’t exist you get an exception, but that doesn’t mean an empty array is exceptional: it is in fact very valid
using an error code for a non-error
well, it is an error though. you have requested a URI for an object that doesn’t exist: it doesn’t matter whether it’s a resource or an individual thing
remember that HTTP youre asking the server for some object matching a URI: please give me the object matching /users/bananoidandroid and /userssssss/bananoidandroid may both not be found for the exact same reason: the object referenced by that string does not exist
here’s the spec definition for 404
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
when you’re dealing with specs, deciding not to follow them because you feel like they’re wrong is not appropriate… this leads to bugs and issues in compliant tools because they make assumptions about what things mean
200 means the thing that you asked completed successfully
here’s the definition of 200:
The request has succeeded. The information returned with the response is dependent on the method used in the request, for example:
GET an entity corresponding to the requested resource is sent in the response;
HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;
POST an entity describing or containing the result of the action;
TRACE an entity containing the request message as received by the end server.
*edit: when talking about compliant, standard tools the classic example is transparent cache: a GET should not transform the resource and thus a GET with response of 200 can be cached… an API that uses a GET to modify a resource may cause transparent proxies (or CDNs) to significantly mishandle the user request… same goes for 200 vs 4xx and 5xx: proxies know that 200 means what it means and may cache based on that, where 5xx should never be cached and 4xx is probably dependant on which specific 4xx
error codes aren’t about who’s at fault… you don’t send a 404 because it’s the users or the servers fault. it’s information… a 404 says something doesn’t exist… it’s nobody’s fault; it just is
a 4xx says the request, if tried again without changes or external intervention, is unlikely to succeed
a 5xx says the request might have been fine but some other problem that you can’t control occurred so may be retried without changes at a later time
these are all standard things that are treated in standard ways by generic HTTP libraries… look at, eg axios: a javascript HTTP library that’s often thinly wrapped to build API clients… a 200 is just passed through as success, where 4xx and 5xx will throw an error: exactly what you’d want if you try to retrieve a non-existent object or submit a malformed payload…
this is standard behaviour for a lot of HTTP libraries, and helps people accidentally write better code - an explosion is better than silence for unhandled exceptions
it was really useful but in typical apple fashion the defaults were pretty simplistic… if you customised it by installing things like better touch bar and spent time integrating it with your workflow, it was great
but also, i don’t miss it much
i’m sure if we have palm rejection worked out in tablets, ass cheek rejection is absolutely future table-screen tech