Python port

[kubuxu]

Python port

[Kubuxu]

The schema right now is very simple, in future if updated version is created the first line of the key will be updated.

This also means that we plan supporting this version of a key for quite a while (at least I hope so).

[machawk1]

@kggp1995 I have not tested the use case you mentioned but can imagine it being applicable to my own scenarios (involving private sharing of archival collections), so may look further into it.

[hmeine]

Thanks for sharing!

[hmeine]

(I must admit, though, that I did not get the relation to the wayback machine.)

[Kubuxu]

@machawk1 I looked at what you sent when you sent it and it looked good. Thanks for sharing it here.

[machawk1]

@hmeine Thanks for the feedback. I can make that more clear in the docs. OpenWayback indexes WARCs to CDX then on client access, reads the index for the source and offset of the payload in a WARC. ipwb does something similar but with CDXJ and the WARC contents extracted, pushed to, and pulled from IPFS.

The appeal of the IPFS swarm implementation is for collaboratively and more securely sharing WARCs' contents among a set of peers with the key, among a few other approaches I am investigating.

@Kubuxu Thank you! I am hoping to integrate it a bit further and to keep the Python version as to close to parallel with the original Golang version.

[0zAND1z]

@machawk1 & team, did you have any success with bridging multiple swarms having different swarm key? Would love to have your input on that. Thx

[0zAND1z]

Thanks for the revert @machawk1 .

Please feel free to share your thoughts in this registered issue: #3

Your inputs would be helpful in the implementation.