Hashtag

#Cloudflare

345 posts tagged with this hashtag.

A friend of mine, @siliconsjang, released SiliconBeest v1.0.0 today. It's a server built on Workers, D1, R2, and Queues, using Fedify.

I like the starting point: after watching fediverse servers go down together during Cloudflare outages, they thought, why not just run on Cloudflare directly?

They're aiming for something cheap enough that a small instance can stay on Cloudflare's free plan, and a somewhat bigger one can fit in the $5/month tier. It's still early; a lot is missing, and Mastodon/Misskey API compatibility is more of a long-term goal.

I'm glad to see Fedify put to use for something like this. Worth checking out.

The source code is on GitHub under AGPL 3.0.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅไบบ(์ง€์ธ)์ธ @siliconsjang ๋‹˜์ด ์˜ค๋Š˜ SiliconBeest v1.0.0์„ ๅ…ฌ้–‹(๊ณต๊ฐœ)ํ–ˆ์Šต๋‹ˆ๋‹ค. Fedify์™€ Cloudflare๋ฅผ ๅŸบ็›ค(๊ธฐ๋ฐ˜)์œผ๋กœ ๋งŒ๋“  ์†Œํ”„ํŠธ์›จ์–ด์ธ๋ฐ, Workers, D1, R2, Queues ๋“ฑ ์„œ๋ฒ„๋ฆฌ์Šค ์Šคํƒ ์œ„์—์„œ ๅ…จ้ƒจ(์ „๋ถ€) ๋Œ์•„๊ฐ‘๋‹ˆ๋‹ค.

็™ผๆƒณ(๋ฐœ์ƒ)์˜ ๅ‡บ็™ผ้ปž(์ถœ๋ฐœ์ )์ด ์žฌ๋ฐŒ์Šต๋‹ˆ๋‹ค. Cloudflare ้šœ็ค™(์žฅ์• ) ๋•Œ ่ฏๅˆๅฎ‡ๅฎ™(์—ฐํ•ฉ์šฐ์ฃผ) ์„œ๋ฒ„๋“ค์ด ๋ฉ๋‹ฌ์•„ ๋‹ค์šด๋˜๋Š” ๊ฑธ ๋ณด๊ณ , ใ€Œ๊ทธ๋Ÿผ ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋Œ๋ฆฌ๋ฉด ๋˜์ง€ ์•Š๋‚˜?」๋ผ๋Š” ์ƒ๊ฐ์—์„œ ๅง‹ไฝœ(์‹œ์ž‘)ํ–ˆ๋‹ค๊ณ  ํ•˜๋„ค์š”.

่ฒป็”จ(๋น„์šฉ) ้ข(๋ฉด)์—์„œ๋Š” ๅฐ่ฆๆจก(์†Œ๊ทœ๋ชจ) ์ธ์Šคํ„ด์Šค๋Š” Cloudflare ็„กๆ–™(๋ฌด๋ฃŒ) ํ”Œ๋žœ, ์กฐ๊ธˆ ๋” ํฐ ่ฆๆจก(๊ทœ๋ชจ)๋Š” ๆœˆ(์›”) $5 ํ”Œ๋žœ์œผ๋กœ ๅ ช็•ถ(๊ฐ๋‹น)ํ•  ์ˆ˜ ์žˆ๋„๋ก ํ•˜๋Š” ๊ฒŒ ็›ฎๆจ™(๋ชฉํ‘œ)๋ผ๊ณ  ํ•ฉ๋‹ˆ๋‹ค. ์•„์ง ๅˆๆœŸ(์ดˆ๊ธฐ) ๋ฒ„์ „์ด๋ผ ๆœชๅ…ท้กฏ(๋ฏธ๊ตฌํ˜„) ๆฉŸ่ƒฝ(๊ธฐ๋Šฅ)์ด ๋งŽ๊ณ , Mastodon ๋ฐ Misskey API ไบ’ๆ›(ํ˜ธํ™˜)์€ ้•ทๆœŸ(์žฅ๊ธฐ) ็›ฎๆจ™(๋ชฉํ‘œ)๋กœ ๋ณด๊ณ  ์žˆ๋‹ค๋„ค์š”.

Fedify๋ฅผ ์จ์ฃผ์‹œ๋Š” ๋ถ„์ด๋ผ ๋ฐ˜๊ฐ‘๊ธฐ๋„ ํ•˜๊ณ , ๆ‡‰ๆด(์‘์›)ํ•˜๊ณ  ์‹ถ์–ด ็ดนไป‹(์†Œ๊ฐœ)ํ•ฉ๋‹ˆ๋‹ค.

์†Œ์Šค ์ฝ”๋“œ๋Š” AGPL 3.0์œผ๋กœ GitHub์— ๊ณต๊ฐœ๋˜์–ด ์žˆ์Šต๋‹ˆ๋‹ค.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

usage reaches historic 50% across services, matching IPv4 โ€” increased usage eases pressure on the IPv4 address market as 'new' protocol designed in 1998 finally hits its stride
, meanwhile, shows that 40% of traffic is done in IPv6, an actually impressive figure if you consider it's measuring actual transferred packets rather than just counting addresses
tomshardware.com/networking/ip

tomshardware.com

IPv6 usage reaches historic 50% across Google services, matching IPv4 โ€” increased usage eases pressure on the IPv4 address market as 'new' protocol designed in 1998 finally hits its stride

Come on folks, the protocol is 28 years old now.

@michael@thms.uk

A friend of mine, @siliconsjang, released SiliconBeest v1.0.0 today. It's a server built on Workers, D1, R2, and Queues, using Fedify.

I like the starting point: after watching fediverse servers go down together during Cloudflare outages, they thought, why not just run on Cloudflare directly?

They're aiming for something cheap enough that a small instance can stay on Cloudflare's free plan, and a somewhat bigger one can fit in the $5/month tier. It's still early; a lot is missing, and Mastodon/Misskey API compatibility is more of a long-term goal.

I'm glad to see Fedify put to use for something like this. Worth checking out.

The source code is on GitHub under AGPL 3.0.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅไบบ(์ง€์ธ)์ธ @siliconsjang ๋‹˜์ด ์˜ค๋Š˜ SiliconBeest v1.0.0์„ ๅ…ฌ้–‹(๊ณต๊ฐœ)ํ–ˆ์Šต๋‹ˆ๋‹ค. Fedify์™€ Cloudflare๋ฅผ ๅŸบ็›ค(๊ธฐ๋ฐ˜)์œผ๋กœ ๋งŒ๋“  ์†Œํ”„ํŠธ์›จ์–ด์ธ๋ฐ, Workers, D1, R2, Queues ๋“ฑ ์„œ๋ฒ„๋ฆฌ์Šค ์Šคํƒ ์œ„์—์„œ ๅ…จ้ƒจ(์ „๋ถ€) ๋Œ์•„๊ฐ‘๋‹ˆ๋‹ค.

็™ผๆƒณ(๋ฐœ์ƒ)์˜ ๅ‡บ็™ผ้ปž(์ถœ๋ฐœ์ )์ด ์žฌ๋ฐŒ์Šต๋‹ˆ๋‹ค. Cloudflare ้šœ็ค™(์žฅ์• ) ๋•Œ ่ฏๅˆๅฎ‡ๅฎ™(์—ฐํ•ฉ์šฐ์ฃผ) ์„œ๋ฒ„๋“ค์ด ๋ฉ๋‹ฌ์•„ ๋‹ค์šด๋˜๋Š” ๊ฑธ ๋ณด๊ณ , ใ€Œ๊ทธ๋Ÿผ ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋Œ๋ฆฌ๋ฉด ๋˜์ง€ ์•Š๋‚˜?」๋ผ๋Š” ์ƒ๊ฐ์—์„œ ๅง‹ไฝœ(์‹œ์ž‘)ํ–ˆ๋‹ค๊ณ  ํ•˜๋„ค์š”.

่ฒป็”จ(๋น„์šฉ) ้ข(๋ฉด)์—์„œ๋Š” ๅฐ่ฆๆจก(์†Œ๊ทœ๋ชจ) ์ธ์Šคํ„ด์Šค๋Š” Cloudflare ็„กๆ–™(๋ฌด๋ฃŒ) ํ”Œ๋žœ, ์กฐ๊ธˆ ๋” ํฐ ่ฆๆจก(๊ทœ๋ชจ)๋Š” ๆœˆ(์›”) $5 ํ”Œ๋žœ์œผ๋กœ ๅ ช็•ถ(๊ฐ๋‹น)ํ•  ์ˆ˜ ์žˆ๋„๋ก ํ•˜๋Š” ๊ฒŒ ็›ฎๆจ™(๋ชฉํ‘œ)๋ผ๊ณ  ํ•ฉ๋‹ˆ๋‹ค. ์•„์ง ๅˆๆœŸ(์ดˆ๊ธฐ) ๋ฒ„์ „์ด๋ผ ๆœชๅ…ท้กฏ(๋ฏธ๊ตฌํ˜„) ๆฉŸ่ƒฝ(๊ธฐ๋Šฅ)์ด ๋งŽ๊ณ , Mastodon ๋ฐ Misskey API ไบ’ๆ›(ํ˜ธํ™˜)์€ ้•ทๆœŸ(์žฅ๊ธฐ) ็›ฎๆจ™(๋ชฉํ‘œ)๋กœ ๋ณด๊ณ  ์žˆ๋‹ค๋„ค์š”.

Fedify๋ฅผ ์จ์ฃผ์‹œ๋Š” ๋ถ„์ด๋ผ ๋ฐ˜๊ฐ‘๊ธฐ๋„ ํ•˜๊ณ , ๆ‡‰ๆด(์‘์›)ํ•˜๊ณ  ์‹ถ์–ด ็ดนไป‹(์†Œ๊ฐœ)ํ•ฉ๋‹ˆ๋‹ค.

์†Œ์Šค ์ฝ”๋“œ๋Š” AGPL 3.0์œผ๋กœ GitHub์— ๊ณต๊ฐœ๋˜์–ด ์žˆ์Šต๋‹ˆ๋‹ค.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅไบบ(์ง€์ธ)์ธ @siliconsjang ๋‹˜์ด ์˜ค๋Š˜ SiliconBeest v1.0.0์„ ๅ…ฌ้–‹(๊ณต๊ฐœ)ํ–ˆ์Šต๋‹ˆ๋‹ค. Fedify์™€ Cloudflare๋ฅผ ๅŸบ็›ค(๊ธฐ๋ฐ˜)์œผ๋กœ ๋งŒ๋“  ์†Œํ”„ํŠธ์›จ์–ด์ธ๋ฐ, Workers, D1, R2, Queues ๋“ฑ ์„œ๋ฒ„๋ฆฌ์Šค ์Šคํƒ ์œ„์—์„œ ๅ…จ้ƒจ(์ „๋ถ€) ๋Œ์•„๊ฐ‘๋‹ˆ๋‹ค.

็™ผๆƒณ(๋ฐœ์ƒ)์˜ ๅ‡บ็™ผ้ปž(์ถœ๋ฐœ์ )์ด ์žฌ๋ฐŒ์Šต๋‹ˆ๋‹ค. Cloudflare ้šœ็ค™(์žฅ์• ) ๋•Œ ่ฏๅˆๅฎ‡ๅฎ™(์—ฐํ•ฉ์šฐ์ฃผ) ์„œ๋ฒ„๋“ค์ด ๋ฉ๋‹ฌ์•„ ๋‹ค์šด๋˜๋Š” ๊ฑธ ๋ณด๊ณ , ใ€Œ๊ทธ๋Ÿผ ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋Œ๋ฆฌ๋ฉด ๋˜์ง€ ์•Š๋‚˜?」๋ผ๋Š” ์ƒ๊ฐ์—์„œ ๅง‹ไฝœ(์‹œ์ž‘)ํ–ˆ๋‹ค๊ณ  ํ•˜๋„ค์š”.

่ฒป็”จ(๋น„์šฉ) ้ข(๋ฉด)์—์„œ๋Š” ๅฐ่ฆๆจก(์†Œ๊ทœ๋ชจ) ์ธ์Šคํ„ด์Šค๋Š” Cloudflare ็„กๆ–™(๋ฌด๋ฃŒ) ํ”Œ๋žœ, ์กฐ๊ธˆ ๋” ํฐ ่ฆๆจก(๊ทœ๋ชจ)๋Š” ๆœˆ(์›”) $5 ํ”Œ๋žœ์œผ๋กœ ๅ ช็•ถ(๊ฐ๋‹น)ํ•  ์ˆ˜ ์žˆ๋„๋ก ํ•˜๋Š” ๊ฒŒ ็›ฎๆจ™(๋ชฉํ‘œ)๋ผ๊ณ  ํ•ฉ๋‹ˆ๋‹ค. ์•„์ง ๅˆๆœŸ(์ดˆ๊ธฐ) ๋ฒ„์ „์ด๋ผ ๆœชๅ…ท้กฏ(๋ฏธ๊ตฌํ˜„) ๆฉŸ่ƒฝ(๊ธฐ๋Šฅ)์ด ๋งŽ๊ณ , Mastodon ๋ฐ Misskey API ไบ’ๆ›(ํ˜ธํ™˜)์€ ้•ทๆœŸ(์žฅ๊ธฐ) ็›ฎๆจ™(๋ชฉํ‘œ)๋กœ ๋ณด๊ณ  ์žˆ๋‹ค๋„ค์š”.

Fedify๋ฅผ ์จ์ฃผ์‹œ๋Š” ๋ถ„์ด๋ผ ๋ฐ˜๊ฐ‘๊ธฐ๋„ ํ•˜๊ณ , ๆ‡‰ๆด(์‘์›)ํ•˜๊ณ  ์‹ถ์–ด ็ดนไป‹(์†Œ๊ฐœ)ํ•ฉ๋‹ˆ๋‹ค.

์†Œ์Šค ์ฝ”๋“œ๋Š” AGPL 3.0์œผ๋กœ GitHub์— ๊ณต๊ฐœ๋˜์–ด ์žˆ์Šต๋‹ˆ๋‹ค.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅไบบ(์ง€์ธ)์ธ @siliconsjang ๋‹˜์ด ์˜ค๋Š˜ SiliconBeest v1.0.0์„ ๅ…ฌ้–‹(๊ณต๊ฐœ)ํ–ˆ์Šต๋‹ˆ๋‹ค. Fedify์™€ Cloudflare๋ฅผ ๅŸบ็›ค(๊ธฐ๋ฐ˜)์œผ๋กœ ๋งŒ๋“  ์†Œํ”„ํŠธ์›จ์–ด์ธ๋ฐ, Workers, D1, R2, Queues ๋“ฑ ์„œ๋ฒ„๋ฆฌ์Šค ์Šคํƒ ์œ„์—์„œ ๅ…จ้ƒจ(์ „๋ถ€) ๋Œ์•„๊ฐ‘๋‹ˆ๋‹ค.

็™ผๆƒณ(๋ฐœ์ƒ)์˜ ๅ‡บ็™ผ้ปž(์ถœ๋ฐœ์ )์ด ์žฌ๋ฐŒ์Šต๋‹ˆ๋‹ค. Cloudflare ้šœ็ค™(์žฅ์• ) ๋•Œ ่ฏๅˆๅฎ‡ๅฎ™(์—ฐํ•ฉ์šฐ์ฃผ) ์„œ๋ฒ„๋“ค์ด ๋ฉ๋‹ฌ์•„ ๋‹ค์šด๋˜๋Š” ๊ฑธ ๋ณด๊ณ , ใ€Œ๊ทธ๋Ÿผ ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋Œ๋ฆฌ๋ฉด ๋˜์ง€ ์•Š๋‚˜?」๋ผ๋Š” ์ƒ๊ฐ์—์„œ ๅง‹ไฝœ(์‹œ์ž‘)ํ–ˆ๋‹ค๊ณ  ํ•˜๋„ค์š”.

่ฒป็”จ(๋น„์šฉ) ้ข(๋ฉด)์—์„œ๋Š” ๅฐ่ฆๆจก(์†Œ๊ทœ๋ชจ) ์ธ์Šคํ„ด์Šค๋Š” Cloudflare ็„กๆ–™(๋ฌด๋ฃŒ) ํ”Œ๋žœ, ์กฐ๊ธˆ ๋” ํฐ ่ฆๆจก(๊ทœ๋ชจ)๋Š” ๆœˆ(์›”) $5 ํ”Œ๋žœ์œผ๋กœ ๅ ช็•ถ(๊ฐ๋‹น)ํ•  ์ˆ˜ ์žˆ๋„๋ก ํ•˜๋Š” ๊ฒŒ ็›ฎๆจ™(๋ชฉํ‘œ)๋ผ๊ณ  ํ•ฉ๋‹ˆ๋‹ค. ์•„์ง ๅˆๆœŸ(์ดˆ๊ธฐ) ๋ฒ„์ „์ด๋ผ ๆœชๅ…ท้กฏ(๋ฏธ๊ตฌํ˜„) ๆฉŸ่ƒฝ(๊ธฐ๋Šฅ)์ด ๋งŽ๊ณ , Mastodon ๋ฐ Misskey API ไบ’ๆ›(ํ˜ธํ™˜)์€ ้•ทๆœŸ(์žฅ๊ธฐ) ็›ฎๆจ™(๋ชฉํ‘œ)๋กœ ๋ณด๊ณ  ์žˆ๋‹ค๋„ค์š”.

Fedify๋ฅผ ์จ์ฃผ์‹œ๋Š” ๋ถ„์ด๋ผ ๋ฐ˜๊ฐ‘๊ธฐ๋„ ํ•˜๊ณ , ๆ‡‰ๆด(์‘์›)ํ•˜๊ณ  ์‹ถ์–ด ็ดนไป‹(์†Œ๊ฐœ)ํ•ฉ๋‹ˆ๋‹ค.

์†Œ์Šค ์ฝ”๋“œ๋Š” AGPL 3.0์œผ๋กœ GitHub์— ๊ณต๊ฐœ๋˜์–ด ์žˆ์Šต๋‹ˆ๋‹ค.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅไบบ(์ง€์ธ)์ธ @siliconsjang ๋‹˜์ด ์˜ค๋Š˜ SiliconBeest v1.0.0์„ ๅ…ฌ้–‹(๊ณต๊ฐœ)ํ–ˆ์Šต๋‹ˆ๋‹ค. Fedify์™€ Cloudflare๋ฅผ ๅŸบ็›ค(๊ธฐ๋ฐ˜)์œผ๋กœ ๋งŒ๋“  ์†Œํ”„ํŠธ์›จ์–ด์ธ๋ฐ, Workers, D1, R2, Queues ๋“ฑ ์„œ๋ฒ„๋ฆฌ์Šค ์Šคํƒ ์œ„์—์„œ ๅ…จ้ƒจ(์ „๋ถ€) ๋Œ์•„๊ฐ‘๋‹ˆ๋‹ค.

็™ผๆƒณ(๋ฐœ์ƒ)์˜ ๅ‡บ็™ผ้ปž(์ถœ๋ฐœ์ )์ด ์žฌ๋ฐŒ์Šต๋‹ˆ๋‹ค. Cloudflare ้šœ็ค™(์žฅ์• ) ๋•Œ ่ฏๅˆๅฎ‡ๅฎ™(์—ฐํ•ฉ์šฐ์ฃผ) ์„œ๋ฒ„๋“ค์ด ๋ฉ๋‹ฌ์•„ ๋‹ค์šด๋˜๋Š” ๊ฑธ ๋ณด๊ณ , ใ€Œ๊ทธ๋Ÿผ ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋Œ๋ฆฌ๋ฉด ๋˜์ง€ ์•Š๋‚˜?」๋ผ๋Š” ์ƒ๊ฐ์—์„œ ๅง‹ไฝœ(์‹œ์ž‘)ํ–ˆ๋‹ค๊ณ  ํ•˜๋„ค์š”.

่ฒป็”จ(๋น„์šฉ) ้ข(๋ฉด)์—์„œ๋Š” ๅฐ่ฆๆจก(์†Œ๊ทœ๋ชจ) ์ธ์Šคํ„ด์Šค๋Š” Cloudflare ็„กๆ–™(๋ฌด๋ฃŒ) ํ”Œ๋žœ, ์กฐ๊ธˆ ๋” ํฐ ่ฆๆจก(๊ทœ๋ชจ)๋Š” ๆœˆ(์›”) $5 ํ”Œ๋žœ์œผ๋กœ ๅ ช็•ถ(๊ฐ๋‹น)ํ•  ์ˆ˜ ์žˆ๋„๋ก ํ•˜๋Š” ๊ฒŒ ็›ฎๆจ™(๋ชฉํ‘œ)๋ผ๊ณ  ํ•ฉ๋‹ˆ๋‹ค. ์•„์ง ๅˆๆœŸ(์ดˆ๊ธฐ) ๋ฒ„์ „์ด๋ผ ๆœชๅ…ท้กฏ(๋ฏธ๊ตฌํ˜„) ๆฉŸ่ƒฝ(๊ธฐ๋Šฅ)์ด ๋งŽ๊ณ , Mastodon ๋ฐ Misskey API ไบ’ๆ›(ํ˜ธํ™˜)์€ ้•ทๆœŸ(์žฅ๊ธฐ) ็›ฎๆจ™(๋ชฉํ‘œ)๋กœ ๋ณด๊ณ  ์žˆ๋‹ค๋„ค์š”.

Fedify๋ฅผ ์จ์ฃผ์‹œ๋Š” ๋ถ„์ด๋ผ ๋ฐ˜๊ฐ‘๊ธฐ๋„ ํ•˜๊ณ , ๆ‡‰ๆด(์‘์›)ํ•˜๊ณ  ์‹ถ์–ด ็ดนไป‹(์†Œ๊ฐœ)ํ•ฉ๋‹ˆ๋‹ค.

์†Œ์Šค ์ฝ”๋“œ๋Š” AGPL 3.0์œผ๋กœ GitHub์— ๊ณต๊ฐœ๋˜์–ด ์žˆ์Šต๋‹ˆ๋‹ค.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅใ‚Šๅˆใ„ใฎ @siliconsjang ใ•ใ‚“ใŒไปŠๆ—ฅใ€SiliconBeest v1.0.0 ใ‚’ๅ…ฌ้–‹ใ—ใพใ—ใŸใ€‚Cloudflare Workersใ€D1ใ€R2ใ€Queuesใ ใ‘ใงๅ‹•ใใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใ‚ตใƒผใƒใƒผใงใ€Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใพใ™ใ€‚

ๅ€‹ไบบ็š„ใซ้ข็™ฝใ„ใจๆ€ใฃใŸใฎใฏๅ‡บ็™บ็‚นใงใ€Cloudflare้šœๅฎณใฎใŸใณใซใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใฎใ‚ตใƒผใƒใƒผใŒใพใจใ‚ใฆ่ฝใกใ‚‹ใฎใ‚’่ฆ‹ใฆใ€ใ€Œใใ‚Œใชใ‚‰ใ„ใฃใCloudflareใฎไธŠใงๅ‹•ใ‹ใ›ใฐใ‚ˆใ„ใฎใงใฏใ€ใจๆ€ใฃใŸใฎใŒๅง‹ใพใ‚Šใ ใใ†ใงใ™ใ€‚

