If you are super smart maybe you could pull it off. Otherwise, it seems pretty difficult to implement it.
Basically a blockchain verification problem
If you are super smart maybe you could pull it off. Otherwise, it seems pretty difficult to implement it.
Basically a blockchain verification problem
isn't this just ipfs?
I don't think so, because IPFS is just more sort of a framework and platform to those kind of applications, something as Nostr or some types of S3 storages, or a CDN. What's necessary thus is all the business logic, the specialized nodes and clients, the metadata, identifiers and namespaces so that that application is not just a directory spread over IPFS (or in our case, Iroh, which is much better than the vanilla IPFS node, Kubo). Something also like in HTTPS you don't see a lot of loose hyperlinks, but rather applications that use HTTPS underneath as another layer.
i don't see why it has to be specialised. you could do this with mastodon today. just post every ipfs uri as a message.
uncensorable
I don't really see the point from a censorship standpoint. I mean, if a moderated community or instance is seeing posts being removed, whoever wants to post there is probably not going to have a good time there in the first place. Like, you probably want to be in a different community or instance that doesn't take issue with whatever the content is that's being posted.
EDIT: Oh, maybe I'm misunderstanding. You're trying to archive the Web and then publish activity about that to ActivityPub, rather than archive ActivityPub and create a Web interface?
Yeah, it's archiving the Web (and more, basically a digital time capsule) then publish that to AP so it's more accesible, and of course have a web and/or a native client where you can manage easily all of that (with a UX similar to the one in Wayback Machine).
Isn't this just a variant of IPFS?
Repost: I don't think so, because IPFS is just more sort of a framework and platform to those kind of applications, something as Nostr or some types of S3 storages, or a CDN. What's necessary thus is all the business logic, the specialized nodes and clients, the metadata, identifiers and namespaces so that that application is not just a directory spread over IPFS (or in our case, Iroh, which is much better than the vanilla IPFS node, Kubo). Something also like in HTTPS you don't see a lot of loose hyperlinks, but rather applications that use HTTPS underneath as another layer.
all 10 comments