- cross-posted to:
- pulse_of_truth@infosec.pub
- cross-posted to:
- pulse_of_truth@infosec.pub
Wayback Machine back in read-only mode after DDoS, may need further maintenance.
Wayback Machine back in read-only mode after DDoS, may need further maintenance.
Could it be? Sure, I don’t see a technological reason why someone couldn’t build a system like that.
Are they now (federated, or blockchained)? No.
True.
I’m working on a decentralised sharing protocol, but it uses reciprocal sharing so you’d have to have large storage anyways.
Hoof, yeah. Collaboration tools always seem to come down to bandwidth, storage, or both.
You need to use something I guess :-) Any examples?
Honestly, despite not actually being federated, I’ve been using raw Git a lot recently. As opposed to ActivityPub, you can always download the current state lf the central repo and bring yourself up to current. I just wish it were easier to store binary data in it (e.g. sharing my MP3s between my laptop and phone)
Of course, that’s not a collaborative use-case. I have no intention of opening my files to the world. Just noting that ActivityPub has some pretty severe limitations (if my mbin server is offline, I wont get the updates I missed while it was down, ever. And if I can’t process messages in real-time, I miss those too).
Honestly, despite not actually being federated, I’ve been using raw Git a lot recently. As opposed to ActivityPub, you can always download the current state lf the central repo and bring yourself up to current. I just wish it were easier to store binary data in it (e.g. sharing my MP3s between my laptop and phone)
Of course, that’s not a collaborative use-case. I have no intention of opening my files to the world. Just noting that ActivityPub has some pretty severe limitations (if my mbin server is offline, I wont get the updates I missed while it was down, ever. And if I can’t process messages in real-time, I miss those too).