ๅฐ่ฆๆจกใชใ‚คใƒณใ‚นใ‚ฟใƒณใ‚นใชใ‚‰Cloudflareใฎ็„กๆ–™ใƒ—ใƒฉใƒณใงใ€ๅฐ‘ใ—ๅคงใใใชใฃใฆใ‚‚ๆœˆ5ใƒ‰ใƒซใใ‚‰ใ„ใง้‹ๅ–ถใงใใ‚‹ใ“ใจใ‚’็›ฎๆŒ‡ใ—ใฆใ„ใ‚‹ใจใฎใ“ใจใ€‚ใพใ ๅˆๆœŸใƒใƒผใ‚ธใƒงใƒณใชใฎใงๆœชๅฎŸ่ฃ…ใฎ้ƒจๅˆ†ใ‚‚ๅคšใใ€Mastodonใ‚„Misskey APIใจใฎไบ’ๆ›ๆ€งใฏๆœชใ ๅ…ˆใฎ็›ฎๆจ™ใฟใŸใ„ใงใ™ใ€‚

Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใ‚‹ใฎใ‚‚ใ‚ใฃใฆใ€ๅ€‹ไบบ็š„ใซๅฌ‰ใ—ใ„ใงใ™ใ€‚ๆฐ—ใซใชใฃใŸใฎใงๅ…ฑๆœ‰ใ—ใพใ™ใ€‚

ใ‚ฝใƒผใ‚นใ‚ณใƒผใƒ‰ใฏAGPL 3.0ใงGitHubใงๅ…ฌ้–‹ใ•ใ‚Œใฆใ„ใพใ™ใ€‚

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅใ‚Šๅˆใ„ใฎ @siliconsjang ใ•ใ‚“ใŒไปŠๆ—ฅใ€SiliconBeest v1.0.0 ใ‚’ๅ…ฌ้–‹ใ—ใพใ—ใŸใ€‚Cloudflare Workersใ€D1ใ€R2ใ€Queuesใ ใ‘ใงๅ‹•ใใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใ‚ตใƒผใƒใƒผใงใ€Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใพใ™ใ€‚

ๅ€‹ไบบ็š„ใซ้ข็™ฝใ„ใจๆ€ใฃใŸใฎใฏๅ‡บ็™บ็‚นใงใ€Cloudflare้šœๅฎณใฎใŸใณใซใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใฎใ‚ตใƒผใƒใƒผใŒใพใจใ‚ใฆ่ฝใกใ‚‹ใฎใ‚’่ฆ‹ใฆใ€ใ€Œใใ‚Œใชใ‚‰ใ„ใฃใCloudflareใฎไธŠใงๅ‹•ใ‹ใ›ใฐใ‚ˆใ„ใฎใงใฏใ€ใจๆ€ใฃใŸใฎใŒๅง‹ใพใ‚Šใ ใใ†ใงใ™ใ€‚

ๅฐ่ฆๆจกใชใ‚คใƒณใ‚นใ‚ฟใƒณใ‚นใชใ‚‰Cloudflareใฎ็„กๆ–™ใƒ—ใƒฉใƒณใงใ€ๅฐ‘ใ—ๅคงใใใชใฃใฆใ‚‚ๆœˆ5ใƒ‰ใƒซใใ‚‰ใ„ใง้‹ๅ–ถใงใใ‚‹ใ“ใจใ‚’็›ฎๆŒ‡ใ—ใฆใ„ใ‚‹ใจใฎใ“ใจใ€‚ใพใ ๅˆๆœŸใƒใƒผใ‚ธใƒงใƒณใชใฎใงๆœชๅฎŸ่ฃ…ใฎ้ƒจๅˆ†ใ‚‚ๅคšใใ€Mastodonใ‚„Misskey APIใจใฎไบ’ๆ›ๆ€งใฏๆœชใ ๅ…ˆใฎ็›ฎๆจ™ใฟใŸใ„ใงใ™ใ€‚

Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใ‚‹ใฎใ‚‚ใ‚ใฃใฆใ€ๅ€‹ไบบ็š„ใซๅฌ‰ใ—ใ„ใงใ™ใ€‚ๆฐ—ใซใชใฃใŸใฎใงๅ…ฑๆœ‰ใ—ใพใ™ใ€‚

ใ‚ฝใƒผใ‚นใ‚ณใƒผใƒ‰ใฏAGPL 3.0ใงGitHubใงๅ…ฌ้–‹ใ•ใ‚Œใฆใ„ใพใ™ใ€‚

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅไบบ(์ง€์ธ)์ธ @siliconsjang ๋‹˜์ด ์˜ค๋Š˜ SiliconBeest v1.0.0์„ ๅ…ฌ้–‹(๊ณต๊ฐœ)ํ–ˆ์Šต๋‹ˆ๋‹ค. Fedify์™€ Cloudflare๋ฅผ ๅŸบ็›ค(๊ธฐ๋ฐ˜)์œผ๋กœ ๋งŒ๋“  ์†Œํ”„ํŠธ์›จ์–ด์ธ๋ฐ, Workers, D1, R2, Queues ๋“ฑ ์„œ๋ฒ„๋ฆฌ์Šค ์Šคํƒ ์œ„์—์„œ ๅ…จ้ƒจ(์ „๋ถ€) ๋Œ์•„๊ฐ‘๋‹ˆ๋‹ค.

็™ผๆƒณ(๋ฐœ์ƒ)์˜ ๅ‡บ็™ผ้ปž(์ถœ๋ฐœ์ )์ด ์žฌ๋ฐŒ์Šต๋‹ˆ๋‹ค. Cloudflare ้šœ็ค™(์žฅ์• ) ๋•Œ ่ฏๅˆๅฎ‡ๅฎ™(์—ฐํ•ฉ์šฐ์ฃผ) ์„œ๋ฒ„๋“ค์ด ๋ฉ๋‹ฌ์•„ ๋‹ค์šด๋˜๋Š” ๊ฑธ ๋ณด๊ณ , ใ€Œ๊ทธ๋Ÿผ ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋Œ๋ฆฌ๋ฉด ๋˜์ง€ ์•Š๋‚˜?」๋ผ๋Š” ์ƒ๊ฐ์—์„œ ๅง‹ไฝœ(์‹œ์ž‘)ํ–ˆ๋‹ค๊ณ  ํ•˜๋„ค์š”.

่ฒป็”จ(๋น„์šฉ) ้ข(๋ฉด)์—์„œ๋Š” ๅฐ่ฆๆจก(์†Œ๊ทœ๋ชจ) ์ธ์Šคํ„ด์Šค๋Š” Cloudflare ็„กๆ–™(๋ฌด๋ฃŒ) ํ”Œ๋žœ, ์กฐ๊ธˆ ๋” ํฐ ่ฆๆจก(๊ทœ๋ชจ)๋Š” ๆœˆ(์›”) $5 ํ”Œ๋žœ์œผ๋กœ ๅ ช็•ถ(๊ฐ๋‹น)ํ•  ์ˆ˜ ์žˆ๋„๋ก ํ•˜๋Š” ๊ฒŒ ็›ฎๆจ™(๋ชฉํ‘œ)๋ผ๊ณ  ํ•ฉ๋‹ˆ๋‹ค. ์•„์ง ๅˆๆœŸ(์ดˆ๊ธฐ) ๋ฒ„์ „์ด๋ผ ๆœชๅ…ท้กฏ(๋ฏธ๊ตฌํ˜„) ๆฉŸ่ƒฝ(๊ธฐ๋Šฅ)์ด ๋งŽ๊ณ , Mastodon ๋ฐ Misskey API ไบ’ๆ›(ํ˜ธํ™˜)์€ ้•ทๆœŸ(์žฅ๊ธฐ) ็›ฎๆจ™(๋ชฉํ‘œ)๋กœ ๋ณด๊ณ  ์žˆ๋‹ค๋„ค์š”.

Fedify๋ฅผ ์จ์ฃผ์‹œ๋Š” ๋ถ„์ด๋ผ ๋ฐ˜๊ฐ‘๊ธฐ๋„ ํ•˜๊ณ , ๆ‡‰ๆด(์‘์›)ํ•˜๊ณ  ์‹ถ์–ด ็ดนไป‹(์†Œ๊ฐœ)ํ•ฉ๋‹ˆ๋‹ค.

์†Œ์Šค ์ฝ”๋“œ๋Š” AGPL 3.0์œผ๋กœ GitHub์— ๊ณต๊ฐœ๋˜์–ด ์žˆ์Šต๋‹ˆ๋‹ค.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅใ‚Šๅˆใ„ใฎ @siliconsjang ใ•ใ‚“ใŒไปŠๆ—ฅใ€SiliconBeest v1.0.0 ใ‚’ๅ…ฌ้–‹ใ—ใพใ—ใŸใ€‚Cloudflare Workersใ€D1ใ€R2ใ€Queuesใ ใ‘ใงๅ‹•ใใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใ‚ตใƒผใƒใƒผใงใ€Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใพใ™ใ€‚

ๅ€‹ไบบ็š„ใซ้ข็™ฝใ„ใจๆ€ใฃใŸใฎใฏๅ‡บ็™บ็‚นใงใ€Cloudflare้šœๅฎณใฎใŸใณใซใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใฎใ‚ตใƒผใƒใƒผใŒใพใจใ‚ใฆ่ฝใกใ‚‹ใฎใ‚’่ฆ‹ใฆใ€ใ€Œใใ‚Œใชใ‚‰ใ„ใฃใCloudflareใฎไธŠใงๅ‹•ใ‹ใ›ใฐใ‚ˆใ„ใฎใงใฏใ€ใจๆ€ใฃใŸใฎใŒๅง‹ใพใ‚Šใ ใใ†ใงใ™ใ€‚

ๅฐ่ฆๆจกใชใ‚คใƒณใ‚นใ‚ฟใƒณใ‚นใชใ‚‰Cloudflareใฎ็„กๆ–™ใƒ—ใƒฉใƒณใงใ€ๅฐ‘ใ—ๅคงใใใชใฃใฆใ‚‚ๆœˆ5ใƒ‰ใƒซใใ‚‰ใ„ใง้‹ๅ–ถใงใใ‚‹ใ“ใจใ‚’็›ฎๆŒ‡ใ—ใฆใ„ใ‚‹ใจใฎใ“ใจใ€‚ใพใ ๅˆๆœŸใƒใƒผใ‚ธใƒงใƒณใชใฎใงๆœชๅฎŸ่ฃ…ใฎ้ƒจๅˆ†ใ‚‚ๅคšใใ€Mastodonใ‚„Misskey APIใจใฎไบ’ๆ›ๆ€งใฏๆœชใ ๅ…ˆใฎ็›ฎๆจ™ใฟใŸใ„ใงใ™ใ€‚

Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใ‚‹ใฎใ‚‚ใ‚ใฃใฆใ€ๅ€‹ไบบ็š„ใซๅฌ‰ใ—ใ„ใงใ™ใ€‚ๆฐ—ใซใชใฃใŸใฎใงๅ…ฑๆœ‰ใ—ใพใ™ใ€‚

ใ‚ฝใƒผใ‚นใ‚ณใƒผใƒ‰ใฏAGPL 3.0ใงGitHubใงๅ…ฌ้–‹ใ•ใ‚Œใฆใ„ใพใ™ใ€‚

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

A friend of mine, @siliconsjang, released SiliconBeest v1.0.0 today. It's a server built on Workers, D1, R2, and Queues, using Fedify.

I like the starting point: after watching fediverse servers go down together during Cloudflare outages, they thought, why not just run on Cloudflare directly?

They're aiming for something cheap enough that a small instance can stay on Cloudflare's free plan, and a somewhat bigger one can fit in the $5/month tier. It's still early; a lot is missing, and Mastodon/Misskey API compatibility is more of a long-term goal.

I'm glad to see Fedify put to use for something like this. Worth checking out.

The source code is on GitHub under AGPL 3.0.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅใ‚Šๅˆใ„ใฎ @siliconsjang ใ•ใ‚“ใŒไปŠๆ—ฅใ€SiliconBeest v1.0.0 ใ‚’ๅ…ฌ้–‹ใ—ใพใ—ใŸใ€‚Cloudflare Workersใ€D1ใ€R2ใ€Queuesใ ใ‘ใงๅ‹•ใใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใ‚ตใƒผใƒใƒผใงใ€Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใพใ™ใ€‚

ๅ€‹ไบบ็š„ใซ้ข็™ฝใ„ใจๆ€ใฃใŸใฎใฏๅ‡บ็™บ็‚นใงใ€Cloudflare้šœๅฎณใฎใŸใณใซใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใฎใ‚ตใƒผใƒใƒผใŒใพใจใ‚ใฆ่ฝใกใ‚‹ใฎใ‚’่ฆ‹ใฆใ€ใ€Œใใ‚Œใชใ‚‰ใ„ใฃใCloudflareใฎไธŠใงๅ‹•ใ‹ใ›ใฐใ‚ˆใ„ใฎใงใฏใ€ใจๆ€ใฃใŸใฎใŒๅง‹ใพใ‚Šใ ใใ†ใงใ™ใ€‚

ๅฐ่ฆๆจกใชใ‚คใƒณใ‚นใ‚ฟใƒณใ‚นใชใ‚‰Cloudflareใฎ็„กๆ–™ใƒ—ใƒฉใƒณใงใ€ๅฐ‘ใ—ๅคงใใใชใฃใฆใ‚‚ๆœˆ5ใƒ‰ใƒซใใ‚‰ใ„ใง้‹ๅ–ถใงใใ‚‹ใ“ใจใ‚’็›ฎๆŒ‡ใ—ใฆใ„ใ‚‹ใจใฎใ“ใจใ€‚ใพใ ๅˆๆœŸใƒใƒผใ‚ธใƒงใƒณใชใฎใงๆœชๅฎŸ่ฃ…ใฎ้ƒจๅˆ†ใ‚‚ๅคšใใ€Mastodonใ‚„Misskey APIใจใฎไบ’ๆ›ๆ€งใฏๆœชใ ๅ…ˆใฎ็›ฎๆจ™ใฟใŸใ„ใงใ™ใ€‚

Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใ‚‹ใฎใ‚‚ใ‚ใฃใฆใ€ๅ€‹ไบบ็š„ใซๅฌ‰ใ—ใ„ใงใ™ใ€‚ๆฐ—ใซใชใฃใŸใฎใงๅ…ฑๆœ‰ใ—ใพใ™ใ€‚

ใ‚ฝใƒผใ‚นใ‚ณใƒผใƒ‰ใฏAGPL 3.0ใงGitHubใงๅ…ฌ้–‹ใ•ใ‚Œใฆใ„ใพใ™ใ€‚

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

A friend of mine, @siliconsjang, released SiliconBeest v1.0.0 today. It's a server built on Workers, D1, R2, and Queues, using Fedify.

I like the starting point: after watching fediverse servers go down together during Cloudflare outages, they thought, why not just run on Cloudflare directly?

They're aiming for something cheap enough that a small instance can stay on Cloudflare's free plan, and a somewhat bigger one can fit in the $5/month tier. It's still early; a lot is missing, and Mastodon/Misskey API compatibility is more of a long-term goal.

I'm glad to see Fedify put to use for something like this. Worth checking out.

The source code is on GitHub under AGPL 3.0.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

A friend of mine, @siliconsjang, released SiliconBeest v1.0.0 today. It's a server built on Workers, D1, R2, and Queues, using Fedify.

I like the starting point: after watching fediverse servers go down together during Cloudflare outages, they thought, why not just run on Cloudflare directly?

They're aiming for something cheap enough that a small instance can stay on Cloudflare's free plan, and a somewhat bigger one can fit in the $5/month tier. It's still early; a lot is missing, and Mastodon/Misskey API compatibility is more of a long-term goal.

I'm glad to see Fedify put to use for something like this. Worth checking out.

The source code is on GitHub under AGPL 3.0.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

A friend of mine, @siliconsjang, released SiliconBeest v1.0.0 today. It's a server built on Workers, D1, R2, and Queues, using Fedify.

I like the starting point: after watching fediverse servers go down together during Cloudflare outages, they thought, why not just run on Cloudflare directly?

They're aiming for something cheap enough that a small instance can stay on Cloudflare's free plan, and a somewhat bigger one can fit in the $5/month tier. It's still early; a lot is missing, and Mastodon/Misskey API compatibility is more of a long-term goal.

I'm glad to see Fedify put to use for something like this. Worth checking out.

The source code is on GitHub under AGPL 3.0.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅใ‚Šๅˆใ„ใฎ @siliconsjang ใ•ใ‚“ใŒไปŠๆ—ฅใ€SiliconBeest v1.0.0 ใ‚’ๅ…ฌ้–‹ใ—ใพใ—ใŸใ€‚Cloudflare Workersใ€D1ใ€R2ใ€Queuesใ ใ‘ใงๅ‹•ใใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใ‚ตใƒผใƒใƒผใงใ€Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใพใ™ใ€‚

ๅ€‹ไบบ็š„ใซ้ข็™ฝใ„ใจๆ€ใฃใŸใฎใฏๅ‡บ็™บ็‚นใงใ€Cloudflare้šœๅฎณใฎใŸใณใซใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใฎใ‚ตใƒผใƒใƒผใŒใพใจใ‚ใฆ่ฝใกใ‚‹ใฎใ‚’่ฆ‹ใฆใ€ใ€Œใใ‚Œใชใ‚‰ใ„ใฃใCloudflareใฎไธŠใงๅ‹•ใ‹ใ›ใฐใ‚ˆใ„ใฎใงใฏใ€ใจๆ€ใฃใŸใฎใŒๅง‹ใพใ‚Šใ ใใ†ใงใ™ใ€‚

ๅฐ่ฆๆจกใชใ‚คใƒณใ‚นใ‚ฟใƒณใ‚นใชใ‚‰Cloudflareใฎ็„กๆ–™ใƒ—ใƒฉใƒณใงใ€ๅฐ‘ใ—ๅคงใใใชใฃใฆใ‚‚ๆœˆ5ใƒ‰ใƒซใใ‚‰ใ„ใง้‹ๅ–ถใงใใ‚‹ใ“ใจใ‚’็›ฎๆŒ‡ใ—ใฆใ„ใ‚‹ใจใฎใ“ใจใ€‚ใพใ ๅˆๆœŸใƒใƒผใ‚ธใƒงใƒณใชใฎใงๆœชๅฎŸ่ฃ…ใฎ้ƒจๅˆ†ใ‚‚ๅคšใใ€Mastodonใ‚„Misskey APIใจใฎไบ’ๆ›ๆ€งใฏๆœชใ ๅ…ˆใฎ็›ฎๆจ™ใฟใŸใ„ใงใ™ใ€‚

Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใ‚‹ใฎใ‚‚ใ‚ใฃใฆใ€ๅ€‹ไบบ็š„ใซๅฌ‰ใ—ใ„ใงใ™ใ€‚ๆฐ—ใซใชใฃใŸใฎใงๅ…ฑๆœ‰ใ—ใพใ™ใ€‚

ใ‚ฝใƒผใ‚นใ‚ณใƒผใƒ‰ใฏAGPL 3.0ใงGitHubใงๅ…ฌ้–‹ใ•ใ‚Œใฆใ„ใพใ™ใ€‚

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅใ‚Šๅˆใ„ใฎ @siliconsjang ใ•ใ‚“ใŒไปŠๆ—ฅใ€SiliconBeest v1.0.0 ใ‚’ๅ…ฌ้–‹ใ—ใพใ—ใŸใ€‚Cloudflare Workersใ€D1ใ€R2ใ€Queuesใ ใ‘ใงๅ‹•ใใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใ‚ตใƒผใƒใƒผใงใ€Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใพใ™ใ€‚

ๅ€‹ไบบ็š„ใซ้ข็™ฝใ„ใจๆ€ใฃใŸใฎใฏๅ‡บ็™บ็‚นใงใ€Cloudflare้šœๅฎณใฎใŸใณใซใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใฎใ‚ตใƒผใƒใƒผใŒใพใจใ‚ใฆ่ฝใกใ‚‹ใฎใ‚’่ฆ‹ใฆใ€ใ€Œใใ‚Œใชใ‚‰ใ„ใฃใCloudflareใฎไธŠใงๅ‹•ใ‹ใ›ใฐใ‚ˆใ„ใฎใงใฏใ€ใจๆ€ใฃใŸใฎใŒๅง‹ใพใ‚Šใ ใใ†ใงใ™ใ€‚

ๅฐ่ฆๆจกใชใ‚คใƒณใ‚นใ‚ฟใƒณใ‚นใชใ‚‰Cloudflareใฎ็„กๆ–™ใƒ—ใƒฉใƒณใงใ€ๅฐ‘ใ—ๅคงใใใชใฃใฆใ‚‚ๆœˆ5ใƒ‰ใƒซใใ‚‰ใ„ใง้‹ๅ–ถใงใใ‚‹ใ“ใจใ‚’็›ฎๆŒ‡ใ—ใฆใ„ใ‚‹ใจใฎใ“ใจใ€‚ใพใ ๅˆๆœŸใƒใƒผใ‚ธใƒงใƒณใชใฎใงๆœชๅฎŸ่ฃ…ใฎ้ƒจๅˆ†ใ‚‚ๅคšใใ€Mastodonใ‚„Misskey APIใจใฎไบ’ๆ›ๆ€งใฏๆœชใ ๅ…ˆใฎ็›ฎๆจ™ใฟใŸใ„ใงใ™ใ€‚

Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใ‚‹ใฎใ‚‚ใ‚ใฃใฆใ€ๅ€‹ไบบ็š„ใซๅฌ‰ใ—ใ„ใงใ™ใ€‚ๆฐ—ใซใชใฃใŸใฎใงๅ…ฑๆœ‰ใ—ใพใ™ใ€‚

ใ‚ฝใƒผใ‚นใ‚ณใƒผใƒ‰ใฏAGPL 3.0ใงGitHubใงๅ…ฌ้–‹ใ•ใ‚Œใฆใ„ใพใ™ใ€‚

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅใ‚Šๅˆใ„ใฎ @siliconsjang ใ•ใ‚“ใŒไปŠๆ—ฅใ€SiliconBeest v1.0.0 ใ‚’ๅ…ฌ้–‹ใ—ใพใ—ใŸใ€‚Cloudflare Workersใ€D1ใ€R2ใ€Queuesใ ใ‘ใงๅ‹•ใใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใ‚ตใƒผใƒใƒผใงใ€Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใพใ™ใ€‚

