Lingolol

0 posts0 participants0 posts today

YunaIs Node.js the future of backend development, or just a beautifully wrapped grenade?Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.When I first used Node.js years ago, I remember: • Security concepts were… let’s say aspirational. • Licensing hell due to questionable npm dependencies. • Tests were flaky, with mocking turning into dark rituals. • Behavior of libraries changed weekly like socks, but more dangerous. • Internet required to run a “local” build. How comforting.Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when: • The backend is non-compiled. • Every endpoint is a potential open door. • The system needs Node + a fleet of dependencies + a container + prayer just to run.Compare that to a compiled, stateless binary that: • Runs in a scratch container. • Requires zero runtime dependencies. • Has encryption at rest, in transit, and ideally per-user. • Can be observed, scaled, audited, stateless and destroyed with precision.I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.So I wonder: Is this the future? Or am I just… old?Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?Tell me how you build secure, observable, compliant systems in Node.js. Genuinely curious. Mildly terrified and maybe old.<a href="https://hachyderm.io/tags/NodeJS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NodeJS</a> <a href="https://hachyderm.io/tags/BackendSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BackendSecurity</a> <a href="https://hachyderm.io/tags/SecureCoding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecureCoding</a> <a href="https://hachyderm.io/tags/PII" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PII</a> <a href="https://hachyderm.io/tags/Compliance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Compliance</a> <a href="https://hachyderm.io/tags/SoftwareArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareArchitecture</a> <a href="https://hachyderm.io/tags/ServerSideRendering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ServerSideRendering</a> <a href="https://hachyderm.io/tags/TypeScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TypeScript</a> <a href="https://hachyderm.io/tags/Java" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Java</a> <a href="https://hachyderm.io/tags/Kotlin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kotlin</a> <a href="https://hachyderm.io/tags/Golang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Golang</a> <a href="https://hachyderm.io/tags/Erlang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Erlang</a> <a href="https://hachyderm.io/tags/Ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ruby</a> <a href="https://hachyderm.io/tags/Scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scalability</a> <a href="https://hachyderm.io/tags/Observability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Observability</a> <a href="https://hachyderm.io/tags/DevSecOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevSecOps</a> <a href="https://hachyderm.io/tags/LegacyVsModern" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LegacyVsModern</a> <a href="https://hachyderm.io/tags/SecureByDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecureByDesign</a> <a href="https://hachyderm.io/tags/CompiledLanguages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CompiledLanguages</a> <a href="https://hachyderm.io/tags/CloudArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudArchitecture</a> <a href="https://hachyderm.io/tags/StatelessDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#StatelessDesign</a> <a href="https://hachyderm.io/tags/SecurityTheatre" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecurityTheatre</a> <a href="https://hachyderm.io/tags/TechSatire" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechSatire</a> <a href="https://hachyderm.io/tags/LinkedInTechRant" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinkedInTechRant</a>

Felix Palmen :freebsd: :c64:First change since <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swad</a> 0.2 will actually be a (huge?) improvement to my <a href="https://mastodon.bsd.cafe/tags/poser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poser</a> lib. So far, it was hardwired to use the good old <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#POSIX</a> <a href="https://mastodon.bsd.cafe/tags/select" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#select</a> call. This is perfectly fine for handling around up to 100 (or at least less than 1000, YMMV) clients.Some <a href="https://mastodon.bsd.cafe/tags/select" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#select</a> implementations offer defining the upper limit for checked file descriptors. Added support for that.POSIX also specifies <a href="https://mastodon.bsd.cafe/tags/poll" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poll</a>, which has very similar <a href="https://mastodon.bsd.cafe/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a> issues, but slightly different. Added support for this as well.And then, I went on to add support for the <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>-specific <a href="https://mastodon.bsd.cafe/tags/epoll" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#epoll</a> and <a href="https://mastodon.bsd.cafe/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSD</a>-specific <a href="https://mastodon.bsd.cafe/tags/kqueue" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kqueue</a> (<a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>, <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a>, <a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a>, ...) which are both designed to *solve* any scalability issues 🥳 A little thing that slightly annoyed me about kqueue was that there's no support for temporarily changing the signal mask, so I had to do the silly dance shown in the screenshot. OTOH, it offers changing event filters and getting events in a single call, which I might try to even further optimize ... 😎<a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a>

Abstract Technology GmbH🌐 At Abstract-Technology, we are constantly exploring innovative solutions to push the boundaries of online learning through the Open edX platform. 🚀 We are excited to share our latest technical deep dive: <a href="https://abstract-technology.de/running-open-edx-on-kubernetes-with-nixos" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://abstract-technology.de/running-open-edx-on-kubernetes-with-nixos</a> <a href="https://mastodon.social/tags/OpenedX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenedX</a> <a href="https://mastodon.social/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kubernetes</a> <a href="https://mastodon.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a> <a href="https://mastodon.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://mastodon.social/tags/Scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scalability</a> <a href="https://mastodon.social/tags/LMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LMS</a>

