On a fediverse server with a versioned client API, what would you expect to happen if an API call is made with a version number higher than what the server supports?
General Discussion
8
Posts
6
Posters
21
Views
-
On a fediverse server with a versioned client API, what would you expect to happen if an API call is made with a version number higher than what the server supports? Should it return an error? Should it take it to mean its highest supported version? Something else?
The API isn't RESTful, the version number is global for all methods (endpoints) and has the format "major.minor".
-
undefined julian@activitypub.space shared this topic on
-
On a fediverse server with a versioned client API, what would you expect to happen if an API call is made with a version number higher than what the server supports? Should it return an error? Should it take it to mean its highest supported version? Something else?
The API isn't RESTful, the version number is global for all methods (endpoints) and has the format "major.minor".
Hi @grishka,
using highest sounds like best effort and makes most sense to me. -
Hi @grishka,
using highest sounds like best effort and makes most sense to me.@mro but what if there are incompatible changes that the app doesn't expect? Like some object having a different format, or some method behaving differently
-
On a fediverse server with a versioned client API, what would you expect to happen if an API call is made with a version number higher than what the server supports? Should it return an error? Should it take it to mean its highest supported version? Something else?
The API isn't RESTful, the version number is global for all methods (endpoints) and has the format "major.minor".
@grishka Return an error that tells the client it's used an unsupported version.
By definition, the server does not know the semantics of the call the client made, so trying to guess and return something in the hope it's correct takes us out of the realm of engineering and into clairvoyance.
-
@grishka Return an error that tells the client it's used an unsupported version.
By definition, the server does not know the semantics of the call the client made, so trying to guess and return something in the hope it's correct takes us out of the realm of engineering and into clairvoyance.
nikclayton@mastodon.social agreed.
It's one thing for a server with a newer API version to be backwards compatible with a request from an older version, but it's impossible to predict the future and handle requests from a newer API client.
Bouncing an error back would be the safest choice.
-
On a fediverse server with a versioned client API, what would you expect to happen if an API call is made with a version number higher than what the server supports? Should it return an error? Should it take it to mean its highest supported version? Something else?
The API isn't RESTful, the version number is global for all methods (endpoints) and has the format "major.minor".
Isn't the convention to put the version in the url? e.g. /api/v3/site
In which case a too-high version gives you a 404 error.
-
Isn't the convention to put the version in the url? e.g. /api/v3/site
In which case a too-high version gives you a 404 error.
@rimu that's for RESTful APIs, mine isn't that because I dislike the concept. I just take the version as the `v` parameter
-
@rimu that's for RESTful APIs, mine isn't that because I dislike the concept. I just take the version as the `v` parameter
@grishka @rimu putting the version in the uri is an older convention and not necessarily a REST(ful) thing either. what i've seen is to use content negotiation via an Accept-Version header
basically if you use conneg then 405 Not Acceptable; if you put versions in uris then 404 Not Found; if you take some parameter or payload then i guess maybe 422 Unprocessable Entity?
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Folgendes habe ich noch gar nicht mitbekommen?
Wisst ihr dazu mehr?Laut https://www.eurosky.social/faq setzen sie nicht auf ActivityPub sondern auf dem AT Protocol von Bluesky auf.
Vergleich der Protokolle siehe
https://www.paulstephenborile.com/2024/11/social-media-protocols-comparison/
-
Entweder übersehe ich was. Aber wenn ich bei Hashtags in meinem #Wordpress Blog brav auf CamelCase achte, wie z.B. #BlueBeanieDay dann macht das #ActivityPub Plugin daraus im Fediverse ein #bluebeanieday
Kann ich da irgendwas machen @pfefferle
-
@jdt one of the first non-social-media uses I've seen for ActivityPub was castling club:
-
An idea. Just a client-side mock-up at this point.
There's quite a bit in the ActivityStreams vocabulary to support this already, but I'd probably want to use some extensions to make it make sense.
-
@julian I was surprised when taking a look at it that the demo instance has been there for 2 years, is barely used by anyone, most are abandoned accounts and half of the functions on it don't work...
All while it's getting positive press.
I think you nailed it about the hype around promise.
-
transicorn@mastodon.social they definitely received a lot of positive press lately, which had me feeling jealous for a bit (why can't my marketing efforts hit the right note?)
I suppose it's always easier to create hype around promise.
-
@saxifraga Yeah, that's definitely one major plus about Mastodon and related projects... being focused on inclusion and having strong policies against hate / discrimination.
I think you'll find most of the people who've been here a long time are here for that very reason aside from perhaps being techies in some ways as well often times.
-
@transicorn couldn’t stand all the hate on those platforms, even as a cis queer person.
I’m on Bluesky, but I’m not sure for how much longer.