ๅ€‹ไบบ็š„ใซ้ข็™ฝใ„ใจๆ€ใฃใŸใฎใฏๅ‡บ็™บ็‚นใงใ€Cloudflare้šœๅฎณใฎใŸใณใซใƒ•ใ‚งใƒ‡ใ‚ฃใƒใƒผใ‚นใฎใ‚ตใƒผใƒใƒผใŒใพใจใ‚ใฆ่ฝใกใ‚‹ใฎใ‚’่ฆ‹ใฆใ€ใ€Œใใ‚Œใชใ‚‰ใ„ใฃใCloudflareใฎไธŠใงๅ‹•ใ‹ใ›ใฐใ‚ˆใ„ใฎใงใฏใ€ใจๆ€ใฃใŸใฎใŒๅง‹ใพใ‚Šใ ใใ†ใงใ™ใ€‚

ๅฐ่ฆๆจกใชใ‚คใƒณใ‚นใ‚ฟใƒณใ‚นใชใ‚‰Cloudflareใฎ็„กๆ–™ใƒ—ใƒฉใƒณใงใ€ๅฐ‘ใ—ๅคงใใใชใฃใฆใ‚‚ๆœˆ5ใƒ‰ใƒซใใ‚‰ใ„ใง้‹ๅ–ถใงใใ‚‹ใ“ใจใ‚’็›ฎๆŒ‡ใ—ใฆใ„ใ‚‹ใจใฎใ“ใจใ€‚ใพใ ๅˆๆœŸใƒใƒผใ‚ธใƒงใƒณใชใฎใงๆœชๅฎŸ่ฃ…ใฎ้ƒจๅˆ†ใ‚‚ๅคšใใ€Mastodonใ‚„Misskey APIใจใฎไบ’ๆ›ๆ€งใฏๆœชใ ๅ…ˆใฎ็›ฎๆจ™ใฟใŸใ„ใงใ™ใ€‚

Fedifyใ‚’ไฝฟใฃใฆใใ‚Œใฆใ„ใ‚‹ใฎใ‚‚ใ‚ใฃใฆใ€ๅ€‹ไบบ็š„ใซๅฌ‰ใ—ใ„ใงใ™ใ€‚ๆฐ—ใซใชใฃใŸใฎใงๅ…ฑๆœ‰ใ—ใพใ™ใ€‚

ใ‚ฝใƒผใ‚นใ‚ณใƒผใƒ‰ใฏAGPL 3.0ใงGitHubใงๅ…ฌ้–‹ใ•ใ‚Œใฆใ„ใพใ™ใ€‚

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

็Ÿฅไบบ(์ง€์ธ)์ธ @siliconsjang ๋‹˜์ด ์˜ค๋Š˜ SiliconBeest v1.0.0์„ ๅ…ฌ้–‹(๊ณต๊ฐœ)ํ–ˆ์Šต๋‹ˆ๋‹ค. Fedify์™€ Cloudflare๋ฅผ ๅŸบ็›ค(๊ธฐ๋ฐ˜)์œผ๋กœ ๋งŒ๋“  ์†Œํ”„ํŠธ์›จ์–ด์ธ๋ฐ, Workers, D1, R2, Queues ๋“ฑ ์„œ๋ฒ„๋ฆฌ์Šค ์Šคํƒ ์œ„์—์„œ ๅ…จ้ƒจ(์ „๋ถ€) ๋Œ์•„๊ฐ‘๋‹ˆ๋‹ค.

็™ผๆƒณ(๋ฐœ์ƒ)์˜ ๅ‡บ็™ผ้ปž(์ถœ๋ฐœ์ )์ด ์žฌ๋ฐŒ์Šต๋‹ˆ๋‹ค. Cloudflare ้šœ็ค™(์žฅ์• ) ๋•Œ ่ฏๅˆๅฎ‡ๅฎ™(์—ฐํ•ฉ์šฐ์ฃผ) ์„œ๋ฒ„๋“ค์ด ๋ฉ๋‹ฌ์•„ ๋‹ค์šด๋˜๋Š” ๊ฑธ ๋ณด๊ณ , ใ€Œ๊ทธ๋Ÿผ ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋Œ๋ฆฌ๋ฉด ๋˜์ง€ ์•Š๋‚˜?」๋ผ๋Š” ์ƒ๊ฐ์—์„œ ๅง‹ไฝœ(์‹œ์ž‘)ํ–ˆ๋‹ค๊ณ  ํ•˜๋„ค์š”.

่ฒป็”จ(๋น„์šฉ) ้ข(๋ฉด)์—์„œ๋Š” ๅฐ่ฆๆจก(์†Œ๊ทœ๋ชจ) ์ธ์Šคํ„ด์Šค๋Š” Cloudflare ็„กๆ–™(๋ฌด๋ฃŒ) ํ”Œ๋žœ, ์กฐ๊ธˆ ๋” ํฐ ่ฆๆจก(๊ทœ๋ชจ)๋Š” ๆœˆ(์›”) $5 ํ”Œ๋žœ์œผ๋กœ ๅ ช็•ถ(๊ฐ๋‹น)ํ•  ์ˆ˜ ์žˆ๋„๋ก ํ•˜๋Š” ๊ฒŒ ็›ฎๆจ™(๋ชฉํ‘œ)๋ผ๊ณ  ํ•ฉ๋‹ˆ๋‹ค. ์•„์ง ๅˆๆœŸ(์ดˆ๊ธฐ) ๋ฒ„์ „์ด๋ผ ๆœชๅ…ท้กฏ(๋ฏธ๊ตฌํ˜„) ๆฉŸ่ƒฝ(๊ธฐ๋Šฅ)์ด ๋งŽ๊ณ , Mastodon ๋ฐ Misskey API ไบ’ๆ›(ํ˜ธํ™˜)์€ ้•ทๆœŸ(์žฅ๊ธฐ) ็›ฎๆจ™(๋ชฉํ‘œ)๋กœ ๋ณด๊ณ  ์žˆ๋‹ค๋„ค์š”.

Fedify๋ฅผ ์จ์ฃผ์‹œ๋Š” ๋ถ„์ด๋ผ ๋ฐ˜๊ฐ‘๊ธฐ๋„ ํ•˜๊ณ , ๆ‡‰ๆด(์‘์›)ํ•˜๊ณ  ์‹ถ์–ด ็ดนไป‹(์†Œ๊ฐœ)ํ•ฉ๋‹ˆ๋‹ค.

์†Œ์Šค ์ฝ”๋“œ๋Š” AGPL 3.0์œผ๋กœ GitHub์— ๊ณต๊ฐœ๋˜์–ด ์žˆ์Šต๋‹ˆ๋‹ค.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

A friend of mine, @siliconsjang, released SiliconBeest v1.0.0 today. It's a server built on Workers, D1, R2, and Queues, using Fedify.

I like the starting point: after watching fediverse servers go down together during Cloudflare outages, they thought, why not just run on Cloudflare directly?

They're aiming for something cheap enough that a small instance can stay on Cloudflare's free plan, and a somewhat bigger one can fit in the $5/month tier. It's still early; a lot is missing, and Mastodon/Misskey API compatibility is more of a long-term goal.

I'm glad to see Fedify put to use for something like this. Worth checking out.

The source code is on GitHub under AGPL 3.0.

github.com

GitHub - SJang1/siliconbeest: Fediverse in Cloudflare Workers + live serverless code

Fediverse in Cloudflare Workers + live serverless code - SJang1/siliconbeest

@siliconsjang@hackers.pub

์•ˆ๋…•ํ•˜์„ธ์š”! Hello everyone!

SiliconBeest v1.0.0 ๊ณต๊ฐœ

๋งˆ์Šคํ† ๋ˆ API ํ˜ธํ™˜์„ ๋ชฉํ‘œ๋กœ ํ•˜๋Š” Cloudflare ์—ฃ์ง€ ์ปดํ“จํŒ… ๊ธฐ๋ฐ˜ ์„œ๋ฒ„๋ฆฌ์Šค ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด, SiliconBeest v1.0.0์„ ๊ณต๊ฐœํ•˜๊ฒŒ ๋˜์–ด ๊ธฐ์ฉ๋‹ˆ๋‹ค.

I'm pleased to announce SiliconBeest v1.0.0, a serverless fediverse software project built on Cloudflare edge computing, aiming for Mastodon API compatibility.

SiliconBeest Logo - a wildebeest with silicon on it


์„ค๋ช… (Description)

ko

  • SiliconBeest๋Š” Cloudflare Workers ํ™˜๊ฒฝ์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ํ”„๋กœ์ ํŠธ์ž…๋‹ˆ๋‹ค.
  • Cloudflare ์žฅ์• ๊ฐ€ ๋ฐœ์ƒํ–ˆ์„ ๋•Œ ๋‹ค์ˆ˜์˜ ์—ฐํ•ฉ์šฐ์ฃผ ์„œ๋ฒ„๊ฐ€ ํ•จ๊ป˜ ์ ‘์† ๋ถˆ๊ฐ€ ์ƒํƒœ๊ฐ€ ๋˜๋Š” ๊ฒƒ์„ ๋ณด๋ฉฐ, ์—ฐํ•ฉ์šฐ์ฃผ ์—ญ์‹œ Cloudflare ์ธํ”„๋ผ์— ์ƒ๋‹นํžˆ ์˜์กดํ•˜๊ณ  ์žˆ๋‹ค๋Š” ์ ์— ์ฐฉ์•ˆํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ๊ทธ๋ ‡๋‹ค๋ฉด ์•„์˜ˆ Cloudflare ์œ„์—์„œ ๋™์ž‘ํ•˜๋Š” ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ๋งŒ๋“ค์–ด๋ณด์ž๋Š” ์ƒ๊ฐ์—์„œ ์‹œ์ž‘ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • Cloudflare Inc.์—์„œ ๊ฐœ๋ฐœํ–ˆ๋˜ Wildebeest ํ”„๋กœ์ ํŠธ์˜ ์•„์ด๋””์–ด์™€ ์ผ๋ถ€ ์ฝ”๋“œ๋ฅผ ์ฐธ๊ณ ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ํ”„๋กœ์ ํŠธ ์ด๋ฆ„์€ ์ œ ๋‹‰๋„ค์ž„์ธ silicon(sjang) ์ด๋ž‘ Cloudflare์˜ Wildebeest๋ฅผ ์กฐํ•ฉํ•ด SiliconBeest๋กœ ์ •ํ–ˆ์Šต๋‹ˆ๋‹ค.
  • ์ ์€ ์‚ฌ์šฉ์ž ์ˆ˜์™€ ์ž‘์€ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์„ ๊ธฐ์ค€์œผ๋กœ๋Š” Cloudflare ๋ฌด๋ฃŒ ํ”Œ๋žœ์—์„œ๋„ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋„๋ก, ์กฐ๊ธˆ ๋” ํฐ ๊ทœ๋ชจ์˜ ์—ฐํ•ฉ์—์„œ๋Š” ์›” $5 ํ”Œ๋žœ์œผ๋กœ๋„ ๊ฐ๋‹นํ•  ์ˆ˜ ์žˆ๋„๋ก ๋งŒ๋“œ๋Š” ๊ฒƒ์„ ๋ชฉํ‘œ๋กœ ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.
  • API ์ธก๋ฉด์—์„œ SiliconBeest์˜ ๋ชฉํ‘œ๋Š” Mastodon ๋ฐ Misskey API์™€์˜ ํ˜ธํ™˜์ž…๋‹ˆ๋‹ค. ๋‹ค๋งŒ ์ด๋ก ์ ์œผ๋กœ ๊ฐ€๋Šฅํ•œ ๊ฒƒ๊ณผ ์‹ค์ œ ๊ตฌํ˜„์€ ๋ณ„๊ฐœ์˜ ๋ฌธ์ œ์ด๊ธฐ ๋•Œ๋ฌธ์—, ํ•ด๋‹น ๋ถ€๋ถ„์€ ์•„์ง ๊ฐœ๋ฐœ ์ค‘์ด๋ฉฐ ์žฅ๊ธฐ์ ์ธ ๋ชฉํ‘œ๋กœ ๋ณด๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

en

  • SiliconBeest is a fediverse project designed to run on Cloudflare Workers.
  • After seeing many fediverse servers become unavailable when Cloudflare had outages, I realized that the fediverse already relies heavily on Cloudflare infrastructure.
  • So I thought: why not build fediverse software directly on top of Cloudflare?
  • This project was inspired by Cloudflare Inc.โ€™s Wildebeest project, and it also references some of its ideas and code.
  • The project name, SiliconBeest, comes from my nickname silicon(sjang) combined with Cloudflareโ€™s Wildebeest.
  • Iโ€™m still working on making it as inexpensive to run as possible. For now, the goal is to support a small number of users with a small federation footprint on the free plan, and a medium federation footprint on the $5 plan.
  • From an API perspective, SiliconBeest aims to be compatible with both Mastodon and Misskey APIs. However, as many people know, full compatibility is difficult in practice, so this remains a long-term goal rather than something fully implemented today.

์•„์ง์€ ์ดˆ๊ธฐ ๋ฒ„์ „์ด๋ผ ๊ตฌํ˜„๋˜์ง€ ์•Š์€ ๋ถ€๋ถ„๋„ ๋งŽ์ง€๋งŒ, Cloudflare Workers, D1, R2, Queues ๋“ฑ Cloudflare์˜ ์„œ๋ฒ„๋ฆฌ์Šค ์ธํ”„๋ผ ์œ„์—์„œ ์—ฐํ•ฉ์šฐ์ฃผ ์†Œํ”„ํŠธ์›จ์–ด๋ฅผ ์–ผ๋งˆ๋‚˜ ๊ฐ€๋ณ๊ณ  ์ €๋ ดํ•˜๊ฒŒ ์šด์˜ํ•  ์ˆ˜ ์žˆ๋Š”์ง€ ์‹คํ—˜ํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

This is still an early version, and many parts are not implemented yet. However, SiliconBeest is an experiment in how lightweight and affordable fediverse software can be when built on top of Cloudflareโ€™s serverless infrastructure, such as Workers, D1, R2, and Queues.

ํ˜„์žฌ v1.0.0์—์„œ๋Š” ๊ธฐ๋ณธ์ ์ธ ๊ตฌ์กฐ์™€ ํ•ต์‹ฌ ๊ธฐ๋Šฅ์„ ๋จผ์ € ์ •๋ฆฌํ•˜๋Š” ๋ฐ ์ง‘์ค‘ํ–ˆ์œผ๋ฉฐ, ์•ž์œผ๋กœ Mastodon API ํ˜ธํ™˜์„ฑ, federation ์•ˆ์ •์„ฑ, ๊ด€๋ฆฌ ๋„๊ตฌ, ๋ฌธ์„œํ™” ๋“ฑ์„ ์ ์ง„์ ์œผ๋กœ ๊ฐœ์„ ํ•ด๋‚˜๊ฐˆ ์˜ˆ์ •์ž…๋‹ˆ๋‹ค.

In v1.0.0, I focused on organizing the basic architecture and core functionality first. Going forward, I plan to gradually improve Mastodon API compatibility, federation stability, admin tooling, and documentation.

๊ด€์‹ฌ ์žˆ์œผ์‹  ๋ถ„๋“ค์€ GitHub ์ €์žฅ์†Œ๋ฅผ ํ™•์ธํ•ด์ฃผ์‹œ๊ณ , ์ด์Šˆ๋‚˜ ํ”ผ๋“œ๋ฐฑ๋„ ์–ธ์ œ๋“  ํ™˜์˜ํ•ฉ๋‹ˆ๋‹ค.

If youโ€™re interested, please check out the GitHub repository. Issues, feedback, and suggestions are always welcome.

https://github.com/SJang1/siliconbeest


์„ค์น˜ ๋ฐ ๋ฐฐํฌ ๋ฐฉ๋ฒ• (Installation and Deployment)

SiliconBeest๋Š” GitHub ํ…œํ”Œ๋ฆฟ๊ณผ Cloudflare๋ฅผ ์ด์šฉํ•ด ๋น„๊ต์  ๊ฐ„๋‹จํ•˜๊ฒŒ ๋ฐฐํฌํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

  1. GitHub ํ…œํ”Œ๋ฆฟ์—์„œ ์ƒˆ ์ €์žฅ์†Œ๋ฅผ ์ƒ์„ฑํ•ฉ๋‹ˆ๋‹ค.
  2. Cloudflare์—์„œ ํ•„์š”ํ•œ ๋ฆฌ์†Œ์Šค์™€ ํ™˜๊ฒฝ์„ ์„ค์ •ํ•ฉ๋‹ˆ๋‹ค.
  3. Cloudflare API ํ† ํฐ๊ณผ ํ•„์š”ํ•œ ํ™˜๊ฒฝ๋ณ€์ˆ˜๋ฅผ GitHub Secrets์— ์ €์žฅํ•ฉ๋‹ˆ๋‹ค.
  4. GitHub Actions๋ฅผ ํ†ตํ•ด ์ž๋™ ๋ฐฐํฌ๋ฅผ ์ง„ํ–‰ํ•ฉ๋‹ˆ๋‹ค.
  5. ๋ฐฐํฌ๊ฐ€ ์™„๋ฃŒ๋˜๋ฉด ์ธ์Šคํ„ด์Šค ์„ค์ •์„ ๋งˆ๋ฌด๋ฆฌํ•ฉ๋‹ˆ๋‹ค.

์•„์ง ์„ค์น˜ ๊ณผ์ •์€ ๊ณ„์† ๋‹ค๋“ฌ๊ณ  ์žˆ์œผ๋ฉฐ, ๊ฐœ์„ ์‚ฌํ•ญ์ด ๋งŽ์Œ์„ ์•Œ๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค. ์ถ”ํ›„ ๋ณด๊ฐ•ํ•ด ๋‚˜๊ฐˆ ์˜ˆ์ •์ด๋ฉฐ, ์ด์— ๋Œ€ํ•œ PR๋„ ํ™˜์˜์ž…๋‹ˆ๋‹ค.

SiliconBeest can be deployed relatively easily using a GitHub template and Cloudflare.

  1. Create a new repository from the GitHub template.
  2. Set up the required resources and environment on Cloudflare.
  3. Store the Cloudflare API token and required environment variables in GitHub Secrets.
  4. Deploy automatically using GitHub Actions.
  5. Once deployment is complete, finish configuring your instance.

The installation process is still being refined, and Iโ€™m aware that there is plenty of room for improvement. I plan to keep improving the documentation and deployment flow over time, and related PRs are always welcome.

@nibushibu@vivaldi.net ยท Reply to GENKI

ใฎ AI Crawl Control ๅˆ†ใ‹ใ‚Šใ‚„ใ™ใใฆใ„ใ„ใชใ€‚ใ—ใ‹ใ‚‚็„กๆ–™ๆž ใงใ‚‚ใคใ‹ใˆใฆใ‚ใ‚ŠใŒใŸใ„ :tony_santa:

@Profpatsch@mastodon.xyz
Github issue

turt2live
1 hour ago
Member

 >   Is there any information on why this happened? If its something fundamental related to hosting Matrix related infrastructure on Cloudflare, I think it should be reported on in more detail.

Cloudflare uses the 451 error code in response to legal notices they receive. Cloudflare's documentation covers the error code in more detail: https://developers.cloudflare.com/support/troubleshooting/http-status-codes/4xx-client-error/error-451/

matrix.to and app.element.io received separate notices for reported illegal content on the domains very close to each other. Cloudflare seemingly responded by placing a 451 block on the domains. Cloudflare removed the blocks after we dealt with the reports and appealed.

Both domains are client-side applications with no backend component, however it appears they were used to reference or access the reported material.
ALT text

Github issue turt2live 1 hour ago Member > Is there any information on why this happened? If its something fundamental related to hosting Matrix related infrastructure on Cloudflare, I think it should be reported on in more detail. Cloudflare uses the 451 error code in response to legal notices they receive. Cloudflare's documentation covers the error code in more detail: https://developers.cloudflare.com/support/troubleshooting/http-status-codes/4xx-client-error/error-451/ matrix.to and app.element.io received separate notices for reported illegal content on the domains very close to each other. Cloudflare seemingly responded by placing a 451 block on the domains. Cloudflare removed the blocks after we dealt with the reports and appealed. Both domains are client-side applications with no backend component, however it appears they were used to reference or access the reported material.

@TechieNotNetie@vivaldi.net

Update (Apr 15, 1900 CET): Cloudflare just pushed a fix to production, and my testing on a site seems to confirm that the problem is gone.

Hello all,

In the past week we have received a lot of reports in the @Vivaldi forums about problems with the @cloudflare "Are you a human?"-"verification" system used by many web sites.

We just posted a forum post explaining the underlying issues and a workaround for one common issue related to the current problems.

forum.vivaldi.net/topic/117404

forum.vivaldi.net

Cloudflare "verification" and Vivaldi (April 2026)

Update (Apr 15, 1900 CET): Cloudflare just pushed a fix to production, and my testing on a site seems to confirm that the problem is gone. Hello all, Recentl...

@zeldman@front-end.social
@zeldman@front-end.social
@ggrey@thelab.uno

Se cercate un servizio di messaggistica istantanea, decentralizzata, interoperabile e rispettosa della privacy, Delta Chat รจ lโ€™alternativa ideale alle Big Tech americane. Non richiede numero di telefono nรฉ email e offre quasi tutte le funzioni delle app piรน popolari. Qui di seguito c’e’ un confronto tra Delta Chat e Signal, due delle piattaforme di messaggistica istantanea.

10 motivi per cui Delta Chat รจ migliore di Signal.

  1. Delta Chat ha i canali (uno-a-molti come su Telegram), Signal no.

  2. Signal รจ centralizzato e quindi molto piรน facile da bloccare, mentre Delta Chat puรฒ funzionare anche in reti intranet e mesh.

  3. Delta Chat, essendo decentralizzato, puรฒ appoggiarsi a piรน server (chiamati relays) contemporaneamente: se uno smette di funzionare, la comunicazione continua senza interruzioni grazie agli altri. Signal, invece, dipende da unโ€™infrastruttura centralizzata: quando servizi come AWS (Amazon Web Services) o Cloudflare subiscono downtime, anche Signal smette di funzionare. Non a caso, Delta Chat riesce a operare anche in paesi con forti restrizioni come Iran, Russia e Cina, mentre Signal in contesti simili (ad esempio durante un viaggio in Cina) potrebbe non funzionare affatto.

  4. Signal non supporta lโ€™uso dello stesso account su piรน telefoni, e il multi dispositivo con desktop รจ debole e dipende ancora dal telefono; con Delta Chat puoi avere piรน dispositivi contemporaneamente ed รจ facilissimo aggiungerne un secondo.

  5. Ogni dispositivo in Delta Chat funziona come un backup completo automatico incrementale, mentre in Signal devi caricare i backup sul cloud ed eventualmente pagare quando diventano troppo grandi.

  6. In Delta Chat puoi avere diversi profili, quanti ne vuoi, separando facilmente il profilo di lavoro (con nome e avatar piรน seri) da quello familiare, dove puoi usare nome e avatar piรน informali. Signal permette un solo profilo.

  7. Non servono numeri di telefono nรฉ dati privati per usare Delta Chat: lโ€™onboarding รจ facilissimo, senza codici SMS nรฉ CAPTCHA da risolvere come su Signal.

  8. Nessuno sconosciuto puรฒ trovarti e inviarti spam o phishing su Delta Chat poichรฉ’ la chat funziona con inviti personali via QR code o link, e lo stesso vale per i tuoi familiari: รจ quindi uno spazio piรน sicuro per le chat di famiglia. Su Signal รจ facile trovarti per chi ha giร  o ha ricevuto direttamente o indirettamente il tuo numero cellulare.

  9. DeltaChat offre mini-app in chat offline come giochi, editor di testo collaborativi, checklist, liste della spesa e altri strumenti, tutti con crittografia end-to-end e senza servizi di terzi che li ospitano: le mini-app vivono nelle chat private e solo i membri possono accedervi. Signal ha funzioni simili ma si basano su app online e centralizzate.

  10. In Delta Chat puoi salvare i messaggi in una chat โ€œMessaggi salvatiโ€; Signal ha anche โ€œNote personaliโ€, ma ciรฒ che รจ superiore in Delta Chat รจ che puoi anche saltare dal messaggio salvato/preferito a quello originale e vederlo nel contesto della chat, mentre in Signal viene semplicemente inoltrata una copia del messaggio.