Coach Pāṇini ®<a href="https://mastodon.world/tags/Scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scalability</a> is a product of a rational and production oriented view of the world, tied to ideas of resource extraction, leverage, and production to get ”more”. <a href="https://www.linkedin.com/posts/fridgren_sorry-love-the-idea-but-it-doesnt-scale-activity-7302011239335927809-rLtx?utm_source=share&utm_medium=member_ios&rcm=ACoAAACmWtEBurVmJxUdnv5QtGB6hgFTyYJNROs" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.linkedin.com/posts/fridgren_sorry-love-the-idea-but-it-doesnt-scale-activity-7302011239335927809-rLtx?utm_source=share&utm_medium=member_ios&rcm=ACoAAACmWtEBurVmJxUdnv5QtGB6hgFTyYJNROs</a>

☮ ♥ ♬ 🧑‍💻Big question, Why ATProtocol from <a href="https://ioc.exchange/tags/BlueSkySocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BlueSkySocial</a> <a href="https://ioc.exchange/tags/PBC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PBC</a>’s mouth instead of Mastodon and ActivityPub?: “Why not use ActivityPub? <a href="https://ioc.exchange/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> is a federated social networking technology popularized by <a href="https://ioc.exchange/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a>.Account <a href="https://ioc.exchange/tags/portability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#portability</a> is a major reason why we chose to build a separate protocol. We consider portability to be crucial because it protects <a href="https://ioc.exchange/tags/users" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#users</a> from sudden bans, server shutdowns, and policy disagreements. Our <a href="https://ioc.exchange/tags/solution" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#solution</a> for portability requires both signed data repositories and <a href="https://ioc.exchange/tags/DIDs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DIDs</a>, neither of which are easy to retrofit into ActivityPub. The migration <a href="https://ioc.exchange/tags/tools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tools</a> for ActivityPub are comparatively limited; they require the original server to provide a redirect and cannot migrate the user's previous data.Another major reason is <a href="https://ioc.exchange/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a>. <a href="https://ioc.exchange/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> depends heavily on delivering messages between a wide network of small-to-medium sized nodes, which can cause individual <a href="https://ioc.exchange/tags/nodes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nodes</a> to be flooded with traffic and generally struggles to provide global views of <a href="https://ioc.exchange/tags/activity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#activity</a>.”Short version, WE CANT CONTROL YOU. <<a href="https://atproto.com/guides/faq" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://atproto.com/guides/faq</a>>

Serge Matveenko ⚠️ movedI've seen more people advocating for wider RSS adoption lately.I was a heavy RSS user back in the day, but honestly, it’s a standard that struggles to keep up with modern demands.In this short read, I break down why RSS’s pull model is inefficient and why push-based alternatives like ActivityPub are the future.Read more: <a href="https://dev.to/justlig/rss-a-great-standard-that-cant-keep-up-4ibp" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://dev.to/justlig/rss-a-great-standard-that-cant-keep-up-4ibp</a><a href="https://fosstodon.org/tags/RSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RSS</a> <a href="https://fosstodon.org/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> <a href="https://fosstodon.org/tags/WebEvolution" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebEvolution</a> <a href="https://fosstodon.org/tags/Scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scalability</a>

Dyne.org foundationThe problems in the European Digital Identity (EUDI)<a href="https://mastodon.social/@jaromil" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jaromil</a>'s independent feedback on the dangers of the current <a href="https://toot.community/tags/EUDI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUDI</a> implementation. What it should be, and the issues it has regarding Fairness, Privacy, Security, Scalability, Obsolescence and Methodology.<a href="https://toot.community/tags/Fairness" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fairness</a> <a href="https://toot.community/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> <a href="https://toot.community/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a href="https://toot.community/tags/Scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scalability</a> <a href="https://toot.community/tags/Obsolescence" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Obsolescence</a> <a href="https://toot.community/tags/Methodology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Methodology</a>.<a href="https://news.dyne.org/the-problems-of-european-digital-identity/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://news.dyne.org/the-problems-of-european-digital-identity/</a>

Koen Hufkens, PhDWhen I read about these things I always think about some of the writing of <a href="https://mamot.fr/@pluralistic" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pluralistic</a> on graceful failure modes. A product (system) is not defined by its success but by how good or poorly it fails. I've been teaching students that not considering (poor) failure modes is a huge liability.<a href="https://arstechnica.com/gadgets/2024/12/nightmare-zipcar-outage-is-a-warning-against-complete-app-dependency/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://arstechnica.com/gadgets/2024/12/nightmare-zipcar-outage-is-a-warning-against-complete-app-dependency/</a><a href="https://mastodon.social/tags/failure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#failure</a> <a href="https://mastodon.social/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a> <a href="https://mastodon.social/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devops</a> <a href="https://mastodon.social/tags/management" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#management</a> <a href="https://mastodon.social/tags/governance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#governance</a>

