List the highest priority outstanding issues

[bitnom]

If anyone could help list the most important/high priority outstanding issues, please.

Related: #1370

[amark]

there's lots of devux facing bugs that people face that are pretty easy to work around, but annoying obviously. I'd love help with these.

However the highest priority items has been scaling the storage engine by switching to Book (unfinished) which is getting integrated into the core of everything (replaces GUN's internal graph, etc.) such that AXE has a singular unified DHT traversal/look-ahead algorithm. This has gotten majorly delayed due to multiple attacks, lawsuits, etc. life situation I've had to deal with. To make myself more productive with coding again I'm trying distracted having Code from Phone built so I can work on Book without my laptop. Just yesterday I finally got Book rendering on my phone with Code from Phone, still lot more to do to get to an MVP editor and I'd love any help. Or probably better:

For anyone who can concentrate laptop coding time, helping fix lower hanging bugs (like what you just did with the reconnection sync) is deeply appreciated. Seems like Mobile / React / Typescript stuff constantly change all the time, so even just keeping docs & things updated there would help a bunch of people too. There's also a big PR that just landed in a temporary branch for SEA that needs a security review + many many many SEA features (auto ACL tables, etc.) to be added, but that stuff since its all security/cryptography definitely needs a lot more review.

There's a super obnoxious bug that if you gun.get('table').map().once(... (or .on?) something with say 1K items, supposedly (people have reported, and I've seen/confirmed it happening, tho exact replication isn't predictable) that sporadic items occasionally don't sync, I think probably because of the code that splits up the stream into smaller chunks & CPU schedules it probably has an off by 1 state mutation, hunting that down would be great even if just a PANIC test (see tests/panic/load.js for a tutorial) would be great.

Tho having an Issue of Issues just confuses things, so preferably we don't (or we move this into a wiki page), since this issue is itself not a bug, can we consider merging somewhere else & closing? I want to keep Issues as Issues, not questions or other things. Thanks!!

[wayjake]

Glad to hear you're still going at it, @amark. What's keeping you from getting off your phone again? Too addicted to Instagram? ;)