Il codice sorgente di Delta Chat รจ open source ed รจ gestito da un gruppo di sviluppatori indipendenti che, insieme agli operatori dei server relay, rendono il protocollo sicuro e decentralizzato, quindi non contaminato da bot di intelligenza artificiale come WhatsApp e, soprattutto, non sotto il controllo delle Big Tech americane come Meta, Google o Microsoft.

This article was translated, adapted and created from an original post by @adbenitez

@delta @sicurezza @ggrey

#amazon #cloudflare #deltachat #fuckbigtech #messagging #saynotometa #signal #telegram #whatsapp
@plutarch@gotosocial.plutar.ch

#NoBot #NoIndex #NoBridge

This post is a test of a custom rule for Cloudflare I've been working on, and of my own conspiracy theory.

Forgive me my tinfoil hat: I have long suspected that the use of these tags (above), in fact, results in attracting more attention from crawlers/spiders/bots/whatever; that said automated systems exist which are specifically instructed to look for these tags, and to index any and all pages in which they find them.

If and only if my custom rule blocks a notably higher number of attempts to index this post alone, as compared to any of my other posts individually, I assume my theory is true until otherwise proven.

I will provide an update about this whenever I have one.

#CloudflareTunnel #Cloudflare #Fediverse #SelfHosting #SelfHosted

@adbenitez@mastodon.de ยท Reply to Ed W8EMV

@w8emv Delta Chat has channels (1-to-many like on Telegram), Signal doesn't

Signal is centralized and hence much more easy to block, while Delta Chat can even work in intra-net and mesh networks

Delta Chat can use several servers "relays" at the same time, do you remember that downtime with signal when or are down?? with Delta Chat if one of your relays go down you can keep chatting using the others (ex. people manage to use Delta Chat in Iran, Russia and China despite the strict network firewalls, if you go on vacations to China Signal will not work, Delta Chat will)

Signal doesn't support using the same account in multiple phones, and multi-device with desktop is weak and still depends on the phone, with delta chat you can have several devices at the same time and it is super easy to add a second device

each device in Delta Chat works as an incremental automatic full backup, while in signal you have to upload backups to some cloud and eventually pay for it when the backup is too big

in Delta Chat you can have several profiles, as much as you like, easily separate your work profile (with more serious avatar and name) from your family profile where you can use more informal name and avatar etc

you don't need phone numbers or any private data to use Delta Chat, onboarding is super easy, no SMS codes, no solving CAPTCHA like on Signal

No strangers can discover you and send you spam or fishing in Delta Chat same for your family members, so it is a safer space for family chat

has offline-first in-chat mini-apps like games, collaborative text pads, checklist, shopping lists and other tools (all end-to-end encrypted without any 3rd party service hosting such apps, they live in the chat and only chat members can access them)

in Delta Chat you can save messages in a "Saved Messages" chat, also has "Note to Self" but what is superior in Delta Chat is that you can also jump from the saved/bookmarked message to the original message and see it in its chat context, in Signal it just forwards a copy of the message to the "Note to Self" chat

and more, but this post is too long already

@adbenitez@mastodon.de ยท Reply to Ed W8EMV

@w8emv Delta Chat has channels (1-to-many like on Telegram), Signal doesn't

Signal is centralized and hence much more easy to block, while Delta Chat can even work in intra-net and mesh networks

Delta Chat can use several servers "relays" at the same time, do you remember that downtime with signal when or are down?? with Delta Chat if one of your relays go down you can keep chatting using the others (ex. people manage to use Delta Chat in Iran, Russia and China despite the strict network firewalls, if you go on vacations to China Signal will not work, Delta Chat will)

Signal doesn't support using the same account in multiple phones, and multi-device with desktop is weak and still depends on the phone, with delta chat you can have several devices at the same time and it is super easy to add a second device

each device in Delta Chat works as an incremental automatic full backup, while in signal you have to upload backups to some cloud and eventually pay for it when the backup is too big

in Delta Chat you can have several profiles, as much as you like, easily separate your work profile (with more serious avatar and name) from your family profile where you can use more informal name and avatar etc

you don't need phone numbers or any private data to use Delta Chat, onboarding is super easy, no SMS codes, no solving CAPTCHA like on Signal

No strangers can discover you and send you spam or fishing in Delta Chat same for your family members, so it is a safer space for family chat

has offline-first in-chat mini-apps like games, collaborative text pads, checklist, shopping lists and other tools (all end-to-end encrypted without any 3rd party service hosting such apps, they live in the chat and only chat members can access them)

in Delta Chat you can save messages in a "Saved Messages" chat, also has "Note to Self" but what is superior in Delta Chat is that you can also jump from the saved/bookmarked message to the original message and see it in its chat context, in Signal it just forwards a copy of the message to the "Note to Self" chat

and more, but this post is too long already

@adbenitez@mastodon.de ยท Reply to Ed W8EMV

@w8emv Delta Chat has channels (1-to-many like on Telegram), Signal doesn't

Signal is centralized and hence much more easy to block, while Delta Chat can even work in intra-net and mesh networks

Delta Chat can use several servers "relays" at the same time, do you remember that downtime with signal when or are down?? with Delta Chat if one of your relays go down you can keep chatting using the others (ex. people manage to use Delta Chat in Iran, Russia and China despite the strict network firewalls, if you go on vacations to China Signal will not work, Delta Chat will)

Signal doesn't support using the same account in multiple phones, and multi-device with desktop is weak and still depends on the phone, with delta chat you can have several devices at the same time and it is super easy to add a second device

each device in Delta Chat works as an incremental automatic full backup, while in signal you have to upload backups to some cloud and eventually pay for it when the backup is too big

in Delta Chat you can have several profiles, as much as you like, easily separate your work profile (with more serious avatar and name) from your family profile where you can use more informal name and avatar etc

you don't need phone numbers or any private data to use Delta Chat, onboarding is super easy, no SMS codes, no solving CAPTCHA like on Signal

No strangers can discover you and send you spam or fishing in Delta Chat same for your family members, so it is a safer space for family chat

has offline-first in-chat mini-apps like games, collaborative text pads, checklist, shopping lists and other tools (all end-to-end encrypted without any 3rd party service hosting such apps, they live in the chat and only chat members can access them)

in Delta Chat you can save messages in a "Saved Messages" chat, also has "Note to Self" but what is superior in Delta Chat is that you can also jump from the saved/bookmarked message to the original message and see it in its chat context, in Signal it just forwards a copy of the message to the "Note to Self" chat

and more, but this post is too long already

@bms48@mastodon.social ยท Reply to sheislaurence

@sheislaurence THIS. I kicked Microsoft to the kerb with 10 days ago on my development . They pushed updates which broke my running development VMs. Edge constantly leaks memory and is rejected by Web security including PoW checks. performance counter passthrough is broken. Ads in the start menu. . The list goes on. Microsoft products are not fit for purpose. I am being impartial, I tried for nearly a year.

@josusanz@mastodon.social
@zenn_trend_bot@silicon.moe ยท Reply to Zenn Trends

๐Ÿ“ฐ ใƒขใƒ€ใƒณใง็ˆ†้€Ÿใ€‚ๆœˆ้ก0ๅ††ใงWebใ‚ขใƒ—ใƒชใ‚’้–‹็™บใƒปๅ…ฌ้–‹ใ™ใ‚‹ๆŠ€่ก“ๆง‹ๆˆ๏ผˆHono/Neon/Drizzle/Cloudflare Pages๏ผ‰ (๐Ÿ‘ 87)

๐Ÿ‡ฌ๐Ÿ‡ง Zero-cost modern web stack: Hono + Neon + Drizzle + Cloudflare Pages. Fast and free to deploy.
๐Ÿ‡ฐ๐Ÿ‡ท ์›” 0์›์œผ๋กœ ๋ชจ๋˜ ์›น์•ฑ ๊ฐœ๋ฐœยท๋ฐฐํฌํ•˜๋Š” ๊ธฐ์ˆ  ์Šคํƒ: Hono, Neon, Drizzle, Cloudflare Pages.

๐Ÿ”— zenn.dev/epicai_techblog/artic

zenn.dev

ใƒขใƒ€ใƒณใง็ˆ†้€Ÿใ€‚ๆœˆ้ก0ๅ††ใงWebใ‚ขใƒ—ใƒชใ‚’้–‹็™บใƒปๅ…ฌ้–‹ใ™ใ‚‹ๆŠ€่ก“ๆง‹ๆˆ๏ผˆHono/Neon/Drizzle/Cloudflare Pages๏ผ‰

@kkarhan@infosec.space ยท Reply to Daniรซl Franke :panheart:

@ainmosni mine are:

No-Gos:

Green flags:

  • Operated and/or maintained by trans*, nonbinary and/or furries.
  • Clearly banning AI & AIslop if not outright sabotaging /tarpitting / hacking any AI bullshit.
  • and are part of the goals.
  • Active development
    • Active issue tracker
  • Regular releases

Yellow Flags (that need context):

  • Low/no activity
    • archived repo
  • few releases
@MrWillCom@noc.social

Cloudflare open-sourced a component library. It seems that this library powers their dashboard.

For non-Tailwind developers, they even provide a standalone stylesheet. I'm so touched!

kumo-ui.com/

The Kumo documentation website displays a grid of core web components including buttons, inputs with validation, switches, and checkboxes. A sidebar on the left lists navigation links and a comprehensive library of UI elements.
ALT text

The Kumo documentation website displays a grid of core web components including buttons, inputs with validation, switches, and checkboxes. A sidebar on the left lists navigation links and a comprehensive library of UI elements.

A screenshot of the Kumo documentation page for "Import Styles" showing two CSS distribution options. It includes code snippets for importing Tailwind-specific styles or a standalone build for non-Tailwind users.
ALT text

A screenshot of the Kumo documentation page for "Import Styles" showing two CSS distribution options. It includes code snippets for importing Tailwind-specific styles or a standalone build for non-Tailwind users.

A minimalist animation sequence showing the kanji character for "cloud" (้›ฒ) morphing into a three-line hamburger menu icon and back again.
ALT text

A minimalist animation sequence showing the kanji character for "cloud" (้›ฒ) morphing into a three-line hamburger menu icon and back again.

@abnv@fantastic.earth

Yesterday my website running on my tiny VPS was discovered by terrible Chinese crawlers. They come from random IPs, use headless browsers to visit one page at a time, very rapidly. So I had to get it on proxy and turn on Cloudflare verification. Sigh. :blobcatverysad:

@abnv@fantastic.earth

Yesterday my website running on my tiny VPS was discovered by terrible Chinese crawlers. They come from random IPs, use headless browsers to visit one page at a time, very rapidly. So I had to get it on proxy and turn on Cloudflare verification. Sigh. :blobcatverysad:

@0xabad1dea@infosec.exchange

they edited the clearly LLM-generated-and-human-unread readme to โ€œclarifyโ€ that by production-ready matrix server by Cloudflare they meant a proof-of-concept matrix server not endorsed for production use by Cloudflare. They removed all the lines like โ€œ// TODO: implement authenticationโ€ from the source code without implementing anything

a colorized git diff:

old text in red: A production-grade Matrix home server implementation blablabla Cloudflare 

new text in green: this is a proof of concept Matrix home server implementation blablabla Cloudflare not endorsed
ALT text

a colorized git diff: old text in red: A production-grade Matrix home server implementation blablabla Cloudflare new text in green: this is a proof of concept Matrix home server implementation blablabla Cloudflare not endorsed

@JadedBlueEyes@tech.lgbt

Cloudflare just published a vibe coded blog post claiming they implemented Matrix on cloudflare workers. They didn't, their post and README is AI generated and the code doesn't do any of the core parts of matrix that make it secure and interoperable. Instead it's littered with 'TODO: Check authorisation' and similar

blog.cloudflare.com/serverless

blog.cloudflare.com

Building a serverless, post-quantum Matrix homeserver

We ported a complete Matrix homeserver to Cloudflare Workers โ€” delivering encrypted messaging at the edge with automatic post-quantum cryptography.

@0xabad1dea@infosec.exchange

they edited the clearly LLM-generated-and-human-unread readme to โ€œclarifyโ€ that by production-ready matrix server by Cloudflare they meant a proof-of-concept matrix server not endorsed for production use by Cloudflare. They removed all the lines like โ€œ// TODO: implement authenticationโ€ from the source code without implementing anything

a colorized git diff:

old text in red: A production-grade Matrix home server implementation blablabla Cloudflare 

new text in green: this is a proof of concept Matrix home server implementation blablabla Cloudflare not endorsed
ALT text

a colorized git diff: old text in red: A production-grade Matrix home server implementation blablabla Cloudflare new text in green: this is a proof of concept Matrix home server implementation blablabla Cloudflare not endorsed

@JadedBlueEyes@tech.lgbt

Cloudflare just published a vibe coded blog post claiming they implemented Matrix on cloudflare workers. They didn't, their post and README is AI generated and the code doesn't do any of the core parts of matrix that make it secure and interoperable. Instead it's littered with 'TODO: Check authorisation' and similar

blog.cloudflare.com/serverless

blog.cloudflare.com

Building a serverless, post-quantum Matrix homeserver

We ported a complete Matrix homeserver to Cloudflare Workers โ€” delivering encrypted messaging at the edge with automatic post-quantum cryptography.

@0xabad1dea@infosec.exchange

they edited the clearly LLM-generated-and-human-unread readme to โ€œclarifyโ€ that by production-ready matrix server by Cloudflare they meant a proof-of-concept matrix server not endorsed for production use by Cloudflare. They removed all the lines like โ€œ// TODO: implement authenticationโ€ from the source code without implementing anything

a colorized git diff:

old text in red: A production-grade Matrix home server implementation blablabla Cloudflare 

new text in green: this is a proof of concept Matrix home server implementation blablabla Cloudflare not endorsed
ALT text

a colorized git diff: old text in red: A production-grade Matrix home server implementation blablabla Cloudflare new text in green: this is a proof of concept Matrix home server implementation blablabla Cloudflare not endorsed

@JadedBlueEyes@tech.lgbt

Cloudflare just published a vibe coded blog post claiming they implemented Matrix on cloudflare workers. They didn't, their post and README is AI generated and the code doesn't do any of the core parts of matrix that make it secure and interoperable. Instead it's littered with 'TODO: Check authorisation' and similar

blog.cloudflare.com/serverless

blog.cloudflare.com

Building a serverless, post-quantum Matrix homeserver

We ported a complete Matrix homeserver to Cloudflare Workers โ€” delivering encrypted messaging at the edge with automatic post-quantum cryptography.

@MrWillCom@noc.social

I have joined the waiting list to try it out. Looking forward to this.

The Cloudflare dashboard shows the Email Sending beta page with a confirmation button stating, "Already joined to the waiting list!"
ALT text

The Cloudflare dashboard shows the Email Sending beta page with a confirmation button stating, "Already joined to the waiting list!"

@theraspb@aus.social

do you use cloudflare? if so what parts do you use? i'm personally interested in the DNS and CDN parts of their offering, but interested to hear what else you use.

  • Yes, I just use it for DNS4 (27%)
  • Yes, I use it for DNS and CDN/attacks1 (7%)
  • No, I host my own DNS4 (27%)
  • No, I use SERVFAIL0 (0%)
  • No, I use a different cloud provider3 (20%)
  • Other, plz comment3 (20%)

@ecosia

Out of curiosity, I analysed Ecosia's infrastructure (through IPs and ASNs) to find out whether it is or not.

I was surprised to find that it relies on S3 for financial data reports (stored .json data), Cloudfront for the Ecosia.org search, Fastly for blog.ecosia.org, for the Ecosia.org homepage, Ads and probably others.

In July 2025, they posted on their blog that 'digital is just ', stating that Europe's digital backbone is dependent on the US and all the problems this entails, such as a lack of control.

They also said, 'We've always believed that where you search matters' and 'Digital is climate action too', despite the fact that they depend on Big Tech themselves and use almost no EU infrastructure in practice.

As Ecosia is a signatory to the initiative, why haven't you migrated your infrastructure to solutions?

It is worrying to know that, by switching to Ecosia, practically 100% of my traffic goes through non-EU companies. I would like to see more independence on your part.

'Building and using local infrastructure means reducing transatlantic data traffic, increasing energy efficiency, and cutting down on the carbon footprint of cloud computing. Plus, tech companies that are based here are more likely to be held accountable to EU environmental standards. It's a win-win.โ€™ โ€“ Ecosia Blog blog.ecosia.org/digital-sovere

blog.ecosia.org

Digital sovereignty is just #oneclickaway

Weโ€™ve joined the #oneclickaway campaign: a call to invest in Europeโ€™s own digital infrastructure. Hereโ€™s why weโ€™re supporting it - and what you can do.

@diogop@ieji.de ยท Reply to Metin Seven ๐ŸŽจ

@metin I moved from Github to a self-hosted Gitea instance that I self-host on OVH, a European cloud provider.

I also moved my .dev top-level domain from Google to EURid's .eu.

I'm very happy with these changes. I no longer have to put up with AI's obsession every time I did something on GitHub.

On top of that, I no longer use Cloudflare, and recently had to install Anubis (Web AI Firewall) to stop being attacked by AI Crawlers from openai and other Big Tech companies that were scanning all the commits on my Gitea (public repositories ofc).

@kravietz@agora.echelon.pl

A fun fact from the latest #CloudFlare 2025 - practically all web today is based on #JavaScript frameworks. That is, to load simple โ€œmy company is ACME WIDGETS and hereโ€™s my phoneโ€ majority of pages will first load 145 MB of advanced JavaScript libraries and then make requests to further 50 Google and Amazon trackers to report โ€œsomeone saw your phone!โ€, wasting tons of bandwidth, electricity, memory and time.

https://blog.cloudflare.com/radar-2025-year-in-review/#javascript-based-libraries-and-frameworks-remained-integral-tools-for-building-web-sites

JavaScript-based libraries and frameworks remained integral tools for building Web sites
ALT text

JavaScript-based libraries and frameworks remained integral tools for building Web sites

@kravietz@agora.echelon.pl

A fun fact from the latest #CloudFlare 2025 - practically all web today is based on #JavaScript frameworks. That is, to load simple โ€œmy company is ACME WIDGETS and hereโ€™s my phoneโ€ majority of pages will first load 145 MB of advanced JavaScript libraries and then make requests to further 50 Google and Amazon trackers to report โ€œsomeone saw your phone!โ€, wasting tons of bandwidth, electricity, memory and time.

https://blog.cloudflare.com/radar-2025-year-in-review/#javascript-based-libraries-and-frameworks-remained-integral-tools-for-building-web-sites

JavaScript-based libraries and frameworks remained integral tools for building Web sites
ALT text

JavaScript-based libraries and frameworks remained integral tools for building Web sites

@kkarhan@infosec.space
@kkarhan@infosec.space
@kkarhan@infosec.space ยท Reply to Stuart Langridge

@sil except is a net negative in my experience as it is only good for 3 things:

Tell me i I'm wrong!

@silverbulletmd@fosstodon.org
@silverbulletmd@fosstodon.org
@MOULE@moule.world
Meme of CJ From Grand Theft Auto: San Andreas walking towards a Cloudflare 500 Internal Server Error screen and saying "Ah shit, here we go again."
ALT text

Meme of CJ From Grand Theft Auto: San Andreas walking towards a Cloudflare 500 Internal Server Error screen and saying "Ah shit, here we go again."

@MOULE@moule.world
Meme of CJ From Grand Theft Auto: San Andreas walking towards a Cloudflare 500 Internal Server Error screen and saying "Ah shit, here we go again."
ALT text

Meme of CJ From Grand Theft Auto: San Andreas walking towards a Cloudflare 500 Internal Server Error screen and saying "Ah shit, here we go again."

@shugo@social.shugo.net
@shugo@social.shugo.net
@kravietz@agora.echelon.pl ยท Reply to Emilion

@emilion

The key problem is choices made by system architects with the help of GAFAM+CF marketing departments:

  1. GAFAM hosted and CF โ€œprotectedโ€ website is now the default mode of deploying websites, whatever size, starting from school - thatโ€™s 100% marketing, itโ€™s not driven by any rational need
  2. by doing that, GAFAM+CF certainly gain user base and groom it to reproduce these choices in corporate environments
  3. this in turn dramatically increases complexity of GAFAM+CF services which now handle not only traffic of relatively small paid user base who actually need them, but also millions of free tier users whose only business goal at GAFAM+CF side isโ€ฆ marketing and user grooming
  4. it remains the fact, that 99% of websites hosted CF do not need neither AWS or CF, they use the former as a fancy alternative to simple cloud VM while the latter asโ€ฆ well, fancy extra proxy layer doing nothing

Iโ€™ve had a lot of these discussions in the enterprise Iโ€™ve worked for. After the initial layer of some architectsโ€™ deeply internalised irrational habits (โ€œYOU CANโ€™T BUILD A WEBSITE WITHOUT AWS AND CF!!!โ€) was broken, everyone promptly agreed on a consensus that CF really only makes sense for DDoS avoidance, but even in that role it should be only switched on frontends that actually need it and doesnโ€™t need to be enabled 100% of the time, only when an actual attack happens.

#CloudFlare #GAFAM

@rysiek

agora.echelon.pl

Akkoma

@latenightowl@social.linux.pizza

I haven't seen this variation of XKCD 2347 yet. Received from a friend, source unknown.

Variation on the XKCD 2347 graphic of software building on each other, showing very unstable tower, featuring sharks biting undewater cables, unpaid opensource developers, AWS, Cloudflare, AI, Microsoft, left-pad, v8, WASM and it is all almost falling apart, but not actually.
ALT text

Variation on the XKCD 2347 graphic of software building on each other, showing very unstable tower, featuring sharks biting undewater cables, unpaid opensource developers, AWS, Cloudflare, AI, Microsoft, left-pad, v8, WASM and it is all almost falling apart, but not actually.

@nb@social.biblioco.de
I have been following the developments of the @bonfire #Fediverse software for some time now, particularly their #OpenScience extension, because I see it as a future manifestation of open, interactive, publication-based #SciComm on the #Fediverse: http://openscience.network

