Is there a concept in #programming for whether an #API is inward or outward? For example, suppose I have an interface whose intention is that other code can implement it, but it's only supposed to be called by the internals of my code: it's public for implementation, but internal for callers.
For #API client packages, I want to make sure args are in the form the API expects. Other packages ({checkmate}, {vctrs}) didn't QUITE do what I want, so I https://xkcd.com/927/ 'ed it and made my own!
There's still a lot missing, and I'll likely tweak the errors to make things clearer, but it was done-enough to put it into the world. Enjoy!
> The #CSS#AnchorPositioning#API is a game-changer in #web#development because it lets you natively position elements relative to other elements, known as anchors. This API simplifies complex #layout requirements for many interface features like menus and submenus, tooltips, selects, labels, cards, settings dialogs, and many more.
Was dies genau bedeutet und wie man es verhindert mit Updates oder Alternative #API's gibt muss ich mir noch ansehen.
»Fluent Bit – Schwere Sicherheitslücke bei vielen #Cloud-Anbietern entdeckt:
Das #OpenSource-Programm #FluentBit wird unter anderem von allen großen Cloud-Anbietern wie #AWS und #Google genutzt. Bei der #Protokoll-#Software wurde jetzt eine kritische #Schwachstelle entdeckt, die mehrere Angriffe (#DoS) erlaubt. Ein #Update wird dringend empfohlen.«
FusionDirectory a un nouveau site web 🍾🍾🍾 on se projette dans les 10 prochaines années avec un look plus moderne qui met en avant notre expertise, nos services autour de la gestion des identités #iam#opensource#workflow#rest#api#esr#education
I am now working on my own chess API and it’s actually pretty fun. I learned that using bitboards is apparently very efficient. So I now use 8 64bit bitboards, 2 for the color and 6 for the pieces (I thought about just using 7 because you COULD theoretically represent the colors in one bitboard, but using 2 makes it faster at the expense of an extra 64 bit, which is neglegible). Gonna continue on this in the upcoming days :3
Should you design APIs based on what you (the owning team) think is the best way to expose your domain, or do you make compromises based on the needs of your API's consumers?
(API here refers to any element of the public contract of your service/subsystem/app/domain/context, such as HTTP endpoints or events.)
Updated my Gaming Library page, you can click the title on the spine of a game and it'll open a dialog with more info about it. Recently integrated the PSN API to show trophies and even an icon if relevant. APIs are cool. (manually mapping API IDs to your Notion list, not so cool, but it is necessary!)
PS: Don't try to change the completed status — rude. Also I didn't copy the idea from somebody I look up to with their NYC checklist, nope. 🙃
Is there a more efficient way to check if two accounts follow each other via Mastodon's API, other than fetching followers of both accounts and finding a match?
Why is it so fun to create APIs? Something about it is so oddly satisfying, the image down below is part of my API documentation and its just pure dopamine to look at xD I could do this kind of stuff forever… #api#rustlang#axum#programming#technology#coding#dev#development
API Platform Conference 2024 speaker lineup announced | Les-Tilleuls.coop (les-tilleuls.coop)
We are pleased to announce the speakers for the API Platform Conference 2024. Get ready for two days of inspirational talks and join us!
Building Objects in the API Lifecycle (dev.to)
Table of Content Table of Content Preface Introduction Why are entities bad for...