When using trustedpeer, flooding check should not be done. #786

Closed
opened 2015-03-06 23:10:13 +01:00 by Atheros1 · 3 comments
Atheros1 commented 2015-03-06 23:10:13 +01:00 (Migrated from github.com)

When using a trustedpeer, these checks shouldn't be done because if there are more than 200K objects active in the network then we won't get all of them.

3384869299/src/class_receiveDataThread.py (L407)
3384869299/src/class_receiveDataThread.py (L432)

When using a trustedpeer, these checks shouldn't be done because if there are more than 200K objects active in the network then we won't get all of them. https://github.com/Bitmessage/PyBitmessage/blob/33848692995f172f55ef51a86f7bc1b50776cca7/src/class_receiveDataThread.py#L407 https://github.com/Bitmessage/PyBitmessage/blob/33848692995f172f55ef51a86f7bc1b50776cca7/src/class_receiveDataThread.py#L432
Atheros1 commented 2015-03-06 23:12:17 +01:00 (Migrated from github.com)

Thanks to BM-2cTWtwwQvhcTMnEgT1bhWDYrC6VpF9Jxve for reporting.

Thanks to BM-2cTWtwwQvhcTMnEgT1bhWDYrC6VpF9Jxve for reporting.
PeterSurda commented 2015-11-11 09:42:26 +01:00 (Migrated from github.com)

Makes sense and looks like I can do that.

Makes sense and looks like I can do that.
PeterSurda commented 2015-11-19 19:49:46 +01:00 (Migrated from github.com)

@Atheros1 If you want you can review it. I didn't test it extensively, I just check that trustedPeer is not broken.

@Atheros1 If you want you can review it. I didn't test it extensively, I just check that trustedPeer is not broken.
This repo is archived. You cannot comment on issues.
No Milestone
No project
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2024-12-11#786
No description provided.