Tokyo Outsider (337ppm)And there it is. <a href="https://dustycloud.org/blog/how-decentralized-is-bluesky/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://dustycloud.org/blog/how-decentralized-is-bluesky/</a><a href="https://mas.to/tags/bluesky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bluesky</a> <a href="https://mas.to/tags/decentralization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decentralization</a> <a href="https://mas.to/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> <a href="https://mas.to/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a>

Tokyo Outsider (337ppm)All of this 👇 🚨 <a href="https://dustycloud.org/blog/how-decentralized-is-bluesky/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://dustycloud.org/blog/how-decentralized-is-bluesky/</a><a href="https://mas.to/tags/bluesky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bluesky</a> <a href="https://mas.to/tags/decentralization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decentralization</a> <a href="https://mas.to/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> <a href="https://mas.to/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a>

Tokyo Outsider (337ppm)This is a scam. It's a scam, and finally I understand what the Bluesky brief was. It was "People want decentralization and portability: How can we remain relevant and profitable in a world with decentralization and portability?"Twitter (as was) was going to be the relay. And the design ensured the network would be able to sell itself as "decentralized", but simultaneously would not function without the relay.<a href="https://mas.to/tags/bluesky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bluesky</a> <a href="https://mas.to/tags/decentralization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decentralization</a> <a href="https://mas.to/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> <a href="https://mas.to/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a>

Tokyo Outsider (337ppm)"Bluesky's architecture documentation does acknowledge this, to some degree"... Then I say, "wtf, Bluesky architecture documentation author?" Because if your architecture documentation acknowledges this you stop writing and rework your architecture. <a href="https://mas.to/tags/bluesky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bluesky</a> <a href="https://mas.to/tags/decentralization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decentralization</a> <a href="https://mas.to/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> <a href="https://mas.to/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a>

Tokyo Outsider (337ppm)(The point, in case you missed it 👇)<a href="https://dustycloud.org/blog/how-decentralized-is-bluesky/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://dustycloud.org/blog/how-decentralized-is-bluesky/</a><a href="https://mas.to/tags/bluesky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bluesky</a> <a href="https://mas.to/tags/decentralization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decentralization</a> <a href="https://mas.to/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> <a href="https://mas.to/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a>

Tokyo Outsider (337ppm)oh no 🫣<a href="https://dustycloud.org/blog/how-decentralized-is-bluesky/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://dustycloud.org/blog/how-decentralized-is-bluesky/</a><a href="https://mas.to/tags/bluesky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bluesky</a> <a href="https://mas.to/tags/decentralization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decentralization</a> <a href="https://mas.to/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> <a href="https://mas.to/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a>

Tokyo Outsider (337ppm)Oh. My. God.<a href="https://dustycloud.org/blog/how-decentralized-is-bluesky/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://dustycloud.org/blog/how-decentralized-is-bluesky/</a><a href="https://mas.to/tags/bluesky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bluesky</a> <a href="https://mas.to/tags/decentralization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decentralization</a> <a href="https://mas.to/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> <a href="https://mas.to/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a>

Eric Vitiello,laHow we reduced the cost of building Twitter at Twitter-scale by 100x – Blog <a href="https://social.pixels.pizza/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> <a href="https://social.pixels.pizza/tags/Scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scalability</a> <a href="https://blog.redplanetlabs.com/2023/08/15/how-we-reduced-the-cost-of-building-twitter-at-twitter-scale-by-100x/" rel="nofollow noopener noreferrer" target="_blank">https://blog.redplanetlabs.com/2023/08/15/how-we-reduced-the-cost-of-building-twitter-at-twitter-scale-by-100x/</a>

Nora_In_🇨🇦So I’m not savvy on tech stuff but it strikes me that this “no one can ever buy Mastodon” thing may be a bit premature. If newbies are not taught to be wary of big or highly-specialized instances, say, couldn’t the top 10 instances coming to represent 80%+ of Mastodon users, or 80% of news accounts, exercise federation power in ways that some of us now find unthinkable but…power, as they say, corrupts? <a href="https://mstdn.ca/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> <a href="https://mstdn.ca/tags/Scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scalability</a> <a href="https://mstdn.ca/tags/decentralized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decentralized</a>

sebWrote down some thoughts about <a href="https://sfba.social/tags/fedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedi</a>, regional instances, and <a href="https://sfba.social/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a>. Sorry for all the words, didn’t have the stamina to word-smith it all.<a href="https://hub.sfba.social/2022/12/16/regional-instances-federation-and-scalability/" rel="nofollow noopener noreferrer" target="_blank">https://hub.sfba.social/2022/12/16/regional-instances-federation-and-scalability/</a>

Recent searches

Search options

Administered by:

Server stats:

#scalability