A few days ago the first pilot was presented that is also self-hostable: https://openscience.network/setup/
However, looking at its current state, I can only take that achievement with a grain of salt.

One of the reasons why the Fediverse is so independent and resistant to central takeovers is because it does not rely on global identity service providers. This is precisely what sets it apart from other #BigTech platforms, as well as Bluesky. However, regarding the development of the Bonfire Open Science flavour, it has become apparent over the past few years that the Bonfire developers are increasingly taking a #ORCID-centric approach. The current pilot, which has now been released, even enforces the use of ORCID, including the self-hosted version. This means that users are forced to use ORCID in order to create an account.

ORCID is a global centralized identity provider that relies entirely on the infrastructure and services of US #Hyperscalers. Anyone who gets involved with ORCID submits to them being the single point of failure with all its consequences, similar to #Cloudflare (btw. guess which provider orcid.org runs on), and that is exactly the opposite of what decentralized networks are about. The organization behind ORCID is also supported by some of those big publishers, who ultimately were the reason why there had to be a counter-movement in the first place, which we now call Open Science.

Anyone who integrates providers such as ORCID into decentralized technologies is probably letting #BigTech in through the back door. #Scholia, which is based on #WikiData, offers a reasonable alternative to ORCID. Its technical infrastructure is independent from big cloud providers, large publishers cannot buy their way into its community, and it even discloses the code for its platform itself.

There is nothing wrong with having an optional feature for importing data from ORCID. However, I find it highly questionable to make user registration dependent on this service provider. I hope that in the future, attention will once again be turned to local SSO authentication services, good old-fashioned email registration, and ORCID integration will become optional.

#Hyperscaler #Centralization #Science #Bonfire

social.biblioco.de

social.biblioco.de

@JamieNemeth@toot.wales

A (horrible) alternate reality, inspired by yesterday.

Teletext mockup/art inspired by yesterday's Cloudflare outage.

P100 Teletext 100 Nov18 14:00:13

Internal server error
Visit Cloudflare on p799 for more info.
2025-11-18 14:00:13 UTC

Pixel art of a TV with bunny-ear aerial with a green tick, a TV transmitter with a red tick, and a PC with a green tick.

You, TV: Working
London, Cloudflare: Error
Teletext, Host: Working

What happened?
There is an internal error on Cloudflare's network.

What can I do?
Please try again in a few minutes.

Cloudflare  Index
ALT text

Teletext mockup/art inspired by yesterday's Cloudflare outage. P100 Teletext 100 Nov18 14:00:13 Internal server error Visit Cloudflare on p799 for more info. 2025-11-18 14:00:13 UTC Pixel art of a TV with bunny-ear aerial with a green tick, a TV transmitter with a red tick, and a PC with a green tick. You, TV: Working London, Cloudflare: Error Teletext, Host: Working What happened? There is an internal error on Cloudflare's network. What can I do? Please try again in a few minutes. Cloudflare Index

@JamieNemeth@toot.wales

A (horrible) alternate reality, inspired by yesterday.

Teletext mockup/art inspired by yesterday's Cloudflare outage.

P100 Teletext 100 Nov18 14:00:13

Internal server error
Visit Cloudflare on p799 for more info.
2025-11-18 14:00:13 UTC

Pixel art of a TV with bunny-ear aerial with a green tick, a TV transmitter with a red tick, and a PC with a green tick.

You, TV: Working
London, Cloudflare: Error
Teletext, Host: Working

What happened?
There is an internal error on Cloudflare's network.

What can I do?
Please try again in a few minutes.

Cloudflare  Index
ALT text

Teletext mockup/art inspired by yesterday's Cloudflare outage. P100 Teletext 100 Nov18 14:00:13 Internal server error Visit Cloudflare on p799 for more info. 2025-11-18 14:00:13 UTC Pixel art of a TV with bunny-ear aerial with a green tick, a TV transmitter with a red tick, and a PC with a green tick. You, TV: Working London, Cloudflare: Error Teletext, Host: Working What happened? There is an internal error on Cloudflare's network. What can I do? Please try again in a few minutes. Cloudflare Index

@rolle@mementomori.social
@JamieNemeth@toot.wales

A (horrible) alternate reality, inspired by yesterday.

Teletext mockup/art inspired by yesterday's Cloudflare outage.

P100 Teletext 100 Nov18 14:00:13

Internal server error
Visit Cloudflare on p799 for more info.
2025-11-18 14:00:13 UTC

Pixel art of a TV with bunny-ear aerial with a green tick, a TV transmitter with a red tick, and a PC with a green tick.

You, TV: Working
London, Cloudflare: Error
Teletext, Host: Working

What happened?
There is an internal error on Cloudflare's network.

What can I do?
Please try again in a few minutes.

Cloudflare  Index
ALT text

Teletext mockup/art inspired by yesterday's Cloudflare outage. P100 Teletext 100 Nov18 14:00:13 Internal server error Visit Cloudflare on p799 for more info. 2025-11-18 14:00:13 UTC Pixel art of a TV with bunny-ear aerial with a green tick, a TV transmitter with a red tick, and a PC with a green tick. You, TV: Working London, Cloudflare: Error Teletext, Host: Working What happened? There is an internal error on Cloudflare's network. What can I do? Please try again in a few minutes. Cloudflare Index

@FoW@netsphere.one

2025๋…„ 11์›” 18์ผ ํด๋ผ์šฐ๋“œํ”Œ๋ ˆ์–ด

์š”์•ฝ: ์‚ฌ์ด๋ฒ„ ๊ณต๊ฒฉ์ด๋‚˜ DDoS ๊ณต๊ฒฉ์ด ์•„๋‹Œ ๋จธ์‹ ๋Ÿฌ๋‹ ๋ชจ๋ธ์˜ ๋‚ด๋ถ€ ์„ค์ • ์˜ค๋ฅ˜๊ฐ€ ์›์ธ.

1. ๋ฐ์ดํ„ฐ๋ฒ ์ด์Šค ๊ถŒํ•œ ๋ณ€๊ฒฝ
2. ์ฟผ๋ฆฌ ๊ฒฐ๊ณผ ์˜ค๋ฅ˜ (์ค‘๋ณต ๋ฐ์ดํ„ฐ)
3. ๋ฉ”๋ชจ๋ฆฌ ์ œํ•œ ์ดˆ๊ณผ ๋ฐ ์‹œ์Šคํ…œ ํŒจ๋‹‰

์„ค์ • ํŒŒ์ผ์€ 5๋ถ„ ๋‹จ์œ„ ๊ฐฑ์‹ ํ•˜๋Š”๋ฐ, ๊ฐฑ์‹  ์ฟผ๋ฆฌ๋ฅผ ์‹คํ–‰ํ•˜๋Š” ๋…ธ๋“œ์— ๋”ฐ๋ผ ์ •์ƒ ํŒŒ์ผ๊ณผ ๋ถˆ๋Ÿ‰ ํŒŒ์ผ์ด ๋ฒˆ๊ฐˆ์•„ ์ƒ์„ฑ๋˜๋ฉด์„œ ์‹œ์Šคํ…œ์ด ํšŒ๋ณต๊ณผ ์žฅ์• ๋ฅผ ๋ฐ˜๋ณต (Flapping)ํ•˜์—ฌ ์›์ธ ํŒŒ์•…์— ํ˜ผ์„ ์„ ๊ฒช์—ˆ๋‹ค.

* blog.cloudflare.com/18-novembe

blog.cloudflare.com

Cloudflare outage on November 18, 2025

Cloudflare suffered a service outage on November 18, 2025. The outage was triggered by a bug in generation logic for a Bot Management feature file causing many Cloudflare services to be affected.

@faker@infosec.exchange

So the outage boils down to a bug in some Rust code.
That's why I recommend my customers to use battle proven memory safe languages instead.
Like Java and PHP.

@rolle@mementomori.social
@FoW@netsphere.one

2025๋…„ 11์›” 18์ผ ํด๋ผ์šฐ๋“œํ”Œ๋ ˆ์–ด

์š”์•ฝ: ์‚ฌ์ด๋ฒ„ ๊ณต๊ฒฉ์ด๋‚˜ DDoS ๊ณต๊ฒฉ์ด ์•„๋‹Œ ๋จธ์‹ ๋Ÿฌ๋‹ ๋ชจ๋ธ์˜ ๋‚ด๋ถ€ ์„ค์ • ์˜ค๋ฅ˜๊ฐ€ ์›์ธ.

1. ๋ฐ์ดํ„ฐ๋ฒ ์ด์Šค ๊ถŒํ•œ ๋ณ€๊ฒฝ
2. ์ฟผ๋ฆฌ ๊ฒฐ๊ณผ ์˜ค๋ฅ˜ (์ค‘๋ณต ๋ฐ์ดํ„ฐ)
3. ๋ฉ”๋ชจ๋ฆฌ ์ œํ•œ ์ดˆ๊ณผ ๋ฐ ์‹œ์Šคํ…œ ํŒจ๋‹‰

์„ค์ • ํŒŒ์ผ์€ 5๋ถ„ ๋‹จ์œ„ ๊ฐฑ์‹ ํ•˜๋Š”๋ฐ, ๊ฐฑ์‹  ์ฟผ๋ฆฌ๋ฅผ ์‹คํ–‰ํ•˜๋Š” ๋…ธ๋“œ์— ๋”ฐ๋ผ ์ •์ƒ ํŒŒ์ผ๊ณผ ๋ถˆ๋Ÿ‰ ํŒŒ์ผ์ด ๋ฒˆ๊ฐˆ์•„ ์ƒ์„ฑ๋˜๋ฉด์„œ ์‹œ์Šคํ…œ์ด ํšŒ๋ณต๊ณผ ์žฅ์• ๋ฅผ ๋ฐ˜๋ณต (Flapping)ํ•˜์—ฌ ์›์ธ ํŒŒ์•…์— ํ˜ผ์„ ์„ ๊ฒช์—ˆ๋‹ค.

* blog.cloudflare.com/18-novembe

blog.cloudflare.com

Cloudflare outage on November 18, 2025

Cloudflare suffered a service outage on November 18, 2025. The outage was triggered by a bug in generation logic for a Bot Management feature file causing many Cloudflare services to be affected.

@nullagent@partyon.xyz ยท Reply to nullagent

As I keep saying, Rust is a language with a ton of subtle but very important features.

But anyways... here's a 3 year old 24 page blog post on how to write "good" Rust and avoid the exact error CloudFlare hit.

It's written by a long time core contributor.

Reading this, its looks to me to be about as hard to write safe Rust code as almost -any- other type safe language. The learning curve however, is very real AND required.

burntsushi.net/unwrap/

blog.burntsushi.net

Using unwrap() in Rust is Okay - Andrew Gallant's Blog

I blog mostly about my own programming projects.

There's a fun " is hard" lesson here ().

1. Because Security, you want to be able to deploy global changes very quickly
2. Because Reliability, you want staged roll-outs that pause or even auto-revert if key metrics get worse

You can't have both 1 and 2 at the same time.

And the temptation to go fast sometimes WILL prove irresistible.

So if you're looking for ways to globally cripple a big cloud, this is the pattern to look for: what is too urgent for staged roll-outs?

The outage follows a pattern we have seen before. Was it Google last time?

1. Generate an exciting config file
2. Auto-deploy the file everywhere
3. Everything everywhere crashes

All these big systems want to be able to react quickly to certain types of events, so they probably all have this failure mode baked in. Because security! Or some such.

"Obviously" the files deployed this way "should" be validated carefully. And there "should" be canaries and staged roll-outs... Should.

@PavelASamsonov@mastodon.social

This is why the OpenBastard team needs to do more community outreach and not just commit more PRs

Better Things Are Possible
Once a month I wake up to a story like "Half the world doesn't work because of the NetBastard outage" I didn't even know about net bastard.
ALT text

Better Things Are Possible Once a month I wake up to a story like "Half the world doesn't work because of the NetBastard outage" I didn't even know about net bastard.

@digitalrechte@mastodon.social

Markus Beckedahl mit einem niederschmetterndem Resรผmee, live vom Gipfel zur Europรคischen Digitalen Souverรคnitรคt aus Berlin, der passenderweise garniert wurde vom Ausfall.
Bezeichnend fรผr die Abhรคngigkeit der von .

Vor Allem viel heiรŸe Luft, altbekannte Phrasen und keine konkreten Schritte

@markus_netzpolitik

Live vom Digitalgipfel
ALT text

Live vom Digitalgipfel

@occult@ominous.net

may be down, but the Japanese Maple in are fine. Go outside and visit your local tree.

Bright red autumn leaves on a tree with sunlight filtering through.
ALT text

Bright red autumn leaves on a tree with sunlight filtering through.

@keefmarshall@mastodon.online

If your usual music streaming service is down at the moment due to Cloudflare controlling half the internet, it would be a great time to try something alternative.

Why not check out:

The Indie Beat Radio:
theindiebeat.fm/

The Faircamp web ring:
faircamp.webr.ing/directory.ht

Everything Bonk Wave or Not Bonk Wave:
music.bonkwave.org/

.. and plenty more links over here:
nham.co.uk/category/community/

nham.co.uk

Distribution Platforms

Non Heralded Awesome Music

@fluepke@chaos.social

This outage is a good reminder, of how much unencrypted TLS traffic that company gets to see.

They have your private data from almost all of the websites, that are currently down.

"SSL added and removed here ;-)"

@koteisaev@mastodon.online ยท Reply to Kote Isaev

Spent 2 hours on looking for better Git UI/UX options as many sites shown in Kagi search results gone dark due that outage.
This whole situation is another example of how it is important for software to be local-first and if network function is unavoidable, it is important to keep it either available within LAN, or with an option to quickly spin an alternative instance (decentralized, federated?) or to make network part and use as less bigtech services/companies as possible. 2/2

@jessienab@wetdry.world
Meme image template
The Myth of the "MODERN" Web

Image of server with Linux penguin in the corner, saying "I connect!"
Image of cloud with text "ISP" overlaid, saying "I connect!"
Image of Cloudflare logo, saying "I DON'T!"

Text at bottom:
ISNT'T THERE SOMEBODY YOU FORGOT TO ACK?
ALT text

Meme image template The Myth of the "MODERN" Web Image of server with Linux penguin in the corner, saying "I connect!" Image of cloud with text "ISP" overlaid, saying "I connect!" Image of Cloudflare logo, saying "I DON'T!" Text at bottom: ISNT'T THERE SOMEBODY YOU FORGOT TO ACK?

@rubenwardy@hachyderm.io

The centralisation of internet infrastructure is concerning to me. Having 20% of the internet behind one CDN and 70% on US big tech cloud providers.... not good

Europe really needs to get tech independence from the US. We need multiple European cloud providers and a restriction on the use of AWS/GCP/Azure for government and public funded services

@sundogplanets@mastodon.social

Hilariously, I found out about the outage by trying to use a goat gestation calculator from the American Goat Society after breeding the first goat of the year this morning.

@forest_watch_impress@rss-mstdn.studiofreesia.com

ใ€ŒCloudflareใ€ใฎใ‚ฐใƒญใƒผใƒใƒซใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใซ้šœๅฎณ ๏ฝžGoogleใ€Xใ€AWSใ€OpenAIใชใฉๅฝฑ้Ÿฟๅคšๆ•ฐ๏ผๅบƒ็ฏ„ๅ›ฒใซใ‚ใŸใ‚Š500ใ‚จใƒฉใƒผใŒ็™บ็”Ÿใ€็พๅœจใ‚‚ๅพฉๆ—งไฝœๆฅญใŒ็ถ™็ถšไธญ
forest.watch.impress.co.jp/doc

forest.watch.impress.co.jp

ใ€ŒCloudflareใ€ใฎใ‚ฐใƒญใƒผใƒใƒซใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใซ้šœๅฎณ ๏ฝžGoogleใ€Xใ€AWSใ€OpenAIใชใฉๅฝฑ้Ÿฟๅคšๆ•ฐ๏ผๅบƒ็ฏ„ๅ›ฒใซใ‚ใŸใ‚Š500ใ‚จใƒฉใƒผใŒ็™บ็”Ÿใ€็พๅœจใ‚‚ๅพฉๆ—งไฝœๆฅญใŒ็ถ™็ถšไธญ

ใ€€Web้ซ˜้€ŸๅŒ–ใƒปใ‚ปใ‚ญใƒฅใƒชใƒ†ใ‚ฃๅผทๅŒ–ใ‚ตใƒผใƒ“ใ‚นใ€ŒCloudflareใ€ใฎใ‚ฐใƒญใƒผใƒใƒซใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใง11ๆœˆ18ๆ—ฅใฎ20ๆ™‚45ๅˆ†ใ”ใ‚ใ‹ใ‚‰้šœๅฎณใŒ็™บ็”Ÿใ—ใฆใ„ใ‚‹ใ€‚ใ€ŒCloudflareใ€ใ‚’ไฝฟ็”จใ—ใฆใ„ใ‚‹ใ‚ตใ‚คใƒˆใซใ‚ขใ‚ฏใ‚ปใ‚นใ™ใ‚‹ใจใ€Ž500ใ€ใ‚จใƒฉใƒผใŒ่กจ็คบใ•ใ‚Œใ‚‹ใปใ‹ใ€ใ€ŒCloudflareใ€ใฎใƒ€ใƒƒใ‚ทใƒฅใƒœใƒผใƒ‰ใจAPIใ‚‚ๆฉŸ่ƒฝใ—ใชใใชใฃใŸใ€‚

@koteisaev@mastodon.online ยท Reply to Kote Isaev

Spent 2 hours on looking for better Git UI/UX options as many sites shown in Kagi search results gone dark due that outage.
This whole situation is another example of how it is important for software to be local-first and if network function is unavoidable, it is important to keep it either available within LAN, or with an option to quickly spin an alternative instance (decentralized, federated?) or to make network part and use as less bigtech services/companies as possible. 2/2

@koteisaev@mastodon.online

Canceled my subscription for and uninstalled it due poor software design decisions which made app not ready to outage - during it GitKraken desktop GIT client unable to connect to a git service I use (not affected by ClownFlare issues).
I guess the problem was caused by the fact that the GitKraken is not a local-first application that was heavily dependent on API calls to a CloudFlare-affected backend.
1/2

@forest_watch_impress@rss-mstdn.studiofreesia.com

ใ€ŒCloudflareใ€ใฎใ‚ฐใƒญใƒผใƒใƒซใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใซ้šœๅฎณ ๏ฝžGoogleใ€Xใ€AWSใ€OpenAIใชใฉๅฝฑ้Ÿฟๅคšๆ•ฐ๏ผๅบƒ็ฏ„ๅ›ฒใซใ‚ใŸใ‚Š500ใ‚จใƒฉใƒผใŒ็™บ็”Ÿใ€็พๅœจใ‚‚ๅพฉๆ—งไฝœๆฅญใŒ็ถ™็ถšไธญ
forest.watch.impress.co.jp/doc

forest.watch.impress.co.jp

ใ€ŒCloudflareใ€ใฎใ‚ฐใƒญใƒผใƒใƒซใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใซ้šœๅฎณ ๏ฝžGoogleใ€Xใ€AWSใ€OpenAIใชใฉๅฝฑ้Ÿฟๅคšๆ•ฐ๏ผๅบƒ็ฏ„ๅ›ฒใซใ‚ใŸใ‚Š500ใ‚จใƒฉใƒผใŒ็™บ็”Ÿใ€็พๅœจใ‚‚ๅพฉๆ—งไฝœๆฅญใŒ็ถ™็ถšไธญ

ใ€€Web้ซ˜้€ŸๅŒ–ใƒปใ‚ปใ‚ญใƒฅใƒชใƒ†ใ‚ฃๅผทๅŒ–ใ‚ตใƒผใƒ“ใ‚นใ€ŒCloudflareใ€ใฎใ‚ฐใƒญใƒผใƒใƒซใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใง11ๆœˆ18ๆ—ฅใฎ20ๆ™‚45ๅˆ†ใ”ใ‚ใ‹ใ‚‰้šœๅฎณใŒ็™บ็”Ÿใ—ใฆใ„ใ‚‹ใ€‚ใ€ŒCloudflareใ€ใ‚’ไฝฟ็”จใ—ใฆใ„ใ‚‹ใ‚ตใ‚คใƒˆใซใ‚ขใ‚ฏใ‚ปใ‚นใ™ใ‚‹ใจใ€Ž500ใ€ใ‚จใƒฉใƒผใŒ่กจ็คบใ•ใ‚Œใ‚‹ใปใ‹ใ€ใ€ŒCloudflareใ€ใฎใƒ€ใƒƒใ‚ทใƒฅใƒœใƒผใƒ‰ใจAPIใ‚‚ๆฉŸ่ƒฝใ—ใชใใชใฃใŸใ€‚

@delta@chaos.social

While US-east1 is busy fixing a good part of the Internet, parts of Matrix/Element, X etc down, good old decentralized continues unimpeded and without degradation :)

In other news, there is a new community maintained โค๏ธ desktop install:

pkg install deltachat-desktop

thanks @feld and others!

@teufelswerk@social.tchncs.de

Wer Cloudflare nutzt, leitet seinen gesamten Webverkehr durch die Infrastruktur eines einzelnen, zentralisierten Anbieters. Damit gibt man nicht nur technische Kontrolle ab, sondern auch Zugriff auf sensible Metadaten und ggf. auch auf Nutzerdaten. In diesem Artikel erfรคhrst du, wie du Cloudflare durch offene, selbst gehostete Lรถsungen ersetzen kannst. ๐Ÿ‘‡

teufelswerk.net/open-source-al

teufelswerk.net

Open-Source-Alternativen zu Cloudflare: Datenschutz, Sicherheit & digitale Souverรคnitรคt

Cloudflare ist heute einer der mรคchtigsten Infrastrukturbetreiber des Internets. Millionen Websites โ€“ von kleinen Blogs รผber E-Commerce-Plattformen bis zu

@fluepke@chaos.social

This outage is a good reminder, of how much unencrypted TLS traffic that company gets to see.

They have your private data from almost all of the websites, that are currently down.

"SSL added and removed here ;-)"

@jessienab@wetdry.world
Meme image template
The Myth of the "MODERN" Web

Image of server with Linux penguin in the corner, saying "I connect!"
Image of cloud with text "ISP" overlaid, saying "I connect!"
Image of Cloudflare logo, saying "I DON'T!"

Text at bottom:
ISNT'T THERE SOMEBODY YOU FORGOT TO ACK?
ALT text

Meme image template The Myth of the "MODERN" Web Image of server with Linux penguin in the corner, saying "I connect!" Image of cloud with text "ISP" overlaid, saying "I connect!" Image of Cloudflare logo, saying "I DON'T!" Text at bottom: ISNT'T THERE SOMEBODY YOU FORGOT TO ACK?

@digitalrechte@mastodon.social

Markus Beckedahl mit einem niederschmetterndem Resรผmee, live vom Gipfel zur Europรคischen Digitalen Souverรคnitรคt aus Berlin, der passenderweise garniert wurde vom Ausfall.
Bezeichnend fรผr die Abhรคngigkeit der von .

