It’s pretty easy with jenny to use GPG to sign your feed (just do it in your publish_command), but of course, there’s no verification. 🤔 Should this be on the TODO list? Is it overkill? Nobody’s using it at the moment …
@movq@www.uninformativ.de I’d like to take this a step further and define the notion of “private feeds” that are fully e2e encrypted and signed. I think using keys.pub could work nicely here.
@movq@www.uninformativ.de I wouldn’t necessarily think of it as “messaging” per se, but naturally it could be repurposed for that of course. @lyse@lyse.isobeef.org ask me on #yarn.social on IRC what the use-case for this was. THe primary and most useful use-case is for “private social media”. For example (true story); I was out with my family visiting the museum and we had a great time, took a few pics, etc. Naturally we wanted to share those moments with our extended family… What are your choices? Facebook, Twitter, TikTok, Instagram? Fuck no 🤣 All privacy eroding piles 💩
@lyse@lyse.isobeef.org I believe also that yarnd’s parser basically ignores the lines too.
@movq@www.uninformativ.de If there were something like verify_command, how could we signal to other feed consumers how to decrypt and/or verify a post? Also what about using TOFU here instead of a key sharing service?
@mckinley@twtxt.net Yeah I think your right on the money there with:
for people to get together online that know each other and meatspace
@mckinley@twtxt.net Hmm you do raise a good point re openness 🤔
@movq@www.uninformativ.de interesting proposition 🤔