The backlog was bigger than I expected...
-
-
You’re not the first fedidev to experience this, Lemmy is just extra
: -
Nice to see your post in here, though! Making good progress?
-
You’re not the first fedidev to experience this, Lemmy is just extra
:flamingos@feddit.uk it’s less that and more Lemmy’s ridiculously effective synchronization mechanic that Mastodon doesn’t utilise!
-
Nice to see your post in here, though! Making good progress?
Better and better every day… Hoping we can get some additional funding to really accelerate development!
-
Less than 3M activities behind now!
-
@julian What did you do to get 3M activities? I'd like to try that too
-
@julian What did you do to get 3M activities? I'd like to try that too
silverpill@mitra.social simple! Respond to a Lemmy server with a 500, and once you hit 40 in one day the instance puts you on a timeout. Repeat as needed until your backlog is 4M activities
-
silverpill@mitra.social simple! Respond to a Lemmy server with a 500, and once you hit 40 in one day the instance puts you on a timeout. Repeat as needed until your backlog is 4M activities
In my case I had a spam protection measure that limited the amount of upvotes per user in one day. Someone on a Lemmy server uploaded past that threshold and NodeBB started sending back 500s.
-
In my case I had a spam protection measure that limited the amount of upvotes per user in one day. Someone on a Lemmy server uploaded past that threshold and NodeBB started sending back 500s.
@julian But shouldn't it respond with something like 429 "Too Many Requests"?
-
Who makes decisions on which features get implemented next?
I’m scared to contribute to any projects because I doubt my work would be utilized. I’m wondering if there’s a schedule or something I can look at, and prepare for upcoming work? or, how do people get involved
-
@julian But shouldn't it respond with something like 429 "Too Many Requests"?
aslakr@mastodon.social it should, yes! The immediate fix was to change the logic so a 200 is sent, but a 429 should work quite well as Lemmy will likely send it back into the delivery queue and (more importantly) not mark it as an error.
-
Who makes decisions on which features get implemented next?
I’m scared to contribute to any projects because I doubt my work would be utilized. I’m wondering if there’s a schedule or something I can look at, and prepare for upcoming work? or, how do people get involved
Depends on the project, and I imagine a lot of the smaller ones are your standard FOSS BDFL leadership.
In my case I’ll likely make a rough milestone list based off our NLNet memorandum and go from there.
