p on Nostr: Hitler trannycided himself. Always remember that lads. Wignatia n3f_X ...
Hitler trannycided himself. Always remember that lads. (npub1p7f…2srj) Wignatia (npub1kd0…s4m4) n3f_X :neon_devilblob: :debian: (npub18k3…upyq)
> I recall mentioning writing a self-hosted AP server in Red (REBOL variant) would be almost trivial.
I recall that, yes. It seems plausible to me but I still haven't used the language (because closed compiler).
> But your approach is true P2P
Yes, indeed.
> with the content distributed IPFS.
IPFS is not technically part of the design. It works analogously to IPFS, but has its own protocol and block structure; I had some different design goals from IPFS so I have different constraints, and IPFS is a bit slow. Revolver can, however, use IPFS as an alternative storage backend (which allows for blocks to move through IPFS's network) and it can attempt to optimistically fetch from IPFS (because we're using the same hashing algorithm), so IPFS is available as a side-channel of sorts. (That part is already done, but I have it disabled on most of the nodes because of the performance problems.)
> I recall mentioning writing a self-hosted AP server in Red (REBOL variant) would be almost trivial.
I recall that, yes. It seems plausible to me but I still haven't used the language (because closed compiler).
> But your approach is true P2P
Yes, indeed.
> with the content distributed IPFS.
IPFS is not technically part of the design. It works analogously to IPFS, but has its own protocol and block structure; I had some different design goals from IPFS so I have different constraints, and IPFS is a bit slow. Revolver can, however, use IPFS as an alternative storage backend (which allows for blocks to move through IPFS's network) and it can attempt to optimistically fetch from IPFS (because we're using the same hashing algorithm), so IPFS is available as a side-channel of sorts. (That part is already done, but I have it disabled on most of the nodes because of the performance problems.)