Closed GoogleCodeExporter closed 9 years ago
Dealing with this requires a standard approach to DoS prevention. We do this in
the reference hub here:
http://code.google.com/p/pubsubhubbub/source/browse/trunk/hub/dos.py
Other hubs aren't fully public and only work for the content providers they
syndicate (like Posterous's hub); those
have no exposure to this attack.
I guess the best thing I can do here is potentially put DoS protections in the
best practices, non-normative part
of the spec.
Original comment by bslatkin
on 19 May 2010 at 5:40
Due to the approaching shutdown of Google Code
(http://google-opensource.blogspot.ch/2015/03/farewell-to-google-code.html)
we're moving all public PubSubHubbub development to the pubsubhubbub
organization on Github:
https://github.com/pubsubhubbub
The protocol spec resides under https://github.com/pubsubhubbub/PubSubHubbub
while the various client libraries and example applications have separate
repositories.
Wiki content has been migrated to the PubSubHubbub project as well:
https://github.com/pubsubhubbub/PubSubHubbub/wiki
Please re-open your issue on GitHub if it's still relevant.
Original comment by the...@google.com
on 18 May 2015 at 7:25
Original issue reported on code.google.com by
alexwilliamsca
on 19 May 2010 at 3:39