shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

285
active users

#endpoints

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://rubber.social/@dragonarchitect" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>dragonarchitect</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.social/@DeltaWye" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>DeltaWye</span></a></span> this also is the advantage of <a href="https://infosec.space/tags/TCPIP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TCPIP</span></a>: Only the <a href="https://infosec.space/tags/endpoints" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>endpoints</span></a> need to be able to reach each other: All the complicated <a href="https://infosec.space/tags/Routing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Routing</span></a> is transparent and thus changing routes don't result in lost connections.</p><ul><li>You can see this with <span class="h-card" translate="no"><a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>torproject</span></a></span> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Tor</span></a> traffic using <a href="https://infosec.space/tags/webtunnel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>webtunnel</span></a> <a href="https://infosec.space/tags/bridges" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bridges</span></a>: It smoothly shifts between <a href="https://infosec.space/tags/WiFi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WiFi</span></a> &amp; <a href="https://infosec.space/tags/WWAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WWAN</span></a> and back...</li></ul>
Teri Radichel<p>Troubleshooting <a href="https://infosec.exchange/tags/AWS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AWS</span></a> <a href="https://infosec.exchange/tags/VPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VPC</span></a> <a href="https://infosec.exchange/tags/Endpoints" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Endpoints</span></a><br>~~<br>ACM.318 When you cannot access AWS Services or your response time slows down after deploying VPC endpoints and how to fix it<br>~~<br>Not sure this is how it’s supposed to work. 🤔 But this fixes it.</p><p><a href="https://medium.com/cloud-security/troubleshooting-vpc-endpoints-abf4cf05f1ef" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">medium.com/cloud-security/trou</span><span class="invisible">bleshooting-vpc-endpoints-abf4cf05f1ef</span></a></p>