Vor Allem viel heiรŸe Luft, altbekannte Phrasen und keine konkreten Schritte

@markus_netzpolitik

Live vom Digitalgipfel
ALT text

Live vom Digitalgipfel

@oageo@c.osumiakari.jp

Cloudflareใ€ใชใ‚“ใ‹ๅพฉๆดปใ—ใŸใฃใฝใ„ใฟใŸใ„ใชใ“ใจใ‚’่จ€ใฃใฆใ„ใ‚‹

@0xabad1dea@infosec.exchange

it's not a proper outage until the status page is rendering without CSS (it's not a flawless 10/10 outage until the status page is in a DNS black hole)

screenshot of cloudflare status page with tiny text in browser-default styling and a massively oversized logo
ALT text

screenshot of cloudflare status page with tiny text in browser-default styling and a massively oversized logo

@jessienab@wetdry.world
Meme image template
The Myth of the "MODERN" Web

Image of server with Linux penguin in the corner, saying "I connect!"
Image of cloud with text "ISP" overlaid, saying "I connect!"
Image of Cloudflare logo, saying "I DON'T!"

Text at bottom:
ISNT'T THERE SOMEBODY YOU FORGOT TO ACK?
ALT text

Meme image template The Myth of the "MODERN" Web Image of server with Linux penguin in the corner, saying "I connect!" Image of cloud with text "ISP" overlaid, saying "I connect!" Image of Cloudflare logo, saying "I DON'T!" Text at bottom: ISNT'T THERE SOMEBODY YOU FORGOT TO ACK?

@rubenwardy@hachyderm.io

The centralisation of internet infrastructure is concerning to me. Having 20% of the internet behind one CDN and 70% on US big tech cloud providers.... not good

Europe really needs to get tech independence from the US. We need multiple European cloud providers and a restriction on the use of AWS/GCP/Azure for government and public funded services

@keefmarshall@mastodon.online

If your usual music streaming service is down at the moment due to Cloudflare controlling half the internet, it would be a great time to try something alternative.

Why not check out:

The Indie Beat Radio:
theindiebeat.fm/

The Faircamp web ring:
faircamp.webr.ing/directory.ht

Everything Bonk Wave or Not Bonk Wave:
music.bonkwave.org/

.. and plenty more links over here:
nham.co.uk/category/community/

nham.co.uk

Distribution Platforms

Non Heralded Awesome Music

@sundogplanets@mastodon.social

Hilariously, I found out about the outage by trying to use a goat gestation calculator from the American Goat Society after breeding the first goat of the year this morning.

@forest_watch_impress@rss-mstdn.studiofreesia.com

ใ€ŒCloudflareใ€ใฎใ‚ฐใƒญใƒผใƒใƒซใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใซ้šœๅฎณ ๏ฝžGoogleใ€Xใ€AWSใ€OpenAIใชใฉๅฝฑ้Ÿฟๅคšๆ•ฐ๏ผๅบƒ็ฏ„ๅ›ฒใซใ‚ใŸใ‚Š500ใ‚จใƒฉใƒผใŒ็™บ็”Ÿใ€็พๅœจใ‚‚ๅพฉๆ—งไฝœๆฅญใŒ็ถ™็ถšไธญ
forest.watch.impress.co.jp/doc

forest.watch.impress.co.jp

ใ€ŒCloudflareใ€ใฎใ‚ฐใƒญใƒผใƒใƒซใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใซ้šœๅฎณ ๏ฝžGoogleใ€Xใ€AWSใ€OpenAIใชใฉๅฝฑ้Ÿฟๅคšๆ•ฐ๏ผๅบƒ็ฏ„ๅ›ฒใซใ‚ใŸใ‚Š500ใ‚จใƒฉใƒผใŒ็™บ็”Ÿใ€็พๅœจใ‚‚ๅพฉๆ—งไฝœๆฅญใŒ็ถ™็ถšไธญ

ใ€€Web้ซ˜้€ŸๅŒ–ใƒปใ‚ปใ‚ญใƒฅใƒชใƒ†ใ‚ฃๅผทๅŒ–ใ‚ตใƒผใƒ“ใ‚นใ€ŒCloudflareใ€ใฎใ‚ฐใƒญใƒผใƒใƒซใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใง11ๆœˆ18ๆ—ฅใฎ20ๆ™‚45ๅˆ†ใ”ใ‚ใ‹ใ‚‰้šœๅฎณใŒ็™บ็”Ÿใ—ใฆใ„ใ‚‹ใ€‚ใ€ŒCloudflareใ€ใ‚’ไฝฟ็”จใ—ใฆใ„ใ‚‹ใ‚ตใ‚คใƒˆใซใ‚ขใ‚ฏใ‚ปใ‚นใ™ใ‚‹ใจใ€Ž500ใ€ใ‚จใƒฉใƒผใŒ่กจ็คบใ•ใ‚Œใ‚‹ใปใ‹ใ€ใ€ŒCloudflareใ€ใฎใƒ€ใƒƒใ‚ทใƒฅใƒœใƒผใƒ‰ใจAPIใ‚‚ๆฉŸ่ƒฝใ—ใชใใชใฃใŸใ€‚

@fluepke@chaos.social

This outage is a good reminder, of how much unencrypted TLS traffic that company gets to see.

They have your private data from almost all of the websites, that are currently down.

"SSL added and removed here ;-)"

@derPUPE@chaos.social

hustet und das
ganze steht still ...

das ganze Intenet?

Nope: in unserem auf unserem dezentralen Servern wird gerade extra fรผr den & das das "Quod erat demonstrandum" bewiesen

โ€ขperfektesโ€ขtimingโ€ข

A humorous image featuring a man turning his head to look at another woman while ignoring his girlfriend, with text overlay commenting on digital topics and trends. The scene captures feelings of distraction and comparison in a lighthearted way.
ALT text

A humorous image featuring a man turning his head to look at another woman while ignoring his girlfriend, with text overlay commenting on digital topics and trends. The scene captures feelings of distraction and comparison in a lighthearted way.

@electric_gumball@mastodon.social

Seriously, who would have thought that having almost everything rely on just one company would ever be a problem?

@box464@mastodon.social

Searching programminghumor.io for Cloudflare memes and this is what I got. Classic.

The image displays an internal server error message (Error code 500) from Cloudflare. It shows a connection status with icons indicating "You," "Cloudflare," and "Host," along with an explanation of the error and a suggestion to try again later. The background is light, and the text is clearly displayed.
ALT text

The image displays an internal server error message (Error code 500) from Cloudflare. It shows a connection status with icons indicating "You," "Cloudflare," and "Host," along with an explanation of the error and a suggestion to try again later. The background is light, and the text is clearly displayed.

@dansup
Don't know if the issue has been figured out yet. But they seem aware.

cloudflarestatus.com/

Screenshot fron CloudFlare status site. Reads, "
Cloudflare System Status
Cloudflare Global Network experiencing issues
Update - We are continuing to investigate this issue.
Nov 18, 2025 - 12:37 UTC
Update - We are seeing services recover, but customers may continue to observe higher-than-normal error rates as we continue remediation efforts.
Nov 18, 2025 - 12:21 UTC
Update - We are continuing to investigate this issue.
Nov 18, 2025 - 12:03 UTC
Investigating - Cloudflare is experiencing an internal service degradation. Some services may be intermittently impacted. We are focused on restoring service. We will update as we are able to remediate. More updates to follow shortly.
Nov 18, 2025 - 11:48 UTC"
ALT text

Screenshot fron CloudFlare status site. Reads, " Cloudflare System Status Cloudflare Global Network experiencing issues Update - We are continuing to investigate this issue. Nov 18, 2025 - 12:37 UTC Update - We are seeing services recover, but customers may continue to observe higher-than-normal error rates as we continue remediation efforts. Nov 18, 2025 - 12:21 UTC Update - We are continuing to investigate this issue. Nov 18, 2025 - 12:03 UTC Investigating - Cloudflare is experiencing an internal service degradation. Some services may be intermittently impacted. We are focused on restoring service. We will update as we are able to remediate. More updates to follow shortly. Nov 18, 2025 - 11:48 UTC"

@Tutanota@mastodon.social

is down taking half the web offline. Don't put all your eggs in one basket!

mastodon.social

Tuta (@Tutanota@mastodon.social)

Attached: 1 image DeApple, DeMicrosoft, DeGoogle, ... DIVERSIFY

@Tutanota@mastodon.social

DeApple, DeMicrosoft, DeGoogle, ... DIVERSIFY

Image with logos from Apple, Microsoft and Google for all kinds of products and alternatives for diversification: NextCloud, Tuta Mail, Tuta Calendar, Notesnook, Tasks, CryptPad, Mistral
ALT text

Image with logos from Apple, Microsoft and Google for all kinds of products and alternatives for diversification: NextCloud, Tuta Mail, Tuta Calendar, Notesnook, Tasks, CryptPad, Mistral

@delta@chaos.social

While US-east1 is busy fixing a good part of the Internet, parts of Matrix/Element, X etc down, good old decentralized continues unimpeded and without degradation :)

In other news, there is a new community maintained โค๏ธ desktop install:

pkg install deltachat-desktop

thanks @feld and others!

@trending@mastodon.bot
@wild1145@mastodonapp.uk

I've disabled the proxy for (Thankfully their API still seems to work and I've been able to bodge it into working) so traffic should now be routing directly to our load balancer infrastructure which I hope will mean we should now be able to be online. This may mean the site will be slower for folks geographically further from the UK but it's either this or the site is intermittently down.

I'll get the change rolled out on and the Universeodon relay now.

@metin@graphics.social
@Tutanota@mastodon.social

is down taking half the web offline. Don't put all your eggs in one basket!

mastodon.social

Tuta (@Tutanota@mastodon.social)

Attached: 1 image DeApple, DeMicrosoft, DeGoogle, ... DIVERSIFY

@Tutanota@mastodon.social

DeApple, DeMicrosoft, DeGoogle, ... DIVERSIFY

Image with logos from Apple, Microsoft and Google for all kinds of products and alternatives for diversification: NextCloud, Tuta Mail, Tuta Calendar, Notesnook, Tasks, CryptPad, Mistral
ALT text

Image with logos from Apple, Microsoft and Google for all kinds of products and alternatives for diversification: NextCloud, Tuta Mail, Tuta Calendar, Notesnook, Tasks, CryptPad, Mistral

@metin@graphics.social
@0xabad1dea@infosec.exchange

it's not a proper outage until the status page is rendering without CSS (it's not a flawless 10/10 outage until the status page is in a DNS black hole)

screenshot of cloudflare status page with tiny text in browser-default styling and a massively oversized logo
ALT text

screenshot of cloudflare status page with tiny text in browser-default styling and a massively oversized logo

@team@manitu.social

Ah, heute funktioniert dann mal ein anderes Drittel des Internets nicht.

Sagten wir schon, wie toll echte Dezentralitรคt ist?

Cloudflare System Status
Cloudflare Global Network experiencing issues
Investigating - Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers. Further detail will be provided as more information becomes available.
ALT text

Cloudflare System Status Cloudflare Global Network experiencing issues Investigating - Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers. Further detail will be provided as more information becomes available.

@gomasy@don.gomasy.jp
@teufelswerk@social.tchncs.de

Wer Cloudflare nutzt, leitet seinen gesamten Webverkehr durch die Infrastruktur eines einzelnen, zentralisierten Anbieters. Damit gibt man nicht nur technische Kontrolle ab, sondern auch Zugriff auf sensible Metadaten und ggf. auch auf Nutzerdaten. In diesem Artikel erfรคhrst du, wie du Cloudflare durch offene, selbst gehostete Lรถsungen ersetzen kannst. ๐Ÿ‘‡

teufelswerk.net/open-source-al

teufelswerk.net

Open-Source-Alternativen zu Cloudflare: Datenschutz, Sicherheit & digitale Souverรคnitรคt

Cloudflare ist heute einer der mรคchtigsten Infrastrukturbetreiber des Internets. Millionen Websites โ€“ von kleinen Blogs รผber E-Commerce-Plattformen bis zu

@teufelswerk@social.tchncs.de

Wer Cloudflare nutzt, leitet seinen gesamten Webverkehr durch die Infrastruktur eines einzelnen, zentralisierten Anbieters. Damit gibt man nicht nur technische Kontrolle ab, sondern auch Zugriff auf sensible Metadaten und ggf. auch auf Nutzerdaten. In diesem Artikel erfรคhrst du, wie du Cloudflare durch offene, selbst gehostete Lรถsungen ersetzen kannst. ๐Ÿ‘‡

teufelswerk.net/open-source-al

teufelswerk.net

Open-Source-Alternativen zu Cloudflare: Datenschutz, Sicherheit & digitale Souverรคnitรคt

Cloudflare ist heute einer der mรคchtigsten Infrastrukturbetreiber des Internets. Millionen Websites โ€“ von kleinen Blogs รผber E-Commerce-Plattformen bis zu

@back2theRoot@chaos.social

Nazis daten, dealen und planen Nachwuchs... und Big Tech hostet mit.
WhiteDate, WhiteDeal & WhiteChild sind weiter online, obwohl sie gegen EU-Gesetze zu Hassrede & Diskriminierung verstoรŸen.

โ€“ schaut da bitte nochmal rein.

Kein Internet fรผr Rassist:innen.
๐Ÿ‘‰ okstupid.lol

... Big Tech halt das Kissen
Am 8. Oktober wurden in ZEIT, WOZ und weiteren Medien
Recherchen iiber WhiteDate, WhiteDeal und WhiteChild
verGffentlicht.
Kurz gesagt - Das sind keine "normalen" Seiten:
WhiteDate ist quasi Tinder fiir Nazis,
WhiteChild funktioniert wie eine
Samentauschbo6rse zum Erhalt der weiflen Rasse
und WhiteDeal ist eine Art Fiverr fiir Rassist:innen...
BE

Aber wieso sind diese Seiten noch online, wer betreibt diese Seiten und wo

werden sie gehostet?
ALT text

... Big Tech halt das Kissen Am 8. Oktober wurden in ZEIT, WOZ und weiteren Medien Recherchen iiber WhiteDate, WhiteDeal und WhiteChild verGffentlicht. Kurz gesagt - Das sind keine "normalen" Seiten: WhiteDate ist quasi Tinder fiir Nazis, WhiteChild funktioniert wie eine Samentauschbo6rse zum Erhalt der weiflen Rasse und WhiteDeal ist eine Art Fiverr fiir Rassist:innen... BE Aber wieso sind diese Seiten noch online, wer betreibt diese Seiten und wo werden sie gehostet?

Hinter dem Netzwerk steckt Christiane H., online bekannt als โ€žLiv Heideโ€œ. Sie ist national und international vernetzt, unter anderem mit der US-Plattform American Renaissance, dem White Nationalist und Anwalt William Daniel Johnson sowie der rechten deutschen Gruppierung Ludendorffer, die Wurzeln in der Nazi-Ideologie hat. AuรŸerdem pflegt sie Kontakte zu Corona-Schwurblern und dem Nazigitarristen Frank Kraemer.

Christiane H. glaubt an den White Genocide, verbreitet antisemitische Verschwรถrungstheorien und andere rassistische Ideologien. Kurz gesagt: Hier wird nicht nur online gedatet โ€“ hier wird ein richtiges rechtsradikales Netzwerk aufgebaut.

Aber wer hostet das Ganze eigentlich?
ALT text

Hinter dem Netzwerk steckt Christiane H., online bekannt als โ€žLiv Heideโ€œ. Sie ist national und international vernetzt, unter anderem mit der US-Plattform American Renaissance, dem White Nationalist und Anwalt William Daniel Johnson sowie der rechten deutschen Gruppierung Ludendorffer, die Wurzeln in der Nazi-Ideologie hat. AuรŸerdem pflegt sie Kontakte zu Corona-Schwurblern und dem Nazigitarristen Frank Kraemer. Christiane H. glaubt an den White Genocide, verbreitet antisemitische Verschwรถrungstheorien und andere rassistische Ideologien. Kurz gesagt: Hier wird nicht nur online gedatet โ€“ hier wird ein richtiges rechtsradikales Netzwerk aufgebaut. Aber wer hostet das Ganze eigentlich?

Big Tech, schaut mal hin!

Die Plattformen sind noch online โ€“ trotz all dem Hass und der rassistischen Ideologie. Wer sorgt dafรผr?

Cloudflare schรผtzt WhiteDate

Hetzner hostet WhiteDeal & WhiteChild

Hostinger hostet ebenfalls WhiteDeal & WhiteChild

Damit werden Inhalte ermรถglicht, die gegen europรคisches Recht verstoรŸen kรถnnten, z.โ€ฏB.:

Hassrede und Diskriminierung (ยง130 StGB)

Aufruf zu Gewalt gegen Gruppen

Verbreitung antisemitischer oder rassistischer Propaganda

Wenn ihr Lust habt, zeigt den Betreiber:innen, dass wir das sehen โ€“ im ersten Kommentar findet ihr ein fertiges Template, um sie direkt anzuschreiben
ALT text

Big Tech, schaut mal hin! Die Plattformen sind noch online โ€“ trotz all dem Hass und der rassistischen Ideologie. Wer sorgt dafรผr? Cloudflare schรผtzt WhiteDate Hetzner hostet WhiteDeal & WhiteChild Hostinger hostet ebenfalls WhiteDeal & WhiteChild Damit werden Inhalte ermรถglicht, die gegen europรคisches Recht verstoรŸen kรถnnten, z.โ€ฏB.: Hassrede und Diskriminierung (ยง130 StGB) Aufruf zu Gewalt gegen Gruppen Verbreitung antisemitischer oder rassistischer Propaganda Wenn ihr Lust habt, zeigt den Betreiber:innen, dass wir das sehen โ€“ im ersten Kommentar findet ihr ein fertiges Template, um sie direkt anzuschreiben

@zeab@fosstodon.org
@a40yostudent@iosdev.space ยท Reply to Danielle Forรฉ
@mjg@mastodon.phoenixtrap.com
@cory@follow.coryd.dev
@mjg@mastodon.phoenixtrap.com
@mjg@mastodon.phoenixtrap.com
@mjg@mastodon.phoenixtrap.com
@nodebb@fosstodon.org

It seems that community.nodebb.org is under a DDoS attack at the moment. We have enabled CloudFlare's "under attack" mode which has stopped the attack but it also has the unfortunate side effect of blocking all incoming ActivityPub traffic as well.

Interesting side effect. Will continue to monitor.

@elblogdelazaro@mastodon.social

Pues por utilizar el proxy de para proteger elblogdelazaro.org, me acaba de amenazar con denunciarme por omisiรณn de denunciar a por permitir que se utilicen sus servicios para piratear su futbol, lo que me faltaba por ver ya, esto esta tomando un cariz mafiosos que apesta.

Captura 1/2 del correo enviado por #laliga amenazando con denunciarme por no denunciar a #cloudflare
ALT text

Captura 1/2 del correo enviado por #laliga amenazando con denunciarme por no denunciar a #cloudflare

Captura 2/2 del correo enviado por #laliga amenazando con denunciarme por no denunciar a #cloudflare
ALT text

Captura 2/2 del correo enviado por #laliga amenazando con denunciarme por no denunciar a #cloudflare

@beitmenotyou@social.beitmenotyou.online

Taking Back Control: My Journey into Self-Hosting with Raspberry Pi
I am using Raspberry Pi 4 and 5 to self-host my blog, social media, and cloud storage. Here is why digital sovereignty matters, and how you can start your own self-hosti
https://beitmenotyou.online/taking-back-control-my-journey-into-self-hosting-with-raspberry-pi/
#SelfHosting #ActivityPub #Blogging #Cloudflare #Decentralisation #DigitalSovereignty #Docker #Nextcloud #RaspberryPi #SelfHosting #Web3 #WordPress

@beitmenotyou@social.beitmenotyou.online

Taking Back Control: My Journey into Self-Hosting with Raspberry Pi
I am using Raspberry Pi 4 and 5 to self-host my blog, social media, and cloud storage. Here is why digital sovereignty matters, and how you can start your own self-hosti
https://beitmenotyou.online/taking-back-control-my-journey-into-self-hosting-with-raspberry-pi/
#SelfHosting #ActivityPub #Blogging #Cloudflare #Decentralisation #DigitalSovereignty #Docker #Nextcloud #RaspberryPi #SelfHosting #Web3 #WordPress

@beitmenotyou@social.beitmenotyou.online

Taking Back Control: My Journey into Self-Hosting with Raspberry Pi
I am using Raspberry Pi 4 and 5 to self-host my blog, social media, and cloud storage. Here is why digital sovereignty matters, and how you can start your own self-hosti
https://beitmenotyou.online/taking-back-control-my-journey-into-self-hosting-with-raspberry-pi/
#SelfHosting #ActivityPub #Blogging #Cloudflare #Decentralisation #DigitalSovereignty #Docker #Nextcloud #RaspberryPi #SelfHosting #Web3 #WordPress

@elblogdelazaro@mastodon.social

Pues por utilizar el proxy de para proteger elblogdelazaro.org, me acaba de amenazar con denunciarme por omisiรณn de denunciar a por permitir que se utilicen sus servicios para piratear su futbol, lo que me faltaba por ver ya, esto esta tomando un cariz mafiosos que apesta.

Captura 1/2 del correo enviado por #laliga amenazando con denunciarme por no denunciar a #cloudflare
ALT text

Captura 1/2 del correo enviado por #laliga amenazando con denunciarme por no denunciar a #cloudflare

Captura 2/2 del correo enviado por #laliga amenazando con denunciarme por no denunciar a #cloudflare
ALT text

Captura 2/2 del correo enviado por #laliga amenazando con denunciarme por no denunciar a #cloudflare

@nibushibu@vivaldi.net

ใฎใƒ€ใƒƒใ‚ทใƒฅใƒœใƒผใƒ‰ใฎใƒฌใ‚นใƒใƒณใ‚นใŒ่‘—ใ—ใ้…ใ„ๆฐ—ใŒใ™ใ‚‹ใ‘ใฉใชใซใ‹ใฎ้šœๅฎณใ‹ใช

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

@symptomdelivery@app.wafrn.net ยท Reply to Cursed Silicon

okay, i made one ^^


#cloudflare #clownflare
the cloudflare logo (a flat orange cloud-the right fifth of the cloud is a lighter orange, and the two colors are separated by a white gleam) but its rotated a bit to be hair for a clown face (with purple mouth makeup, purple nose, and purple eye makeup). theres bold impact font CLOUDFLARE beneath the clown, but the UD has been replaced with WN in a comic sans style font so it says CLOWNFLARE
ALT text

the cloudflare logo (a flat orange cloud-the right fifth of the cloud is a lighter orange, and the two colors are separated by a white gleam) but its rotated a bit to be hair for a clown face (with purple mouth makeup, purple nose, and purple eye makeup). theres bold impact font CLOUDFLARE beneath the clown, but the UD has been replaced with WN in a comic sans style font so it says CLOWNFLARE

