Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add email accounts to assets, add comments #71

Merged
merged 2 commits into from
May 23, 2024

Conversation

VirginiaBalseiro
Copy link
Member

Adds list of existing emails and the groups that should have access. See: #47 (comment)

assets.md Outdated Show resolved Hide resolved
Copy link
Member

@csarven csarven left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎶 "Will the real Administrator please stand up?" 🎶

Thanks for doing this work.


Regarding @TallTed 's suggestions: https://github.com/solid/team/pull/71/files#r1513276361 , very minor opinion: I think linking to the email addresses makes it a bit easier for harvesters to pick them up (entailing unsolicited emails to those accounts, see e.g., https://csarven.ca/hiding-email-addresses ). Granted those email addresses are linked from elsewhere so they're already out there. Just minimising additional exposure FWIW. The email addresses only in code blocks serves its purpose here too.

@TallTed
Copy link
Contributor

TallTed commented Mar 11, 2024

Harvesters have plenty of ways to deal with such obfuscation, and spammers are the first to adopt technological solutions of any kind. Humans have to work harder to send email to addresses that aren't mailto: hrefs. But you do you.

Co-authored-by: Ted Thibodeau Jr <[email protected]>
@VirginiaBalseiro VirginiaBalseiro merged commit bf0f6e6 into main May 23, 2024
@VirginiaBalseiro VirginiaBalseiro deleted the update-team-assets-emails branch May 23, 2024 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants