Skip to content

Commit

Permalink
docs: make email address less prominent
Browse files Browse the repository at this point in the history
getting too many email requests for support with questions that are already covered in the docs. πŸ˜•
  • Loading branch information
snarfed committed Nov 16, 2024
1 parent 05b86df commit 9725099
Show file tree
Hide file tree
Showing 4 changed files with 7 additions and 17 deletions.
8 changes: 0 additions & 8 deletions common.py
Original file line number Diff line number Diff line change
Expand Up @@ -366,14 +366,6 @@ def create_task(queue, delay=None, **params):
return msg, 202


def email_me(msg):
assert False # not working, SMTP woes :(
if not DEBUG:
util.send_email(smtp_host=SMTP_HOST, smtp_port=SMTP_PORT,
from_='[email protected]', to='[email protected]',
subject=util.ellipsize(msg), body=msg)


def report_exception(**kwargs):
return report_error(msg=None, exception=True, **kwargs)

Expand Down
6 changes: 2 additions & 4 deletions templates/base.html
Original file line number Diff line number Diff line change
Expand Up @@ -47,8 +47,7 @@
<a href="/docs">Docs</a> &nbsp;
<a href="https://snarfed.org/?s=%22bridgy+fed%22">News</a> &nbsp;
<a href="https://github.com/snarfed/bridgy-fed">Code</a> &nbsp;
<a href="https://github.com/snarfed/bridgy-fed/issues">Issues</a> &nbsp;
<a href="mailto:[email protected]">Feedback</a>
<a href="https://github.com/snarfed/bridgy-fed/issues">Issues</a>
</p>
</div>

Expand All @@ -60,8 +59,7 @@
<a href="/docs">Docs</a> &nbsp;
<a href="https://snarfed.org/?s=%22bridgy+fed%22">News</a> &nbsp;
<a href="https://github.com/snarfed/bridgy-fed">Code</a> &nbsp;
<a href="https://github.com/snarfed/bridgy-fed/issues">Issues</a> &nbsp;
<a href="mailto:[email protected]">Feedback</a>
<a href="https://github.com/snarfed/bridgy-fed/issues">Issues</a>
</p>
</div>

