julian @julian@activitypub.space
Public

@evan@cosocial.ca if I've been hit by them I've never noticed. It could be that the nature of conversations on the fediverse usually mean NodeBB reaches out to many servers, but the only software I've ever had a problem with is Discourse. It blocks me after 15 requests.

mcc has a toot thread in the hundreds, and when NodeBB discovered it it backfilled the entire thing.

When it hits a 429 NodeBB should probably retry after a cooldown period, but it doesn't at the moment. It just marks it as failed.

Evan Prodromou (@evan@cosocial.ca)

31.3K Posts, 2.09K Following, 11.7K Followers · He/him. Board member at CoSocial.ca. Research Director, Social Web Foundation. Author of "ActivityPub: Programming for the Social Web" from O'Reilly Media. Founder of Wikitravel, StatusNet, identi.ca, Fuzzy.ai. Creator of pump.io. Co-creator of GNU social. Former co-chair of the Social Web Working Group at W3C. Co-author of Activity Streams 2.0. Co-author of ActivityPub. Co-author of OStatus. Grad student in CS at Georgia Tech. Greek, Arab, Palestinian, American, Canadian, Montréalais.

cosocial.ca · CoSocial

🫧 socialcoding.. @smallcircles@social.coop
Public

@julian @evanEvan Prodromou

Voted "No, but.." against backdrop of API task force, where issue tracker has an issue on rate limits.

From perspective of "avoiding misconceptions" I was wondering about a range of issues that have been created, and how they relate to Protocol versus Solution design. See also: github.com/swicg/activitypub-a

I think it may be valuable to define different stakeholder roles, to track people's needs. For thus far I discern in order of importance:

1. Solution developer
2. Protosocial implementer
3. Protocol designer

When asking the question "Should rate limits be part of the protocol?", starting point for design is a firm No.

Solution devs should not be worried about them. Need for rate limits depends on requirements of individual Protosocial impls, and what their goals are.

Protocol-level there's actor introspection. There are no "instances" but Application actors that host Services, including system services, that may expose Rate Limit as metadata.

Conduct "Hammock Driven Development" as per the recommendation of Rich Hickey, creator of Clojure. Creating this issue in follow-up to fediverse discussion started by @dahlia .. In the README there...

Avoid Misconception · Issue #63 · swicg/activitypub-api

Conduct "Hammock Driven Development" as per the recommendation of Rich Hickey, creator of Clojure. Creating this issue in follow-up to fediverse discussion started by @dahlia .. In the README there...

github.com · GitHub

0
1
0

If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116272009707549380 on your instance and quote it. (Note that quoting is not supported in Mastodon.)