I mean you could start by composting and not throwing into a landfill… many cities accept with leaf collection
Voyager app users
That’s coming very soon. Probably next week
Anyone else noticing? It seems to be affecting other instances as well, since instances hot link to eachother.
The rate limiting seems to get much worse in the evenings.
lemmy.world:
mander.xyz:
{
"code": "object-request-error",
"msg": "Invalid status 429 Too Many Requests for Some(\\"01/90/24/ad/1d/8d/7e/8a/82/ee/7104ff150707.png\\") - {\n \\"message\\":\\"Too many requests\\"\n}"
}
… at least we voted! (Wisconsin)
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!
(╯°□°）╯︵ ┻━┻
This looks like a bug, can you report it on GitHub?
could the lemmy.ml censorship drama be related to this?
I think it’s just cooling down from Reddit migration. Same thing with Voyager donations (albeit smaller scale).
The script is pretty easy to read and follow along manually if you need to.
Hey there! Voyager for Lemmy dev here.
As I've been adding more mod and admin feature to Voyager, I've realized that self-hosting my own Lemmy instance may help me improve Lemmy moderation and administration in Voyager.
But I had another thought: Why not open up registration to Voyager supporters? It's a win-win: I get more real-world experience administrating a Lemmy instance, and Voyager supporters get a fun additional benefit!
Introducing https://vger.social :)
While I hope this instance is around for the long run, it is new, and therefore still experimental. If vger.social does shut down, I will give everyone at least 60 days notice.
Whut about purple people