Skip to content

Issues: primetype/poldercast

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8 Open 4 Closed
8 Open 4 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Document the implementation decisions differences from the paper
#18 opened Feb 7, 2020 by NicolasDP
@NicolasDP
Improve Cyclon implementations by favouring least recently used entries instead of random ones enhancement New feature or request
#17 opened Feb 7, 2020 by NicolasDP
@NicolasDP
PolderCast Layers Not Communicating
#16 opened Feb 6, 2020 by michaeljfazio
5
Poldercast Vicinity Layer Not Returning "Nearest" Neighbours enhancement New feature or request
#15 opened Feb 6, 2020 by michaeljfazio
16
Very Expensive Indirection in Node Lookups enhancement New feature or request
#14 opened Feb 5, 2020 by michaeljfazio
Improve Vicinity algorithm
#11 opened Jan 29, 2020 by NicolasDP
A workable way to retire old gossips throughout the network
#10 opened Jan 28, 2020 by mzabaluev
5
Configurable limit needed for number of nodes returned in a view
#6 opened Oct 18, 2019 by mzabaluev
ProTip! Add no:assignee to see everything that’s not assigned.