Voyager doesn’t have a global API key, it requests a temporary one per device. There are limits, but not really clear, really depends on what redgifs feels like doing.
I do plan on exposing the error message received from redgifs for more clarity in the future
if you chill on the porn for a day or so it should start working again 😜
Hi, Voyager dev here, I’d like to see a very small, terse API for clients devs to make a more seamless experience!
The MVP IMO would be a way to automatically log the user in when opening the Canvas, perhaps by
And I could see stuff beyond this. Like an API to know event metadata, docs on how to embed Canvas in app (would be great for engagement)
Anywho simple is best but would be awesome for tighter integration of apps/clients with a documented API!
Update: I have a fix in the next release!
It’s not Voyager. I don’t call or integrate with Google. Maybe https://github.com/nextcloud/Android-SingleSignOn/issues/388?
DST is bad, byte me
Guillotine would transport well by bike, like a canoe or kayak…
In fact, you could even make the wheels reusable for a nice kayak trip after using the guillotine! Win win!
No problem. And it should be something that's happened since the beginning of Voyager, so if you notice it get notably worse after a release, let me know.
If kbin releases API docs, a JS client on npm, and then dogfoods it like Lemmy does, I’d be happy to look into it. :)
(But even then, API differences would make this very hard to do well and probably not worth the effort.)
The reason Lemmy has such a great app ecosystem is the backend and front end are completely separate, with a published client layer for communication.
Madison, Wisconsin.
To me at least the speed isn’t a problem. I’d much rather take a 2 day Amtrak (in sleeper) than an 8 hour plane.
The problem is the pricing, and also how much it fluctuates due to the extremely low capacity (one train a day…)
Yeah, that’s fair.. it’s unfortunate, it’s a really important feature