Update orbit-db to 0.28.0

[EmiM]

No description provided.

[EmiM]

Note: #120 this may be helpful

[EmiM]

#152

[EmiM]

The issues that I encountered:

• I don't receive replication events: https://gitter.im/orbitdb/Lobby?at=619c2e9fc6149e534944d921
• Error : Agent is not a constructor while using 54.0.0 ipfs/js-ipfs#3938
• crypto is not defined (while running tests)

[EmiM]

^ The above issues have been resolved:

• Replication events didn't happen because nodes were not connecting (IPFS.create accepts PeerID's private key in init options now)
• IPFS devs fixed the Agent issue and released a new patch so I bumped IPFS js to 0.60.2 in waggle
• Added jest setup file which sets global crypto. This may be a workaround.

[EmiM]

I noticed a change in replication behavior.
This is what I see during test (1000 entries in log db):

• multiple replicate.progress events (as before)
• For localhost p2p network it's about 20 seconds, for tor network it's about 150 seconds
• one replicate event with big chunk of data
  https://github.com/ZbayApp/waggle/runs/4326485402?check_suite_focus=true

[EmiM]

Asked Orbit-db folks: https://gitter.im/orbitdb/Lobby?at=61a4d643cdb5c1081a3926d3

[EmiM]

• replicate event works as expected (the previous chunky behavior was a bug):

haad @haad:matrix.org [m] 16:07
hey, thanks for the pings. regarding the replicated event: indeed, this is now sent only when the db has been (fully) replicated. in fact, the previous behaviour wasn't intended (replicated events "chunked"). however, if I understand the need described above, you want to be able to "know when some progress of replication has been made" and the replicate.progress event will give you that (see https://github.com/orbitdb/orbit-db-store/blob/main/src/Store.js#L100 for the callback signature and params). it's emitted for each replicated db log entry. with that, you can eg. show a nice progress bar, or hook to it to show the replicated data to the user. note though that when replicate.progress is fired, the DB index hasn't been updated yet with the replicated data.

• Created an issue regarding replication times: Should we see the replication times improvement switching from orbitdb 0.26 to 0.28? orbitdb/orbitdb#938