I'd like to see more use out of #IPFS since it's such a powerful platform for distributed content and database operations.
Relatedly, I would like to see more native embrace of cryptographic features like Web of trust and signing of content in these days of AI generation and questions over the trustworthiness of sources.
It might be interesting if the browsing process involved checking signing keys of content to see who has certified the content as genuine.
@Hyolobrika any advancement in that field would be very welcome to me, though personally I would prefer not to get complicated by involving other technologies like DNS, even DNSSEC secured.
I have similar complaints against ActivityPub :)
I think we could go pretty natively distributed for cryptographic signing, so we don't really need the hierarchical technologies anymore, though it's understandable why established interests and people simply not wanting to rock the boat would look using what we have now as a springboard.
In fact, it's slightly off topic, but with polls showing degradation in the public trust of institutions these days, relying on things like DNS and institutions using DNS, well it might not be the best time for that anyway.
@volkris @jensimmons I don’t like the hierarchical nature of DNS either. I would much prefer we use GNS (petname/web of trust based), but no one does.
The reason I suggested linking to DNS is so that people don’t have to set up their own “address books”. For instance, news outlets and bloggers etc can all sign things with their domains.
@Hyolobrika Yeah, it's certainly practical, work with the world we have not the one we wish we had 🙂
@volkris @jensimmons The second would be a good idea, but not how C2PA wants to do it (inbuilt set of trusted CAs). For instance, there could be a way to link content to any (preferably DNSSEC-secured) domain name
orand you could add the pubkeys of entities you trust to an “address book”.