@pixelfed I’m not saying I will go ahead with this, I want your feedback before any decision is made!
I want to get this right, there is no rush, so please let me know your thoughts on this!
@pixelfed I’m not saying I will go ahead with this, I want your feedback before any decision is made!
I want to get this right, there is no rush, so please let me know your thoughts on this!
@raphael Just posted about this!
@dansup you can do this is in a privacy-preserving way, no?
- Instead of asking the user to upload their contacts, get the user own email/phone/pixelfed account handle.
- Upload a hash of the private contact information, paired with clean text pixelfed account info.
- Other people now are able to find each other by simply asking your service "do you know anyone with this hash?", and in case your service answers yes, then your app can say "yes, you should talk with so-and-so@pixelfed.
@raphael It would be client side matching yes, I worded this badly 😅
@dansup almost. What I am saying is that you don't even need to upload the contact list. You can do the matching in the device.
@Melpomene @pixelfed we could support allow-list discovery, where a user allows their account to be discovered by X (the hashed phone numbers)
@dansup@mastodon.social @pixelfed@mastodon.social it isn't a bad idea, it's just not am idea that I'd find particularly useful. I try not to mix real life and my fediverse life, so I'd not want my number out there to be searched. I'd also worry that it might open the door to bad actors using it to doxx folk.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.