If you work with APIs and haven’t dug into OpenAPI yet, here’s a full blown introduction to get you started from absolutely zero context. Written by me, for the excellent folks at @httptoolkit.
Do you have a #cyberdeck for daily use?
Any cool gadgets or #techwear?
Souped up terminal prompt beyond oh-my-zsh?
Any other useful desktop apps which help you trough the day?
All the RGB you can fit into your room?
Preaching the gospel of #Arch Linux?
I kinda feel pretty un-cyber these days and was wondering…
When you visit my #web#server without the trailing dot, it sees the domain name in the #request and redirects the request to the #canonical, correct #URL - with the dot.
Unfortunately, there are a few #HTTP user agents that don't handle the trailing dot correctly. The worst offenders didn't handle the trailing dot at all, but I think most of those have been fixed by now, with the possible exception of #curl.
> Not being content with alienating only the general purpose #JSON#API enthusiasts, let me now proceed to also alienate my erstwhile #hypermedia enthusiast allies by saying:
> I don’t think #contentNegotiation is typically the right approach to returning both JSON and #HTML for most applications.
Which web server is the fastest and most suitable for you if it has to distribute the network requests to different services located in virtual operating systems. It should also be relatively easy to configure 🤔 :BoostOK:
Funny list, aint it? Well, it is kind of worrying. The federation, we knew that, is not looking at status messages at al. This means some 40 percent of the requests made are not honored and are answered with different status messages. In bytes it might not be much but let's assume some 10 million instances are generating some 40 percent faults.... There have been days I would have been given the task to solve it.
Code 200 - OK 49.98% 62231<br></br>Code 202 - Accepted 0.07% 87<br></br>Code 204 - No Content 0.03% 43<br></br>Code 302 - Found 1.87% 2325<br></br>Code 304 - Not Modified 2.37% 2956<br></br>Code 400 - Bad Request 22.14% 27567<br></br>Code 401 - Unauthorized 0.42% 523<br></br>Code 403 - Forbidden 10.44% 12997<br></br>Code 404 - Not Found 8.82% 10985<br></br>Code 408 - Request Timeout 0.02% 21<br></br>Code 409 - Conflict 0.01% 7
> Compression dictionaries are bits of compressible content known ahead of time. They are being used by compression engines to reduce the size of compressed content.
It’s pretty efficient. A proposal is being designed to support compression dictionary with HTTP. It can be pretty impactful on the Web in terms of network bandwidth and speed.
If I read between the lines on the software design for #ActivityPub, I don't think there are actually supposed to be servers per se, or more precisely that servers are supposed to be very simple passthroughs that have some forwarding/processing logic?
If so then this makes some sense, since when AP was being written was a big time for BaaS (Backend as a Service; https://en.wikipedia.org/wiki/Backend_as_a_service ) and that influenced a lot of ideas.
@hrefna
Having seen this movie several times before, IMHO, it's a case of adopting a spec because it can be interoperable and then having it spin out of control when adoption explodes.
I've seen it happen with #smtp#http#html#json#javascript
and because the solution started with a limited scope, it was hard to refactor without breaking things.
It appears that all popular #NodeJS#HTTP client libraries are either deprecated, outdated, or are missing features. As any other sane person would do, I decided to write my own.