mirror of
https://github.com/astro/buzzrelay.git
synced 2024-05-18 17:28:06 +00:00
112 lines
3.8 KiB
HTML
112 lines
3.8 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en" xml:lang="en">
|
|
<head>
|
|
<title>#FediBuzz Relay</title>
|
|
<meta charset="utf-8">
|
|
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
|
|
<meta name="robots" content="index,follow">
|
|
<meta name="description" content="The buzzing ActivityPub relay service">
|
|
<meta name="keywords" content="activitypub relay fedibuzz">
|
|
<meta name="language" content="en">
|
|
<meta name="author" content="Astro">
|
|
<link rel="stylesheet" href="style.css">
|
|
</head>
|
|
<body>
|
|
<header>
|
|
<h1>#FediBuzz Relay</h1>
|
|
<p>The customizable ActivityPub relay service</p>
|
|
</header>
|
|
|
|
<section>
|
|
<p>
|
|
Mastodon and many other ActivityPub-compatible services live
|
|
and breathe decentralization. Yet it can get lonely on a small
|
|
instance. Mastoadmins can bring the global buzz of toots into
|
|
the <b>Federated Timeline</b> of their small server by
|
|
following <b>ActivityPub relays</b>.
|
|
</p>
|
|
<p>
|
|
With this service <a href="https://fedi.buzz/">#FediBuzz</a>
|
|
provides relay endpoints for you to customize.
|
|
</p>
|
|
<ol>
|
|
<li>In Mastodon: click <b>Preferences</b> in the navigation sidebar</li>
|
|
<li>Navigate to <b>Administration</b></li>
|
|
<li>Navigate to <b>Relays</b> <code>/admin/relays</code></li>
|
|
<li>Click the <b>Add new relay</b> button <code>/admin/relays/new</code></li>
|
|
<li>Generate a relay address below</li>
|
|
<li>Copy & paste into Mastodon's preferences</li>
|
|
<li>Hit the <b>Save and enable</b> button</li>
|
|
</ol>
|
|
</section>
|
|
|
|
<section class="boxes">
|
|
<noscript>
|
|
<h2>
|
|
Please enable JavaScript!
|
|
</h2>
|
|
</noscript>
|
|
<article>
|
|
<h2>Follow posts by #tag</h2>
|
|
<div>
|
|
<input id="tag" size="20" placeholder="tag">
|
|
</div>
|
|
<pre id="tag-url">
|
|
</pre>
|
|
</article>
|
|
<article>
|
|
<h2>Follow posts by instance</h2>
|
|
<div>
|
|
<input id="instance" size="20" placeholder="example.xyz">
|
|
</div>
|
|
<pre id="instance-url">
|
|
</pre>
|
|
</article>
|
|
</section>
|
|
|
|
<section class="faq">
|
|
<h2>Can I follow all my city's hashtags for all dates in the year?</h2>
|
|
<p>
|
|
Putting dates in hashtags is popular. We are aware, and our
|
|
solution is very simple: posts with hashtags that end in
|
|
digits are additionally delivered to all followers that follow
|
|
the hashtag without the trailing digits.
|
|
</p>
|
|
<p>
|
|
That means, if you follow <code>#dd</code> on this relay,
|
|
you'll also get <code>#dd1302</code>, <code>#dd1402</code>,
|
|
<code>#dd1502</code>, and many more!
|
|
</p>
|
|
|
|
<h2>Will this service get me undesirable content?</h2>
|
|
<p>
|
|
To steer free of the worst, #FediBuzz ignores anyone from
|
|
instances that appear in
|
|
the <a href="https://github.com/gardenfence/blocklist">Garden
|
|
Fence blocklist</a>, which we pull regularly. However, because
|
|
we relay links to content in real-time, this service will
|
|
never do any manual filtering itself.
|
|
</p>
|
|
|
|
<h2>Is it cool to follow a few thousand tags/instances to build my own firehose?</h2>
|
|
<p>
|
|
Please don't, it's inefficient. Take a look at #FediBuzz'
|
|
<a href="https://docs.joinmastodon.org/methods/streaming/#public">federated
|
|
timeline API</a> instead:
|
|
</p>
|
|
<pre>https://fedi.buzz/api/v1/streaming/public</pre>
|
|
</section>
|
|
|
|
<footer>
|
|
<p>
|
|
<a href="https://github.com/astro/buzzrelay">source</a>
|
|
•
|
|
by <a rel="me" href="https://c3d2.social/@astro">@astro­@c3d2.social</a>
|
|
</p>
|
|
</footer>
|
|
|
|
<script type="text/javascript" src="urlgen.js">
|
|
</script>
|
|
</body>
|
|
</html>
|