@symptomdelivery@app.wafrn.net

i made a thing (context: https://app.wafrn.net/fediverse/post/425f5ff1-3eee-4ddc-afe2-3e6af598e397)

i'm thinking about having it made into stickers

(posting this again so it federates correctly lol)


#cloudflare
the cloudflare logo (a flat orange cloud-the right fifth of the cloud is a lighter orange, and the two colors are separated by a white gleam) but its rotated a bit to be hair for a clown face (with purple mouth makeup, purple nose, and purple eye makeup). theres bold impact font CLOUDFLARE beneath the clown, but the UD has been replaced with WN in a comic sans style font so it says CLOWNFLARE
ALT text

the cloudflare logo (a flat orange cloud-the right fifth of the cloud is a lighter orange, and the two colors are separated by a white gleam) but its rotated a bit to be hair for a clown face (with purple mouth makeup, purple nose, and purple eye makeup). theres bold impact font CLOUDFLARE beneath the clown, but the UD has been replaced with WN in a comic sans style font so it says CLOWNFLARE

@symptomdelivery@app.wafrn.net

i made a thing (context: https://app.wafrn.net/fediverse/post/425f5ff1-3eee-4ddc-afe2-3e6af598e397)

i'm thinking about having it made into stickers

(posting this again so it federates correctly lol)


#cloudflare
the cloudflare logo (a flat orange cloud-the right fifth of the cloud is a lighter orange, and the two colors are separated by a white gleam) but its rotated a bit to be hair for a clown face (with purple mouth makeup, purple nose, and purple eye makeup). theres bold impact font CLOUDFLARE beneath the clown, but the UD has been replaced with WN in a comic sans style font so it says CLOWNFLARE
ALT text

the cloudflare logo (a flat orange cloud-the right fifth of the cloud is a lighter orange, and the two colors are separated by a white gleam) but its rotated a bit to be hair for a clown face (with purple mouth makeup, purple nose, and purple eye makeup). theres bold impact font CLOUDFLARE beneath the clown, but the UD has been replaced with WN in a comic sans style font so it says CLOWNFLARE

@symptomdelivery@app.wafrn.net ยท Reply to Cursed Silicon

okay, i made one ^^


#cloudflare #clownflare
the cloudflare logo (a flat orange cloud-the right fifth of the cloud is a lighter orange, and the two colors are separated by a white gleam) but its rotated a bit to be hair for a clown face (with purple mouth makeup, purple nose, and purple eye makeup). theres bold impact font CLOUDFLARE beneath the clown, but the UD has been replaced with WN in a comic sans style font so it says CLOWNFLARE
ALT text

the cloudflare logo (a flat orange cloud-the right fifth of the cloud is a lighter orange, and the two colors are separated by a white gleam) but its rotated a bit to be hair for a clown face (with purple mouth makeup, purple nose, and purple eye makeup). theres bold impact font CLOUDFLARE beneath the clown, but the UD has been replaced with WN in a comic sans style font so it says CLOWNFLARE

@markwyner@mas.to

Anyone else seeing these Cloudflare gatekeeper screens everywhere? Anyone else remember when the internet wasnโ€™t mostly โ€œaccept my cookies,โ€ โ€œprove youโ€™re a human,โ€ and โ€œsign up for my newsletterโ€?

Screenshot of a website gate that reads โ€œone with nature dot com. Verify you are human by completing the action below.โ€There is a checkbox with the label โ€œverify you are human.โ€Then more copy that reads โ€œone with nature dot com needs to review the security of your connection before proceeding.โ€
ALT text

Screenshot of a website gate that reads โ€œone with nature dot com. Verify you are human by completing the action below.โ€There is a checkbox with the label โ€œverify you are human.โ€Then more copy that reads โ€œone with nature dot com needs to review the security of your connection before proceeding.โ€

@markwyner@mas.to

Anyone else seeing these Cloudflare gatekeeper screens everywhere? Anyone else remember when the internet wasnโ€™t mostly โ€œaccept my cookies,โ€ โ€œprove youโ€™re a human,โ€ and โ€œsign up for my newsletterโ€?

Screenshot of a website gate that reads โ€œone with nature dot com. Verify you are human by completing the action below.โ€There is a checkbox with the label โ€œverify you are human.โ€Then more copy that reads โ€œone with nature dot com needs to review the security of your connection before proceeding.โ€
ALT text

Screenshot of a website gate that reads โ€œone with nature dot com. Verify you are human by completing the action below.โ€There is a checkbox with the label โ€œverify you are human.โ€Then more copy that reads โ€œone with nature dot com needs to review the security of your connection before proceeding.โ€

@brewsterkahle@mastodon.archive.org

Moment of Gratitude: CloudFlare

CloudFlare saved the Internet Archive servers from DDOS attack yesterday

The max rate of this DDOS attack was 525 Gbps (44.93 Mpps) of a "TCP flood."

The Internet Archive does not have enough bandwidth to fend off that kind of attack.

Thank you or we would have had a very bad Saturday at the @internetarchive

DDOS attacks are coming more frequently.

@brewsterkahle@mastodon.archive.org

Moment of Gratitude: CloudFlare

CloudFlare saved the Internet Archive servers from DDOS attack yesterday

The max rate of this DDOS attack was 525 Gbps (44.93 Mpps) of a "TCP flood."

The Internet Archive does not have enough bandwidth to fend off that kind of attack.

Thank you or we would have had a very bad Saturday at the @internetarchive

DDOS attacks are coming more frequently.

@brewsterkahle@mastodon.archive.org

Moment of Gratitude: CloudFlare

CloudFlare saved the Internet Archive servers from DDOS attack yesterday

The max rate of this DDOS attack was 525 Gbps (44.93 Mpps) of a "TCP flood."

The Internet Archive does not have enough bandwidth to fend off that kind of attack.

Thank you or we would have had a very bad Saturday at the @internetarchive

DDOS attacks are coming more frequently.

@brewsterkahle@mastodon.archive.org

Moment of Gratitude: CloudFlare

CloudFlare saved the Internet Archive servers from DDOS attack yesterday

The max rate of this DDOS attack was 525 Gbps (44.93 Mpps) of a "TCP flood."

The Internet Archive does not have enough bandwidth to fend off that kind of attack.

Thank you or we would have had a very bad Saturday at the @internetarchive

DDOS attacks are coming more frequently.

@dada@diaspodon.fr
@dada@diaspodon.fr

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

๐ŸŒ Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

๐Ÿ—๏ธ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

๐Ÿ” HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselvesโ€”making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

๐Ÿ” WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

๐Ÿ›  Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

๐Ÿš€ Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

๐ŸŽฏ Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

discord.com

Join the Fedify/Hollo Discord Server!

Check out the Fedify/Hollo community on Discord - hang out with 95 other members and enjoy free voice and text chat.

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! ๐Ÿš€

๐ŸŽ‰ support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, can now run on Cloudflare Workers.

What's included:

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

npmjs.com

@fedify/fedify

An ActivityPub server framework. Latest version: 1.5.3, last published: 16 days ago. Start using @fedify/fedify in your project by running `npm i @fedify/fedify`. There are 3 other projects in the npm registry using @fedify/fedify.

๐ŸŽ‰ support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, can now run on Cloudflare Workers.

What's included:

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

npmjs.com

@fedify/fedify

An ActivityPub server framework. Latest version: 1.5.3, last published: 16 days ago. Start using @fedify/fedify in your project by running `npm i @fedify/fedify`. There are 3 other projects in the npm registry using @fedify/fedify.

๐ŸŽ‰ support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, can now run on Cloudflare Workers.

What's included:

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

npmjs.com

@fedify/fedify

An ActivityPub server framework. Latest version: 1.5.3, last published: 16 days ago. Start using @fedify/fedify in your project by running `npm i @fedify/fedify`. There are 3 other projects in the npm registry using @fedify/fedify.

๐ŸŽ‰ support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, can now run on Cloudflare Workers.

What's included:

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

npmjs.com

@fedify/fedify

An ActivityPub server framework. Latest version: 1.5.3, last published: 16 days ago. Start using @fedify/fedify in your project by running `npm i @fedify/fedify`. There are 3 other projects in the npm registry using @fedify/fedify.

๐ŸŽ‰ support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, can now run on Cloudflare Workers.

What's included:

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

npmjs.com

@fedify/fedify

An ActivityPub server framework. Latest version: 1.5.3, last published: 16 days ago. Start using @fedify/fedify in your project by running `npm i @fedify/fedify`. There are 3 other projects in the npm registry using @fedify/fedify.

๐ŸŽ‰ support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, can now run on Cloudflare Workers.

What's included:

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

npmjs.com

@fedify/fedify

An ActivityPub server framework. Latest version: 1.5.3, last published: 16 days ago. Start using @fedify/fedify in your project by running `npm i @fedify/fedify`. There are 3 other projects in the npm registry using @fedify/fedify.

๐ŸŽ‰ support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, can now run on Cloudflare Workers.

What's included:

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

npmjs.com

@fedify/fedify

An ActivityPub server framework. Latest version: 1.5.3, last published: 16 days ago. Start using @fedify/fedify in your project by running `npm i @fedify/fedify`. There are 3 other projects in the npm registry using @fedify/fedify.

๐ŸŽ‰ support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, can now run on Cloudflare Workers.

What's included:

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

npmjs.com

@fedify/fedify

An ActivityPub server framework. Latest version: 1.5.3, last published: 16 days ago. Start using @fedify/fedify in your project by running `npm i @fedify/fedify`. There are 3 other projects in the npm registry using @fedify/fedify.

Tunnel... ํ™•์‹คํžˆ ํฌํŠธ, ์ธ์ฆ์„œ์™€ ๋ฐฉํ™”๋ฒฝ์„ ๊ด€๋ฆฌํ•˜๋Š” ์ˆ˜๊ณ ์™€๋Š” ๋น„๊ตํ•  ์ˆ˜ ์—†์„ ์ •๋„๋กœ ํŽธ๋ฆฌํ•˜๋‹ค. ๋˜, ์ง€์‹์ด ์ถฉ๋ถ„์น˜ ์•Š์€ ๋‚˜๊ฐ™์€ ์‚ฌ๋žŒ๋„ ์›น ์„œ๋น„์Šค๋ฅผ ์•ˆ์ „ํ•˜๊ฒŒ ์šด์˜ํ•˜๋„๋ก ๋•๋Š”๋‹ค๋Š” ์ ์—์„œ ์„ ๋„์ ์ด๋‹ค. ๋”๊ตฌ๋‚˜ ์—”๋“œํฌ์ธํŠธ์—์„œ ์ƒ์œ„ ๋…ธ๋“œ๋กœ ํ„ฐ๋„์„ ์—ด์–ด ์„œ๋น„์Šค๋ฅผ ๊ฐ€๋Šฅ์ผ€ ํ•œ๋‹ค๋Š” ์•„์ด๋””์–ด๊ฐ€ ์ฐฝ์˜์ ์œผ๋กœ ๋А๊ปด์ง€๊ธฐ๊นŒ์ง€ ํ•œ๋‹ค.

์•„๋‹ˆ Tunnel ์ง„์งœ ํŽธํ•˜๋„ค...
@enbay ๋‹˜ ๋ง์”€์ฒ˜๋Ÿผ ์žฅ์ฐจ ์˜์กด์„ฑ์„ ๊ฑฑ์ •ํ•ด์•ผ ํ•  ์ง€๊ฒฝ์ด๋‹ค. ๋ฌผ๋ก  ๊ทธ ๋•Œ ์ฏค์ด๋ฉด ํ•ด๋‹น ์ปจ์…‰ํŠธ์˜ FOSS ํ”„๋กœ์ ํŠธ๊ฐ€ ์–ด๋”˜๊ฐ€์— ์žˆ๊ฑฐ๋‚˜ ์ƒ๊ฒจ๋‚  ๊ฒƒ์ด๋ผ ์ƒ๊ฐํ•œ๋‹ค.

: ์ค‘๊ฐ„ ์ •๋ฆฌ

- ๋„๋ฉ”์ธ: 2๊ฐœ๋ฅผ -์— ๋ฌผ๋ ค์„œ ๋ธ”๋กœ๊ทธ, ๋งˆ์Šคํ† ๋ˆ ์ธ์Šคํ„ด์Šค ๋“ฑ์„ ์—ฐ๊ฒฐํ–ˆ๋‹ค. ๋งŒ๋ฃŒ์ผ์€ 10๋…„ ์ฏค ๋‚จ์•˜์œผ๋ฏ€๋กœ ๋‹น๋ถ„๊ฐ„ ์žŠ๊ณ  ์ง€๋‚ด๋„ ๋˜๊ฒ ๋‹ค.

- ํ™ˆ์„œ๋ฒ„: -์— -๋ฅผ ๊น”์•„์„œ DNS ์„œ๋ฒ„ ๊ฒธ ํ”„๋ก์‹œ ์ฒ˜๋ฆฌ์šฉ ์›น์„œ๋ฒ„๋กœ ๊ฐ€๋™ ์ค‘. ๋””๋น„๊ฐ€ ํ•„์š”ํ•œ ์„œ๋น„์Šค๋Š” ๊ตด๋ฆฌ์ง€ ์•Š์„ ์ƒ๊ฐ์ด๋ผ ์ด๋Œ€๋กœ ์ข‹๋‹ค.

- NAS: i3-4160 ๋ฐ์Šคํฌํ†ฑ์— -๋ฅผ ๊น”์•„์„œ ๋‚จ๋Š” HDD(500G, 3T)๋ฅผ ๋ถ™์˜€๋‹ค. ํด๋ผ์šฐ๋“œ์— ์ €์žฅ ์ค‘์ด๋˜ ๋ฏธ๋””์–ด ์ž๋ฃŒ ์ผ๋ถ€๋ฅผ ์„œ๋น™ ์ค‘. ์•„์ง ๋ฐฑ์—… ๋ฃจํ‹ด์€ ์—†๋‹ค.

- ์ž‘์—…์ปด: ๋งž์ถ˜ ์ง€ 5๋…„ ์ฏค ๋œ 3700x ๋ฐ์Šคํฌํ†ฑ. ์ž‘์—…๋งŒ ํ•˜๋‹ˆ๊นŒ ์˜ค๋ž˜ ๊ฐˆ ์ค„ ์•Œ์•˜๋Š”๋ฐ, ์Šฌ์Šฌ ๋ฌด๊ฑฐ์›Œ์ง€๊ณ  ์žˆ๋‹ค. ํ•˜ํ•„ ๋“œ๋ผ์ด๋ฒ„๋„ ์š”์ƒˆ ๋ฉ”๋กฑํ•˜๊ณ ... ๋ช‡ ๊ฐœ์›” ์•ˆ์— ๋นŒ๋“œ๋ฅผ ์œ„ํ•ด ๊ธฐ๋ฐ˜์œผ๋กœ ์˜ฎ๊ธธ ๊ฐ€๋Šฅ์„ฑ์ด ์žˆ์–ด ๋ณ„๋‹ค๋ฅธ ์กฐ์น˜ ์—†์ด ์‚ฌ์šฉ ์ค‘.

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

github.com

Cloudflare Workers ยท Issue #233 ยท fedify-dev/fedify

Background Fedify currently supports three JavaScript runtimes: Node.js, Bun, and Deno. However, there has been significant community demand for supporting Cloudflare Workers, a popular edge functi...

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

github.com

Cloudflare Workers ยท Issue #233 ยท fedify-dev/fedify

Background Fedify currently supports three JavaScript runtimes: Node.js, Bun, and Deno. However, there has been significant community demand for supporting Cloudflare Workers, a popular edge functi...

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

github.com

Cloudflare Workers ยท Issue #233 ยท fedify-dev/fedify

Background Fedify currently supports three JavaScript runtimes: Node.js, Bun, and Deno. However, there has been significant community demand for supporting Cloudflare Workers, a popular edge functi...

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

github.com

Cloudflare Workers ยท Issue #233 ยท fedify-dev/fedify

Background Fedify currently supports three JavaScript runtimes: Node.js, Bun, and Deno. However, there has been significant community demand for supporting Cloudflare Workers, a popular edge functi...

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

github.com

Cloudflare Workers ยท Issue #233 ยท fedify-dev/fedify

Background Fedify currently supports three JavaScript runtimes: Node.js, Bun, and Deno. However, there has been significant community demand for supporting Cloudflare Workers, a popular edge functi...

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

github.com

Cloudflare Workers ยท Issue #233 ยท fedify-dev/fedify

Background Fedify currently supports three JavaScript runtimes: Node.js, Bun, and Deno. However, there has been significant community demand for supporting Cloudflare Workers, a popular edge functi...

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

github.com

Cloudflare Workers ยท Issue #233 ยท fedify-dev/fedify

Background Fedify currently supports three JavaScript runtimes: Node.js, Bun, and Deno. However, there has been significant community demand for supporting Cloudflare Workers, a popular edge functi...

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

github.com

Cloudflare Workers ยท Issue #233 ยท fedify-dev/fedify

Background Fedify currently supports three JavaScript runtimes: Node.js, Bun, and Deno. However, there has been significant community demand for supporting Cloudflare Workers, a popular edge functi...

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

github.com

Cloudflare Workers ยท Issue #233 ยท fedify-dev/fedify

Background Fedify currently supports three JavaScript runtimes: Node.js, Bun, and Deno. However, there has been significant community demand for supporting Cloudflare Workers, a popular edge functi...

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

github.com

Cloudflare Workers ยท Issue #233 ยท fedify-dev/fedify

Background Fedify currently supports three JavaScript runtimes: Node.js, Bun, and Deno. However, there has been significant community demand for supporting Cloudflare Workers, a popular edge functi...

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

github.com

Cloudflare Workers ยท Issue #233 ยท fedify-dev/fedify

Background Fedify currently supports three JavaScript runtimes: Node.js, Bun, and Deno. However, there has been significant community demand for supporting Cloudflare Workers, a popular edge functi...

@michael@thms.uk

โ€œWhen looking at where the DDoS attacks originate from, specifically HTTP DDoS attacks, there are a few autonomous systems that stand out. In 2025 Q1, the German-based Hetzner (AS24940) retained its position as the largest source of HTTP DDoS attacks. It was followed by the French-based OVH (AS16276) in second, the US-based DigitalOcean (AS14061) in third, and another German-based provider, Contabo (AS51167), in fourth.โ€

Yikes! Sounds like a who is who of our favourite hosting providers ๐Ÿ˜ฌ

blog.cloudflare.com/ddos-threa

blog.cloudflare.com

Targeted by 20.5 million DDoS attacks, up 358% year-over-year: Cloudflareโ€™s 2025 Q1 DDoS Threat Report

DDoS attacks are surging. In 2025 Q1, Cloudflare blocked +20M attacks (a 358% YoY spike) along with 5.6 Tbps and 4.8 Bpps record-breaking attacks. And that's just the beginning. Read more in our latest DDoS Threat Report.

@michael@thms.uk ยท Reply to Michael

โ€œWhen surveying Cloudflare customers [โ€ฆ] 11% reported that they mistakenly inflicted the DDoS attack on themselves (self-DDoS)โ€

๐Ÿ˜‚ ๐Ÿ˜‚ ๐Ÿ˜‚

@michael@thms.uk ยท Reply to Michael

โ€œWhen surveying Cloudflare customers [โ€ฆ] 11% reported that they mistakenly inflicted the DDoS attack on themselves (self-DDoS)โ€

๐Ÿ˜‚ ๐Ÿ˜‚ ๐Ÿ˜‚

@michael@thms.uk

โ€œWhen looking at where the DDoS attacks originate from, specifically HTTP DDoS attacks, there are a few autonomous systems that stand out. In 2025 Q1, the German-based Hetzner (AS24940) retained its position as the largest source of HTTP DDoS attacks. It was followed by the French-based OVH (AS16276) in second, the US-based DigitalOcean (AS14061) in third, and another German-based provider, Contabo (AS51167), in fourth.โ€

Yikes! Sounds like a who is who of our favourite hosting providers ๐Ÿ˜ฌ

blog.cloudflare.com/ddos-threa

blog.cloudflare.com

Targeted by 20.5 million DDoS attacks, up 358% year-over-year: Cloudflareโ€™s 2025 Q1 DDoS Threat Report

DDoS attacks are surging. In 2025 Q1, Cloudflare blocked +20M attacks (a 358% YoY spike) along with 5.6 Tbps and 4.8 Bpps record-breaking attacks. And that's just the beginning. Read more in our latest DDoS Threat Report.

@stefanmuelller@climatejustice.social

โ€žDas liegt auch an einer Eigenheit der taz. Sie versucht, so viel Infrastruktur wie mรถglich unter eigener Kontrolle zu halten. Weltweit arbeiten viele andere Firmen dauerhaft mit US-amerikanischen Unternehmen zusammen, die Webseiten relativ zuverlรคssig vor DDoS-Angriffen schรผtzen. Fรผr die EDV-Abteilung der taz kommt das aus Grรผnden des Datenschutzes nicht infrage, weil sie befรผrchtet, dass solche Firmen mitlesen kรถnnten, wer taz.de besucht und welche Daten und auch Passwรถrter verwendet werden.โ€œ

Danke @tazgetroete! Das macht Ihr genau richtig. GroรŸen Dank in die EDV, dafรผr, dass sie solche Attacken abwehren.

taz.de/!6081815

taz.de

Angriff auf die taz: Gezielt getroffen

Am Tag der Bundestagswahl legt ein Cyberangriff taz.de lahm. Es ist nicht der erste dieser Art. Warum das kein Zufall ist.

@stefanmuelller@climatejustice.social

โ€žDas liegt auch an einer Eigenheit der taz. Sie versucht, so viel Infrastruktur wie mรถglich unter eigener Kontrolle zu halten. Weltweit arbeiten viele andere Firmen dauerhaft mit US-amerikanischen Unternehmen zusammen, die Webseiten relativ zuverlรคssig vor DDoS-Angriffen schรผtzen. Fรผr die EDV-Abteilung der taz kommt das aus Grรผnden des Datenschutzes nicht infrage, weil sie befรผrchtet, dass solche Firmen mitlesen kรถnnten, wer taz.de besucht und welche Daten und auch Passwรถrter verwendet werden.โ€œ

Danke @tazgetroete! Das macht Ihr genau richtig. GroรŸen Dank in die EDV, dafรผr, dass sie solche Attacken abwehren.

taz.de/!6081815

taz.de

Angriff auf die taz: Gezielt getroffen

Am Tag der Bundestagswahl legt ein Cyberangriff taz.de lahm. Es ist nicht der erste dieser Art. Warum das kein Zufall ist.

@osma it doesn't matter how federated you are. Rogue governments will allow indiscriminate internet blocks, like what's happening in , where all major ISP are blocking some major CDN and cloud providers like , , Quic or CDN77 (affecting millions of legitimate websites) just because some of their users are using them to host illegal IPTV streaming of sports (!)
vercel.com/blog/update-on-spai

vercel.com

Update on Spain and LaLiga blocks of the internet - Vercel

A Spanish court has empowered LaLiga to block entire IP addresses tied to unauthorized football streamsโ€”causing legitimate websites hosted on Vercel to become inaccessible in Spain.

@nibushibu@vivaldi.net

VPN ใฏ :apple_inc: ใซใ‚‚ :android_logo: ใซใ‚‚ใ‚‚ใจใ‚‚ใจใ‚คใƒณใ‚นใƒˆใƒผใƒซใฏใ—ใฆใ‚ใฃใŸใ—ใ€ใ‚‚ใจใ‚‚ใจ็„กๆ–™ใƒ—ใƒฉใƒณใงไฝฟใฃใฆใŸใ‹ใ‚‰ใ€่‡ชๅˆ†ใงใใ‚‹ใ“ใจใฏๅฎŸใฏใ‚ใพใ‚Šๅค‰ใ‚ใฃใฆใฏใ„ใชใ„ใ‚“ใ ใ‚ˆใชโ€ฆ
ใ‚ใจ ใฎ ใ‚‚ VPN ็š„ใชๆฐ—ๆŒใกใ‚คใƒณใ‚นใƒˆใƒผใƒซใ—ใฆใ„ใฆไฝฟใฃใฆใ‚‹ :loading:

@TheZeldaZone@mastodon.social

I've been trying to de-corporate where I can but like. There's not really an alternative to , right...? Aside from "a shit load of my own hardware"? Feels like an okay "no ethical consumption" write off for now

@avery@mastodon.v0dev.cfd

Cloudflare is the worst.

Banning people under 18 without warning, even when they want to use parental consent, is anti-youth entrepreneurship.

You build projects, buy domains, verify your identity, and they delete your whole account just for being young. โ˜ ๏ธ

No second chance, no future. This affects many developers, and even Cloudflare themselves.

I'll never recommend Cloudflare, and I never will.

@dampuzakura@fedibird.com

Based on Cloudflareโ€™s Speed Test tool, my Internet connection download speed is 31Mbps. Detailed analytics help me better understand our user experience. Try it yourself at speed.cloudflare.com/

speed.cloudflare.com

Internet Speed Test - Measure Network Performance | Cloudflare

Test your Internet connection. Check your network performance with our Internet speed test. Powered by Cloudflare's global edge network.

@cloudflare@noc.social

๐ŸŒ Something new is coming.

The way we build, secure, and scale in the cloud is evolving faster than ever. Thatโ€™s why weโ€™re bringing together top industry leaders to explore whatโ€™s next.

Real stories. Practical insights. A fresh perspective on the future of AI, security, and cloud innovation.

Stay tuned. ๐Ÿ‘€

@nibushibu@vivaldi.net

ใฎ ใ‚ขใƒ—ใƒชใ€ใƒžใ‚ทใƒณใฎๅ†่ตทๅ‹•ใจใ‹ใ™ใ‚‹ใจใพใŸ IPC Error ใจใ„ใ†่กจ็คบใซใชใฃใกใ‚ƒใ†ใช :tony_sigh:

@nibushibu@vivaldi.net

ใ‚ขใƒ—ใƒช็น‹ใŒใ‚‰ใชใ‹ใฃใŸใฎใ€ ใ‚ขใƒƒใƒ—ใƒ‡ใƒผใƒˆใ—ใŸใ‹ใ‚‰ใ‹ใ€‚
ๅ†ใ‚คใƒณใ‚นใƒˆใƒผใƒซใ—ใŸใ‚‰็น‹ใŒใ‚‹ใ‚ˆใ†ใซใชใฃใŸ :tony_smiling:

@ZhiZhu@newsie.social ยท Reply to Zhi Zhu ๐Ÿ•ธ๏ธ

Anyone Can Push Updates to the DOGE.gov Website:
"These 'experts' left their database open."
404media.co/anyone-can-push-up

"The doge.gov website... is insecure & pulls from a database that can be edited by anyone...

doge.gov is seemingly built on a Pages site that is not currently hosted on government servers...

has secured administrator access to the codebases at various agencies, including the Dept of Treasury."

News headline: DOGE
Anyone Can Push Updates to the DOGE.gov Website

"These 'experts' left their database open."

by Jason Koebler 
Feb 14, 2025 at 1:42 AM
ALT text

News headline: DOGE Anyone Can Push Updates to the DOGE.gov Website "These 'experts' left their database open." by Jason Koebler Feb 14, 2025 at 1:42 AM

@RareBird15@allovertheplace.ca

Help Needed with Cloudflare Zero Trust, Pages, and Workers for ReactFlux + MiniFlux Setup

Hi everyone,

I'm new to and have been trying to set up a project on my 500. I'm mostly self-taught, so I apologize if I misunderstand anything or miss important details. Here's my situation:

Current Setup

  • I'm running the self-hosted feed reader on my Raspberry Pi 500 (, installed via Pacman).
  • The setup uses as a reverse proxy, a tunnel, and Cloudflare Access for SSO.
  • My application is configured to allow all origins, methods, and headers. It has a policy that allows specific emails or login methods (e.g., GitHub).

What I'm Trying to Do

  • I want to deploy ReactFlux, an alternative frontend for MiniFlux, on .
  • Before setting it up fully, I tested the ReactFlux demo with my MiniFlux instance at https://rss.laniecarmelo.tech. However, ReactFlux couldn't log in.

Suspected Issue

I believe the issue is caused by Cloudflare Access protection blocking ReactFlux from accessing the MiniFlux API (https://rss.laniecarmelo.tech/v1/*).

What I've Tried So Far

  1. I added another hostname (rss.laniecarmelo.tech/v1/*) to my tunnel configuration and created a new Cloudflare Access application with a policy set to "Bypass" for everyone. However, this didn't workโ€”when testing the API endpoint in a private browser window, I'm still asked to sign into Cloudflare.
  2. I also tried setting up the hostname with "Protect with Access" turned off but got the same results.
  3. Next, I attempted to use a written in JavaScript to bypass authentication for /v1/*, but it doesn't seem to be doing anything (or isn't being triggered).

What I Need Help With

  • How can I properly configure Cloudflare so ReactFlux can access the MiniFlux API (/v1/*) while keeping the rest of my MiniFlux instance protected by Cloudflare Access?
  • I've been stuck on this for a couple of days and would really appreciate any guidance or suggestions!

Thanks in advance for your help!


@selfhosting @selfhost @selfhosted

reactflux.pages.dev

ReactFlux

A Simple but Powerful RSS Reader for Miniflux

@qiita@rss-mstdn.studiofreesia.com
@preslavrachev@mastodon.social

Not a single week passes, without me writing an email to a website owner that need to unhook their site's RSS endpoint from Cloudflare's claws.

Do it for the sake of preserving your reader's audience!

openrss.org/blog/using-cloudfl

---

openrss.org

Using Cloudflare on your website could be blocking RSS users

Cloudflare's security features could be blocking RSS feed users from accessing your website

@bojkotiMalbona@infosec.exchange ยท Reply to The Tor Project

@torproject I see nothing there to address the elephant in the room -- the top problem from our top adversary:

Of course there needs to be a campaign against oppressive regimes but all Tor users worldwide are under DoS attack by Cloudflare. We have lost access to ยฝ the web and no 2024 efforts counter the loss of availability.

Also in 2024: archive.org went down for a day or so, at which moment all Tor users also lost access to archived Cloudflare sites.

@preslavrachev@mastodon.social

Not a single week passes, without me writing an email to a website owner that need to unhook their site's RSS endpoint from Cloudflare's claws.

Do it for the sake of preserving your reader's audience!

openrss.org/blog/using-cloudfl

---

openrss.org

Using Cloudflare on your website could be blocking RSS users

Cloudflare's security features could be blocking RSS feed users from accessing your website

@f09fa681@digitalcourage.social ยท Reply to Michaล‚ "rysiek" Woลบniak ยท ๐Ÿ‡บ๐Ÿ‡ฆ

@rysiek This is downplaying it way too much for my taste. Let me explain:

The rough location information is usually only available to servers. Now, even though I prefer zero trust, I would argue that trusting a messenger's server to not give away my rough location is way more reasonable than trusting the person that uploaded the data I'm downloading from the server.

**But in this case, the person that uploaded the data can extract the location I'm downloading it from.** This is big. It takes metadata to a whole different level.

I also want to quickly respond to the arguments:

That very rough radius could actually a pretty big deal in less populated areas.

The second argument is whataboutism. (And there are definitely apps that are not affected.)

Kinda agree with the third one though.

---

If I were , I would turn off the caching mechanism for now and urge to rethink their statement. The privacy protection mechanisms are clearly lacking. Cloudflares position is simply not acceptable.

@bojkotiMalbona@infosec.exchange ยท Reply to 08956495
@bojkotiMalbona@infosec.exchange ยท Reply to Michael Macnair

@mykter Yet another reason to laugh in the face of those who ignored the warnings about from years past:
github.com/privacytools/privac

And WTF.. Signal thought it was wise to use as a proxy. Fucking morons. Anyone who read the above thread years ago knows Signal makes foolish decisions and does not steer clear of mass surveillance risks.

And still today the Signal die-hard loyal patrons continue to pimp Signal. Just yesterday I saw some Signal promoting posts.

Question to signal users: do you use Orbot to route Signal over Tor? Does that work? If yes, this why I actually prefer Cloudflare hosts to block tor -- to do me the favor of not having to block at the firewall.

I would like to get my security house more in order by having an egress firewall that blocks all attempts to reach Cloudflare sites.

github.com

โŒ Software Removal | Signal ยท Issue #779 ยท privacytools/privacytools.io

Problem with Signal Signal has copious privacy issues making it unfit for privacytools.io endorsement. Users are forced to supply a phone number to Signal (https://github.com/privacytoolsIO/privacy...

@thenewoil@mastodon.thenewoil.org
@dampuzakura@fedibird.com
@matthias@social.klein.ruhr

For the first time in two weeks, all services are back online, and the is glowing green again. The experiment of integrating and with has been shelved, and everything has been rolled back to its original state.

While this setup might work perfectly for some, Iโ€™ve decided to stick with native . This way, I maintain full control over my data and keep things simple and secure.

A system status page featuring various service components with operational metrics. Each service displays its current status, uptime percentage, and a time indication. Most services show a status of "100% operational." The layout includes sections for infrastructure, hypervisors, and
ALT text

A system status page featuring various service components with operational metrics. Each service displays its current status, uptime percentage, and a time indication. Most services show a status of "100% operational." The layout includes sections for infrastructure, hypervisors, and

@qiita@rss-mstdn.studiofreesia.com

ใ€ๅ€‹ไบบ้–‹็™บใ€‘ๅ˜˜ใฎใƒใ‚ฑใƒใ‚ฑใฎใ‚ซใƒผใƒ‰ใ‚’ไฝœใ‚Œใ‚‹ใ‚ตใƒผใƒ“ใ‚นใ‚’ไฝœใฃใŸใ€ใ‚ณใƒผใƒ‰ๅ…จๅ…ฌ้–‹ใ€‘
qiita.com/retoruto_carry/items

@Eliot_L@social.coop ยท Reply to Eliot Lash

Thanks everyone who responded to my question about finding an alternative. I've investigated everyone's suggestions and crunched the numbers. R2 looks to be the cheapest option (cheaper than S3 even) but I'm uncomfortable with them hosting hate speech and terror organizations.

/ is the second cheapest and they seem to be on the up-and-up so I am currently evaluating them. Thanks @titociuro for the suggestion, the onboarding process has been smooth so far!

Spreadsheet showing current AWS S3 hosting costs and estimated costs with all the providers suggested by people responding to this thread.

S3 Usage For October 2024	
S3 Data (GiB)	22.65
S3 Egress (GiB)	2.27
S3 Bill	$0.52
NSFN Domain + DNS + Privacy Annual (Paid thru May 04, 2026)	$20.50
Amortized Monthly	$1.71
Total Monthly	$2.23
	
Data Storage Fees	
Tigris (Fly.io) $0.02/GB/month	$0.45
	
Data Egress Fees	
Tigris (Fly.io)	$0
	
Total Esimated Monthly Cost	
Cloudflare R2	$0.20
Tigris (Fly.io)	$0.45
Hetzner Level 1 Hosting (10GB+Domain)	$2.21
Hetzner Level 4 Hosting (40GB+Domain)	$5.71
Digital Ocean Spaces	$5.00
Ubespace Suggested Donation	$5.30
ALT text

Spreadsheet showing current AWS S3 hosting costs and estimated costs with all the providers suggested by people responding to this thread. S3 Usage For October 2024 S3 Data (GiB) 22.65 S3 Egress (GiB) 2.27 S3 Bill $0.52 NSFN Domain + DNS + Privacy Annual (Paid thru May 04, 2026) $20.50 Amortized Monthly $1.71 Total Monthly $2.23 Data Storage Fees Tigris (Fly.io) $0.02/GB/month $0.45 Data Egress Fees Tigris (Fly.io) $0 Total Esimated Monthly Cost Cloudflare R2 $0.20 Tigris (Fly.io) $0.45 Hetzner Level 1 Hosting (10GB+Domain) $2.21 Hetzner Level 4 Hosting (40GB+Domain) $5.71 Digital Ocean Spaces $5.00 Ubespace Suggested Donation $5.30

@preya@mastodon.social

Die betreibt digitale Wegelagerei durch ihre -Politik. Seit Monaten leiden Millionen Kunden durch kaum nutzbare Geschwindigkeit beim Verbindungsaufbau zu , EA, Netflix, etc. Stell dir vor du zahlst 60โ‚ฌ/Monat um dann deine Spiele mit 120 kB/s zu laden. Die Foren sind voll davon aber medial erregt das irgendwie sehr wenig Aufmerksamkeit. Wieso berichtet kaum jemand darรผber? Wieso ist das kein Fall fรผr die Verbraucherzentralen?

@cloudflare@noc.social

Weโ€™re all set for GITEX GLOBAL โ€“ the worldโ€™s largest tech and startup event! ๐ŸŒ๐Ÿ’ก Get ready for a week full of insightful conversations, cutting-edge innovation, and transformative ideas.

The Cloudflare team will be there to share tech talks, AI experiences, and so much more! Donโ€™t miss out on this incredible opportunity to connect and explore the future of technology. Visit us at Hall 8 Booth B40.

Stay tuned and come join us.

๏ปฟ

@0ddj0bb@infosec.exchange

has demonstrated they do not care if they knowingly serve malware distributors as their customers.

Some how they think being a "pass through " cdn means they dont actually serve the traffic they do.

FTC should look at them

@Jeremiah@alpaca.gold

Happy 2nd anniversary to this tweet about Cloudflare booting Kiwi Farms.

Stripe HR investigated me for potential employee social media misconduct because an executive thought I was posting about Stripe willfully working with anti-trans, white supremacy, and antisemitic groups.

Screenshot source: twitter.com/JeremiahLee/status

Screenshot of tweet. I donโ€™t know how many "infrastructure" companies need to hear this, but there is no reward for being the most neutral when it comes to doing business with people who promote intolerance of othersโ€™ humanityโ€”other than profiting from their hate. Username @JeremiahLee. 9:13 PM. Sep 27, 2022

Username Jeremiah Lee.
ALT text

Screenshot of tweet. I donโ€™t know how many "infrastructure" companies need to hear this, but there is no reward for being the most neutral when it comes to doing business with people who promote intolerance of othersโ€™ humanityโ€”other than profiting from their hate. Username @JeremiahLee. 9:13 PM. Sep 27, 2022 Username Jeremiah Lee.

@ame@breta.moe

Strong recommendation for keeping up with the cloudflare blog updates this week!

Some highlights:
* Image transformations on the free tier
* More models in workers AI
* A new hosted sqlite service where code is run right next to the db
* A new, persistent logging service for Workers
* CI for Workers
* Increased nodejs compatibility for Workers
* An upcoming container platform with GPU support next year ๐Ÿคฏ

@hydrandt@fosstodon.org

I cancelled pro subscription in May.

I got confirmation e-mails.

I got charged in June and July.

I created two tickets about it (first was auto-closed). I can not see the tickets in the interface (it is completely empty).

I only got an automated response explaining how to cancel a subscription (...).

Anyone else having this kind of problem? Obviously I want a refund. I'm not touching it (cancelling again) in the interface so they can have a look at it...

@cloudflare

@suzannealdrich@hachyderm.io

๐Ÿ”’ Exciting times ahead! Today, I officially rejoin the team at Cloudflare, ready to dive deep into the latest in cybersecurity and cloud innovations. Looking forward to contributing to pioneering projects and tackling the evolving challenges in internet security. Let's make the digital world a safer place together! ๐ŸŒ

Today I re-joined Cloudflare to help build a #BetterInternet
ALT text

Today I re-joined Cloudflare to help build a #BetterInternet

@com@mastodon.social ยท Reply to Quinn Comendant

Hetzner is the most admired cloud platform (75% want to continue working with it), but is only used by 5% of developers. Cloudflare admired by 68% (used by 15%), AWS admired by 63% (used by 48%), Azure admired by 60% (used by 28%), GCP admired by 56% (used by 25%).

The image shows a bar chart titled "Admired and Desired / Desired and Admired - Cloud platforms." It displays the percentages of respondents who desire and admire various cloud platforms. The platforms and their respective percentages are:

- Amazon Web Services: Desired 43.4%, Admired 63.3%
- Microsoft Azure: Desired 24.9%, Admired 59.9%
- Google Cloud: Desired 23.4%, Admired 55.6%
- Cloudflare: Desired 15.8%, Admired 68.2%
- Firebase: Desired 11.8%, Admired 54.8%
- Vercel: Desired 10.6%, Admired 59.4%
- Digital Ocean: Desired 10.4%, Admired 56.6%
- Hetzner: Desired 5.6%, Admired 59.4%
- Supabase: Desired 5.3%, Admired 74.6%
- Netlify: Desired 5.2%, Admired 49.4%
- Heroku: Desired 4%, Admired 25.8%
- Fly.io: Desired 3.9%, Admired 61.7%
- VMware: Desired 3.8%, Admired 39.1%
- Linode: Desired 3.5%, Admired 55.2%
- Oracle Cloud Infrastructure: Desired 2.9%, Admired 56.3%
- Databricks: Desired 2.7%, Admired 54.9%
- OpenShift: Desired 2.5%, Admired 52%
- Managed Hosting: Desired 2.4%, Admired 62.6%
- OVH: Desired 2.4%, Admired 55.1%
- Render: Desired 2.2%, Admired 50.2%
- OpenStack: Desired 2.1%, Admired 49%
- PythonAnywhere: Desired 2.1%, Admired 41.6%
- Vultr: Desired 1.5%, Admired 51.1%
- Alibaba Cloud: Desired 1.4%, Admired 40.9%
- IBM Cloud or Watson: Desired 1.4%, Admired 40.3%
- Scaleway: Desired 0.9%, Admired 55.6%
- Colocation: Desired 0.8%, Admired 62.5%
ALT text

The image shows a bar chart titled "Admired and Desired / Desired and Admired - Cloud platforms." It displays the percentages of respondents who desire and admire various cloud platforms. The platforms and their respective percentages are: - Amazon Web Services: Desired 43.4%, Admired 63.3% - Microsoft Azure: Desired 24.9%, Admired 59.9% - Google Cloud: Desired 23.4%, Admired 55.6% - Cloudflare: Desired 15.8%, Admired 68.2% - Firebase: Desired 11.8%, Admired 54.8% - Vercel: Desired 10.6%, Admired 59.4% - Digital Ocean: Desired 10.4%, Admired 56.6% - Hetzner: Desired 5.6%, Admired 59.4% - Supabase: Desired 5.3%, Admired 74.6% - Netlify: Desired 5.2%, Admired 49.4% - Heroku: Desired 4%, Admired 25.8% - Fly.io: Desired 3.9%, Admired 61.7% - VMware: Desired 3.8%, Admired 39.1% - Linode: Desired 3.5%, Admired 55.2% - Oracle Cloud Infrastructure: Desired 2.9%, Admired 56.3% - Databricks: Desired 2.7%, Admired 54.9% - OpenShift: Desired 2.5%, Admired 52% - Managed Hosting: Desired 2.4%, Admired 62.6% - OVH: Desired 2.4%, Admired 55.1% - Render: Desired 2.2%, Admired 50.2% - OpenStack: Desired 2.1%, Admired 49% - PythonAnywhere: Desired 2.1%, Admired 41.6% - Vultr: Desired 1.5%, Admired 51.1% - Alibaba Cloud: Desired 1.4%, Admired 40.9% - IBM Cloud or Watson: Desired 1.4%, Admired 40.3% - Scaleway: Desired 0.9%, Admired 55.6% - Colocation: Desired 0.8%, Admired 62.5%

The image shows a bar chart titled "Most popular technologies / All Respondents - Cloud platforms." It displays the popularity of various cloud platforms among survey respondents. The platforms and their respective percentages are:

- Amazon Web Services: 48%
- Microsoft Azure: 27.8%
- Google Cloud: 25.1%
- Cloudflare: 15.1%
- Firebase: 13.9%
- Vercel: 11.9%
- Digital Ocean: 11.7%
- Heroku: 8.2%
- Netlify: 7%
- VMware: 6.6%
- Hetzner: 5%
- Supabase: 3.8%
- Linode, now Akamai: 3.1%
- OVH: 3%
- Managed Hosting: 3%
- Oracle Cloud Infrastructure: 2.9%
- Render: 2.8%
- Fly.io: 2.6%
- OpenShift: 2.4%
- Databricks: 2%
- PythonAnywhere: 1.9%
- Vultr: 1.7%
- OpenStack: 1.6%
- Alibaba Cloud: 1.2%
- IBM Cloud or Watson: 1.1%
- Scaleway: 0.9%
- Colocation: 0.7%
ALT text

The image shows a bar chart titled "Most popular technologies / All Respondents - Cloud platforms." It displays the popularity of various cloud platforms among survey respondents. The platforms and their respective percentages are: - Amazon Web Services: 48% - Microsoft Azure: 27.8% - Google Cloud: 25.1% - Cloudflare: 15.1% - Firebase: 13.9% - Vercel: 11.9% - Digital Ocean: 11.7% - Heroku: 8.2% - Netlify: 7% - VMware: 6.6% - Hetzner: 5% - Supabase: 3.8% - Linode, now Akamai: 3.1% - OVH: 3% - Managed Hosting: 3% - Oracle Cloud Infrastructure: 2.9% - Render: 2.8% - Fly.io: 2.6% - OpenShift: 2.4% - Databricks: 2% - PythonAnywhere: 1.9% - Vultr: 1.7% - OpenStack: 1.6% - Alibaba Cloud: 1.2% - IBM Cloud or Watson: 1.1% - Scaleway: 0.9% - Colocation: 0.7%

@thisismissem@hachyderm.io

Yo, cloudflare, you're sales contact number in germany.. isn't you??!

Legit just called this number and it didn't work, tried swapping +49 for 0 and it took me to someone that was definitely not Cloudflare.

Screenshot from the Cloudflare website showing a sales phone number of: +49 89 2555 2276
ALT text

Screenshot from the Cloudflare website showing a sales phone number of: +49 89 2555 2276