Expand Down
8 changes: 4 additions & 4 deletions templates/docs.html
Original file line number Diff line number Diff line change
Expand Up @@ -242,7 +242,7 @@ <h3 id="about">About</h3>
<li id="opt-out" class="question">How do I opt out and remove my site or account?</li>
<li class="answer">
<p>If you're on the fediverse or Bluesky, and you've opted in but now want to opt out, block the Bridgy Fed bot user for the network you want to opt out of. For example, on the fediverse, block <code>@[email protected]</code>. On Bluesky, block <a href="https://bsky.app/profile/ap.brid.gy">@ap.brid.gy</a>.</p>
<p>If you're on the web, feel free to <a href="mailto:[email protected]">email me</a>, or you can put the text <code>#nobridge</code> in the <a href="#web-profile">profile on your home page</a> and then <a href="#update-profile">update your profile</a> on <a href="#user-page">your user page</a>.</p>
<p>If you're on the web, <a href="mailto:[email protected]">email us</a> from an address at your web site's domain to show that you own it, or you can put the text <code>#nobridge</code> in the <a href="#web-profile">profile on your home page</a> and then <a href="#update-profile">update your profile</a> on <a href="#user-page">your user page</a>.</p>
<p>Once you've done this, Bridgy Fed will deactivate your bridged profile in that network, and it will no longer bridge any of your posts or interactions there.</p>
<p>You can undo this later by un-blocking and re-following the bot user, but depending on the network, not everything will be perfectly restored. For example, when you disable bridging into the fediverse, the bridged fediverse account is deleted and all followers are disconnected. If you later re-enable it, fediverse users will have to search for your account by address manually to find and follow it again.</p>
</li>
Expand Down Expand Up @@ -947,7 +947,7 @@ <h3 id="background">Background</h3>
</p>
<p>Otherwise, you may use the service for any purpose you see fit. However, we may terminate or block your access for any reason, or no reason at all. (We've never done this, and we expect we never will. Just playing it safe.)
</p>
<p>Do you an administer an instance or other service that Bridgy Fed interacts with? If you have any concerns or questions, feel free to <a href="https://github.com/snarfed/bridgy-fed/issues">file an issue</a> or <a href="mailto:[email protected]">email me privately</a>!</p>
<p>Do you an administer an instance or other service that Bridgy Fed interacts with? If you have any concerns or questions, feel free to <a href="https://github.com/snarfed/bridgy-fed/issues">file an issue</a>!</p>
</li>


Expand All @@ -970,7 +970,7 @@ <h3 id="background">Background</h3>
</li>
</ul>
<p>These are principles, not a policy. When a user or post gets reported to me, I don't follow this letter by letter to determine what to do. The language here will evolve over time. However, I hope to live up to this <em>in spirit</em> for the long run.</p>
<p>Please reach out and let me know your thoughts! And feel free to report anything you see on Bridgy Fed that you think shouldn't be there. You can <a href="https://github.com/snarfed/bridgy-fed/issues">file an issue on GitHub</a>, <a href="mailto:[email protected]">email me privately</a>, or <a href="https://fed.brid.gy/web/snarfed.org">ping me on your social network of choice</a>.</p>
<p>Please reach out and let me know your thoughts! And feel free to report anything you see on Bridgy Fed that you think shouldn't be there. You can <a href="https://github.com/snarfed/bridgy-fed/issues">file an issue on GitHub</a> or <a href="https://fed.brid.gy/web/snarfed.org">ping me on your social network of choice</a>.</p>
</li>


Expand All @@ -982,7 +982,7 @@ <h3 id="background">Background</h3>

<li id="vulnerability" class="question">I found a security vulnerability!</li>
<li class="answer">
<p>Oof. Thank you for reporting it! Please <a href="https://github.com/snarfed/bridgy-fed/security/advisories">file an advisory on GitHub</a> or email details to <a href="mailto:[email protected]">[email protected]</a>. We may provide monetary awards for reports of significant vulnerabilities, eg reading or modifying users' private keys, <em>if</em> you follow these rules:</p>
<p>Oof. Thank you for reporting it! Please <a href="https://github.com/snarfed/bridgy-fed/security/advisories">file an advisory on GitHub</a>. We may provide monetary awards for reports of significant vulnerabilities, eg reading or modifying users' private keys, <em>if</em> you follow these rules:</p>
<ul>
<li>Vulnerabilities must be in the application itself, not unrelated services like email (eg SPF/DKIM/DMARC).</li>
<li>Out of scope: rate limiting, XSS/CSRF attacks (Bridgy Fed has no authenticated sessions or private data accessible to users).
Expand Down
2 changes: 1 addition & 1 deletion templates/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@
<!-- </div> -->

<div class="row big front-light">
<p>Bridgy Fed is a free, non-commercial, <a href="https://github.com/snarfed/bridgy-fed">open source</a> service. <a href="https://snarfed.org/2023-11-27_re-introducing-bridgy-fed">More background here.</a> <a href="https://github.com/snarfed/bridgy-fed/issues">Bug reports, feature requests</a>, and <a href="mailto:[email protected]">other feedback</a> are welcome!</a></p>
<p>Bridgy Fed is a free, non-commercial, <a href="https://github.com/snarfed/bridgy-fed">open source</a> service. <a href="https://snarfed.org/2023-11-27_re-introducing-bridgy-fed">More background here.</a> <a href="https://github.com/snarfed/bridgy-fed/issues">Bug reports, feature requests, and other feedback</a> are welcome!</a></p>
</div>

<div id="front-logo-bottom" class="row">
Expand Down

0 comments on commit 9725099

Please sign in to comment.