@j12t @julian Yeah, this requires some thinking and depends on the goals from the issuers.The badges need to be explicitly accepted in BadgeFed, so even if you issue one to them, they still need to accept it, which solves the consent issue. I do think we can integrate with your existing management systems to automate most of the flow, and a checkbox during registration makes total sense.I've seen people simply share their badges on their socials, LinkedIn, Mastodon, personal websites, and that creates organic visibility for the event. It becomes social proof and generates a ripple effect.Beyond that, you could:- Display accepted badges on the event page (opt-in only, badgefed already have a public/private way to do this).- Encourage speakers to embed them on their homepages (badgefed provides embedded html/js codes) or their mastodon socials (e.g. https://verifiedby.maho.dev/recipient/aHR0cHM6Ly9oYWNoeWRlcm0uaW8vQG1hcGFjaGU).- Use them as part of a "returning attendee" or "community contributor" recognition over time (create special badges for those people).
