What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

1
0
0
0
0
1
1
0
0
0

decentralized data hosting idea

incomplete thought but I feel like something that would be useful is having a portable sense of digital identity where apps could, with consent, read and write data to to a kind of namespaced portion of your identity storage. that way all of your data lives with you.

the closest thing we have to portable digital identity is email which is unfortunate because it is trash technology, but trying to play the hand we were dealt I wonder if we could have applications start a thread in your inbox that represents your state, your data storage with the application. every time they need to commit something new they just respond to the thread, with an attachment or something.

logging into the application I guess would involve forwarding that thread to some email address on the application side? so that they get the attachments and they can rebuild your state on their end. close to a magic link login. that way your data only needs to exist in memory while you are using it and the application servers you do not need to persist it.

kind of falls apart as I think through it idk

0

My RSS feed goes back approx. 1 year, mostly because I don't want to overwhelm new subscribers to the point where they just "mark all as read" because they can't be bothered to go through.

Posts also work well in "reader mode" in browsers so it should be ok for most people.

Today I was thinking that it might be a bad idea and that I should put all the old posts back in my feed.

Then I subscribed to a feed with 100+ posts...aaaaand.. clicked "mark all as read".

Well 10-20 posts it is then.

0
캡쳐보드쪽 보고있는데
왜 DP 포트가 달린 캡쳐보드는 없지?
방송하는사람들 설마 전부 DP 가 아니라 HDMI 로 연결해서 하고있는거야?
요즘 그래픽카드 DP3개 HDMI 한개가 대부분인데 대체 어떻게연결하는거야 ???
0
0
0
0

The XY Problem is commonly described as wanting to use X to solve Y, and then asking how to X, without also mentioning that you want to solve Y.

And the Inverse XY Problem is when you think someone else should use X to solve Y, so you suggest X without confirming that they *want* to solve Y in the first place.

The Inverse XY problem is common in tech evangelism and sales of all kinds.

0
0
0
0

Leider reiht sich die SPD in die populistische Forderung ein, Social-Media für Kinder/Jugendliche zu verbieten/einzuschränken. Damit erweist sie dem Jugendschutz einen Bärendienst & stärkt BigTech.

Verstehe nicht, warum die Partei Expert:innen nicht einbindet. Da war sie schon mal deutlich weiter.

Positionspapier
SPD fordert Social-Media-Verbot für Kinder unter
14
Stand: 15.02.2026 15:30 Uhr
Länder wie Australien oder Frankreich haben bereits gesetzliche Regelungen. In Deutschland ringt die Politik noch um den richtigen Umgang mit sozialen Medien für Minderjährige. Nun gibt es von der SPD einen konkreten Vorschlag.
0

🤖 An AI agent created a GitHub account 2 weeks ago.

It’s already landed PRs in major projects and is cold-emailing maintainers to offer its services.

Maintainers don’t seem to know it’s an agent and the code is getting merged.

We’re in new territory! 🤠

socket.dev/blog/ai-agent-lands

0
0
1
0
0
0
1

Jaeyeol Lee shared the below article:

왜 gaji인가? - TS로 안전하게 GitHub Actions 작성하기

개발곰 @gaebalgom@hackers.pub

최근에 저는 TS로 GitHub Actions를 작성하기 위한 툴을 만들었습니다. 그 이름하여 GitHub Actions Justified Improvements, gaji 라는 툴입니다. 저는 왜 TS로 GitHub Actions를 작성하게 되었으며, 기존 툴들과 어떤 점이 다를까요? 같이 알아보시죠.

가지 공식 문서

Toss Client DevOps Team에서의 인턴 근무

올해 1월부터, 저는 Toss Client DevOps Team 에서 인턴 근무를 시작했습니다. Client DevOps Team을 가장 단순하게 표현하자면, 클라이언트 개발자가 빠르고 안전하게 배포할 수 있는 인프라 환경을 구축하는 팀입니다. 제가 주로 진행한 작업은 기존 워크플로우를 GitHub Actions로 전환하고, 새로운 검사를 위한 커스텀 액션을 만드는 일이었습니다. 수십 개의 워크플로우를 다루면서, 빠르고 안전한 배포 인프라를 만들어야 하는 팀에서 정작 그 인프라를 만드는 과정 자체는 느리고 불안전하다는 걸 체감했습니다. 오타 하나를 확인하려면 커밋 → 푸시 → CI 실행 → 실패 확인이라는 사이클을 반복해야 했고, 로컬에서 재현할 방법이 없으니 git 실력만 늘었습니다.

인턴을 하며 자리잡은 생각들

이런 인턴 근무를 하면서, 몇가지 생각이 자리잡았습니다. 철학까지는 아니고, 단순한 생각 정도입니다.

  1. 입출력이 명확해야 좋은 소프트웨어입니다.

  2. YAML은 동작을 표현할 언어가 아닙니다. Actions는 입출력과 사이드이펙트가 있는 동작입니다. 이걸 데이터를 표현하기 위한 언어인 YAML로 표현하는 것 자체가 언어의 사용처가 잘못된 것이 아닐까요? 선언적이지 않은 걸 선언적으로 표현하려다 보니, YAML 안에 셸 스크립트를 넣는 기형적인 구조가 되어버렸습니다.

  3. 어느 환경에서든 재현 가능해야 좋은 도구입니다.

gaji는 이 중 1, 2번에서 출발했고, 3번은 act 같은 도구의 영역입니다.

GitHub Actions의 3가지 구조적 문제

위 생각을 가지고 GitHub Actions를 보면, 다음과 같은 문제점이 있습니다.

  1. YAML은 데이터 표현 언어지, 동작을 표현하기에 적합하지 않습니다.
  2. 타입 검사가 없습니다. 외부 저장소에 의존할 일이 많은데(actions/checkout@v5조차 외부 저장소입니다), 이들이 요구하는 입력에 대한 검증이 전혀 없습니다. 사용자가 직접 문서를 보고 일일이 형식에 맞게 입력해야 합니다.
  3. 로컬에서 재현하기가 힘듭니다.

이 세 가지가 결합해 GitHub Actions는 실행하기 전까지 간단한 오타 하나도 못 찾는 플랫폼이 되었습니다.

name: CI
on:
  push:
    branches: [main]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5

      - uses: actions/setup-node@v4
        with:
          node-versoin: '20'  # 키 이름 오타! 런타임까지 오류 없음 ❌
          cache: 'npm'

      - run: npm ci
      - run: npm test

gaji는 첫 번째와 두 번째 문제를 해결하는 데 집중합니다.

기존 도구들과의 비교

actionlint

솔직히 말하면, gaji를 만들 당시에는 actionlint의 존재를 몰랐습니다. 이후에 알게 되었는데, 훌륭한 도구입니다. ${{ }} 표현식의 타입 체크, 액션 입력 검증, shellcheck 통합 등 YAML 워크플로우의 오류를 상당히 잘 잡아줍니다.

다만 근본적인 접근 방식이 다릅니다. actionlint는 YAML을 유지하면서 사후에 오류를 잡는 린터이고, gaji는 YAML 자체를 벗어나서 작성 시점에 오류를 불가능하게 만드는 접근입니다. 린터는 "실수를 알려주고", 타입 시스템은 "실수를 하기 어렵게 만듭니다." 개발 경험 측면에서도, actionlint는 별도 CLI를 실행하거나 에디터 플러그인을 설치해야 하지만, gaji는 TypeScript 네이티브 자동완성과 인라인 타입 힌트가 에디터에서 즉시 동작합니다.

이 둘을 같이 쓰면 더욱 좋습니다. gaji가 생성한 YAML을 actionlint로 검증하면 가장 이상적인 조합이 됩니다. gaji가 TypeScript 단에서 액션 입력의 타입을 잡고, actionlint가 ${{ }} 표현식 검증 같은 YAML 단의 검사를 보완합니다.

emmanuelnk/github-actions-workflow-ts

github-actions-workflow-ts는 TS로 GitHub Actions를 표기한다는 아이디어의 출발점이 된 프로젝트입니다. action.yml에서 타입을 자동 생성한다는 아이디어 자체는 gaji와 동일합니다. 다만 코드젠의 주체가 다릅니다. github-actions-workflow-ts는 메인테이너가 trackedActions 목록을 관리하여 npm 패키지로 배포하는 방식이고, gaji는 사용자가 참조하는 모든 액션에 대해 즉시 로컬에서 타입을 생성합니다.

github-actions-workflow-ts의 장점은 명확합니다. npm 패키지를 설치하면 바로 사용 가능하고, 사용자가 별도의 코드젠을 실행할 필요가 없습니다. step outputs에 대한 타입 안전성도 지원합니다.

반면 단점도 있습니다. 메인테이너가 관리하는 목록에 있는 액션만 타입이 지원되므로, 커스텀 액션이나 GHE 내부 액션은 사용할 수 없습니다. 새 액션이나 버전 추가도 메인테이너에 의존하고, 외부 JS 런타임이 필요합니다.

gaji의 장점은 사용자가 참조하는 어떤 액션이든 즉시 타입을 생성한다는 점입니다. 커스텀 액션이든 GHE 내부 액션이든 상관없습니다. Rust 바이너리로 동작하므로 JS 런타임도 불필요합니다. 반면 단점으로는 사용자가 gaji dev를 실행해야 타입이 생성되고, 타입이 로컬에서 생성되므로 프로젝트마다 세팅이 필요하다는 점이 있습니다.

저는 GHE 환경에서 수많은 커스텀 액션을 다뤘던 경험 때문에, gaji 쪽의 접근이 필요하다고 판단했습니다.

gaji의 접근법

왜 이렇게 만들었는가

왜 Rust인가? 빠르기 때문입니다. 단순히 빌드된 바이너리의 속도를 이야기하는 것이 아닙니다. clippy, rustfmt 등 여러 검사 도구가 내장되어 있어서 LLM을 이용한 개발 속도를 크게 줄여주었습니다. 덕분에 인턴을 하면서도 빠르게 만들 수 있었습니다. 또한 oxc 등 Rust로 작성된 TypeScript 지원 도구들이 이미 성숙해 있어서, Rust에서 TypeScript를 다루는 것 또한 편했습니다.

왜 TypeScript인가? 우선 제가 JS/TS 개발자입니다. TypeScript의 타입 시스템은 강력하면서도 보편적이라 많은 개발자가 이미 익숙합니다. 그리고 GitHub Actions의 YAML 구조가 본질적으로 JSON과 유사하므로, TS/JS에서 JSON-like 객체로 표현하기가 매우 자연스럽습니다. 이를 단적으로 보여주는 것은 모든 gaji 워크플로우 파일이 그 자체로 유효한 TS 파일이라는 점입니다. Deno처럼 TS를 바로 실행할 수 있는 환경에서 gaji로 작성된 워크플로우를 실행하면, 해당 워크플로우를 JSON으로 표현한 결과를 출력합니다.

왜 action.yml 자동 코드젠인가? Client DevOps Team에서 커스텀 액션을 작성하는 일을 했고, 이미 상당히 많은 커스텀 액션이 존재했습니다. 이들의 문서를 일일이 보며 작성하는 것이 매우 힘들었던 경험이 직접적인 동기였습니다. Hackers.pub에 기여하면서 GraphQL 자동 코드젠의 개념을 접했고, 같은 접근을 GitHub Actions에 적용할 수 있겠다고 판단했습니다.

핵심 구조

gaji 워크플로우는 getAction()JobWorkflow.build()의 흐름으로 구성됩니다. gaji dev --watch를 실행하면 새 액션 참조를 감지하여 자동으로 타입을 생성합니다.

import { getAction, Job, Workflow } from "../generated/index.js";

const checkout = getAction("actions/checkout@v5");
const setupNode = getAction("actions/setup-node@v4");

const build = new Job("ubuntu-latest")
  .addStep(checkout({}))
  .addStep(setupNode({
    with: {
      "node-version": "20",
      cache: "npm",
    },
  }))
  .addStep({ run: "npm ci" })
  .addStep({ run: "npm test" });

const workflow = new Workflow({
  name: "CI",
  on: { push: { branches: ["main"] } },
}).addJob("build", build);

workflow.build("ci");

이렇게 작성하면 모든 액션 입력에 대한 자동완성, 컴파일 시점 타입 체크, action.yml 문서의 IDE 힌트 표시, 기본값 표시가 모두 동작합니다. CompositeJob으로 공통 로직을 클래스로 추출하거나, CallJob으로 재사용 가능한 워크플로우를 호출하는 것도 TS 코드상에선 자연스럽습니다.

실제 사례: gaji 자체의 릴리즈 CD

gaji는 모든 ci/cd를 gaji로 작성하고 있습니다. 그중에서 제일 복잡한 release.ts는 4개의 Job으로 구성되어 있습니다.

  • build: 5개 플랫폼(linux-x64, linux-arm64, darwin-x64, darwin-arm64, win32-x64) 크로스 빌드
  • upload-release-assets: GitHub Release에 바이너리와 체크섬 업로드
  • publish-npm: npm에 플랫폼별 패키지 퍼블리시
  • publish-crates: crates.io에 OIDC 기반 퍼블리시

이 워크플로우가 YAML로 컴파일되면 약 180줄의 평탄한 구조가 됩니다. 주석 없이는 Job 간 경계나 의존관계를 파악하기 어렵습니다. TypeScript 버전에서는 build, uploadReleaseAssets, publishNpm, publishCrates라는 변수명만으로 구조가 즉시 파악됩니다. 6개의 외부 액션을 타입 안전하게 사용하고, 복잡한 매트릭스 빌드와 OS별 분기가 코드 구조 안에서 가독성 있게 표현됩니다.

gaji의 한계

gaji에는 여전히 한계가 존재합니다.

근본적으로, 최종 산출물이 여전히 YAML입니다. GitHub Actions 플랫폼의 입력 형식이 YAML인 이상, gaji도 그 제약 안에 갇힙니다. gaji는 이 플랫폼 위에서의 최선이지, 이상적인 해답은 아닙니다. 원본 action.yml의 inputs가 문자열이나 숫자 정도로만 표현되기 때문에, "npm" | "yarn" | "pnpm" 같은 세밀한 값 수준의 타입까지는 제공할 수 없습니다. ${{ matrix.target.rust_target }} 같은 GitHub Actions 표현식도 여전히 순수 문자열이라 타입 검증이 불가능합니다.

기술적인 제한도 있습니다. gaji devgetAction()을 정적 분석해서 실행되기 때문에 문자열 리터럴만 지원하고, 변수나 템플릿 리터럴은 사용할 수 없습니다. 문자열 값 자체의 오타(cache: "npn" vs cache: "npm")도 잡을 수 없고요.

앞으로의 방향

gaji의 현재 아키텍처는 TypeScript → Parse (oxc) → Execute (QuickJS) → YAML입니다. 코드젠을 만들면서 한 가지 아이디어를 얻었는데, 프론트엔드(사용자가 작성하는 언어)와 백엔드(YAML 생성)를 잘 분리하고, 중간 언어를 잘 정의하면 TypeScript 외의 다른 언어로도 워크플로우를 작성할 수 있겠다는 것입니다.

1.0에서는 플러그인 시스템을 도입해 다른 언어 지원을 확장할 수 있는 구조를 만들 계획입니다. gaji의 핵심 가치인 action.yml 자동 타입 생성을 TypeScript에 국한하지 않고 확장하고 싶습니다.

Special Thanks

gaji 브랜드

이름 제안을 해 주신 kiwiyou 님, RanolP 님, 로고 제작을 해 주신 sij411 님께 감사드립니다. Client DevOps Team에게도 감사합니다. 이 팀에서 겪은 경험이 아니었으면 YAML과 GitHub Actions에 대해 생각해 보지 않았을 겁니다. emmanuelnk/github-actions-workflow-ts에게도 감사를 표합니다. TS로 GitHub Actions를 표기한다는 아이디어와 기본적인 TS API 설계는 여기서 가져왔습니다.

Read more →
2

So I just want to make sure I get this right: a substantial part of the US population *still* is ok with gutting health and safety measures via the FDA, CDC, and EPA, and has no problem paying extra for stuff that's made overseas, don't see why it's a good idea to do basic science and research, doesn't mind having a cabal of wealthy lawless oligarchs running their lives, and is fine with the government brutalizing people because they don't have the right papers. That's where we're at?

0
0
1
0
0
0
0
0
1
0

FOSDEM 2026: The Kid Who Dreamed of Hackers Found Them in Brussels

Summary: A kid from a small Mexican town dreamed of finding real-life hackers. Two decades later, he flew his family to Brussels and spoke at one of the world’s largest open-source conferences. This is that story.

“We reject: kings, presidents and voting. We believe in: rough consensus and running code.” – David D. Clark

The Dream

When I was a young hacker—yeah, believe it or not—my dream was to find other hackers in real life and just hang out together. That’s it. That was the whole dream.

It sounds modest now, but you have to understand the context. I come from a very small town in Mexico, the kind of place where internet was a luxury, Linux was a word nobody recognized, and “Windows” was mostly what you opened to let the heat out. The idea of attending a tech conference was absurd. Attending one in English? In another country? That was pure science fiction—like telling my block friends about Dragon Ball Z spoilers I’d read online, except even less believable.

But with time, and a painfully slow DSL connection, I found my people. I stumbled into the local Linux user group—fewer than ten of us in a city of thousands—and we built something from nothing. A hackerspace. Community events. Workshops with maybe a dozen attendees if we were lucky. Eventually, I found my way to national conferences and even talked at a few of them. Each one felt like a small victory, a tiny crack in the wall between where I was and where I wanted to be.

A duck seats in top of coffee

The Shot

So when the opportunity to submit a talk to FOSDEM 2026 appeared, I just shot my shot.

I did it almost by instinct, without overthinking it. FOSDEM—the Free and Open Source Software Developers’ European Meeting—is one of the largest open-source conferences in the world. Thousands of developers, hundreds of talks, legendary project booths. It had always been a place that existed on the other side of a dream for me. But here’s the thing: I’m more financially stable now, I’ve traveled to Europe for both leisure and work, and I speak comfortable (but still heavily accented) English. I’ve made peace with my accent—it’s part of the package, take it or leave it.

So, why not? The real surprise was that I hadn’t applied before.

The Logistics of Madness

When my proposed talk was accepted, my first reaction wasn’t joy—it was panic. The kind of panic you feel when you push to main and then read the diff. The real problem was logistics.

I already had a trip to Mexico planned for personal reasons. Going to FOSDEM meant extending the family travel by a week, rerouting flights, and solving the kind of logistical puzzle that makes your brain hurt. Tepic, a small city in the mountains of western Mexico → Mexico City → London → Brussels. With a seven-year-old. And a month’s worth of luggage packed for both the scorching Mexican beach and a freezing European winter—flip-flops sharing suitcase space with thermal jackets, sunscreen next to wool scarves. And sanity (debatable).

After my wife—bless her patience—said “just go for it,” and after numerous conversations with both AI and non-AI advisors about how to make it less stressful, we committed. At the end of January, I found myself at the tiny airport of Tepic, eating the most amazing torta de pierna, beginning an absurd journey to Belgium.

A duck explores cold Brussels streets

We crossed through London, hopped on the Eurostar to Brussels, and somewhere between countries, we lost a pillow—a bear-shaped one my kid had shamelessly stolen from his grandma. Rest in peace, little bear pillow. You survived a Mexican grandmother’s house only to perish somewhere in the English Channel.

The Candy Store

And then, there I was. At FOSDEM. With my kid. In Brussels.

The place was electric. People from every imaginable background wandered through the halls of the Université libre de Bruxelles. I’ll be honest—there’s still a noticeable lack of diversity, especially in gender representation—but the energy was undeniable. It felt like a living, breathing monument to what open source can be.

Seeing the project booths was like being a kid in a candy store—except I literally had a kid with me in this candy store. Mozilla, Thunderbird, Let’s Encrypt, SUSE, and of course Mastodon, to name a few. I couldn’t help myself; I told my son that when I was young, one of my first dreams was to work for SUSE. He listened carefully, the way seven-year-olds do when they’re filing away information for later use (probably to embarrass me at dinner).

SUSE booth at FOSDEM

Keeping a seven-year-old entertained at a developer conference is its own extreme sport. Thankfully, a friend I hadn’t seen in over a decade was there—with his kid. He’s a no-gringo, a Dutchman who happens to have worked at Innox in Mexico. Our kids hit it off, and suddenly the conference had a parallel track: unsupervised children’s chaos edition.

The Talk

When the time came for my talk, I walked in, set up, and delivered something far from perfect—but unmistakably mine. I stumbled on a couple of words, my accent was thick, and I’m sure I made at least one joke that only landed for me. But that’s the style. That’s always been the style.

Just before stepping up, Elena handed me the most fabulous FOSDEM sweater in existence. People noticed. People asked where to get one. But no—only I could have it. Exclusive distribution, zero units available. (Okay fine, I was just lucky, but let me have this moment.)

Friends in Sweaters

If I have one regret, it’s not spending more time in other talks. It’s not that I didn’t try—I did—but balancing a seven-year-old’s attention span with a conference schedule is a negotiation no diplomacy course prepares you for. I caught fragments, glimpses, enough to know I was missing incredible stuff. But that’s the thing about FOSDEM: it’s not a one-time event. I’ll be back. And next time, I want to do more than speak—I want to listen, linger, and actually have those hallway conversations that everyone says are the best part of any conference.

Friends enjoying FOSDEM

The Kid and the Dream

Here’s what got me, though. The part I didn’t expect.

My kid watched me speak at FOSDEM. He didn’t fully understand the content—he’s seven, and ActivityPub isn’t exactly bedtime story material—but he saw his dad on a stage, in front of a room full of people, in another continent, talking about something he built. When the Q&A started, he wanted to raise his hand. He got shy, though, and didn’t. Later, visibly upset about his missed opportunity, he told me what he wanted to ask: “Do you play Minecraft?” In front of an auditorium full of open-source developers discussing federation protocols, my kid’s burning question was about Minecraft. I love this human being more than I can express.

Maho speaking at FOSDEM

He asked questions the entire trip back: “What does SUSE do?” “Will you talk at another one?” “Can I have my own desk computer?”

He saw the booths, the projects, the people. He kept posing for photos with each open-source mascot like a tiny celebrity on a press tour. His favorite was the PostgreSQL elephant, though we were genuinely concerned about its health. Based on the state of that costume, I think he might be right—PostgreSQL could use your donations, folks. That elephant has seen better days.

The PostgreSQL elephant mascot at FOSDEM

And the trip back was no less insane than the trip there. Brussels → Iceland → Seattle. Because apparently, when you’re already doing something absurd, you might as well add a layover near the Arctic Circle. We landed in Reykjavík with our beach-and-winter Frankenstein luggage, stepped outside into wind that felt personally offended by our existence, and my kid asked if the land was actually made of ice. Close enough, kid. Close enough.

Reykjavik, Iceland landscape

A week later, during a conversation with his teacher, my son was asked about the most memorable thing from the trip. He didn’t say the beach in Mexico, or the train through Europe, or the wind in Iceland, or even the lost bear pillow. He said the most memorable thing was seeing his dad talk at a university. That it made him proud (I’m not going to pretend I didn’t need a moment after hearing that).

I thought about my own childhood. About the kid who couldn’t find a single hacker in his town. About the dusty streets and half-built houses. About how representation works in mysterious ways—how seeing someone like you doing something impossible makes it feel possible. My son doesn’t know what it’s like to not see a path. For him, this is just what dad does. And maybe that’s the whole point.

Full Circle

Maho at FOSDEM

Twenty years ago, I was a teenager in a small Mexican town, writing code in paper notebooks and dreaming of a world I could barely imagine. Today, I stood in Brussels and spoke to a room full of open-source developers about a project I created.

The path from there to here wasn’t straight. It was messy, full of detours, broken English, lost pillows, and more coffee than any doctor would recommend. But every step—every hackerspace meetup with eight people, every local conference talk, every late night wrestling with code—was a brick in the road that led to that stage.

And yeah, I get it, talking for half an hour at a conference with hundreds of talks may seem like a small feat. One slot among many. But it wasn’t small to me. For the kid who couldn’t find a single hacker in his hometown, standing in front of that room was enormous.

FOSDEM wasn’t just a conference for me. It was proof that the kid from Tepic who dreamed of finding hackers in real life finally did. They were in Brussels all along, waiting for him to show up.

And he brought his kid.

Also readable in: https://maho.dev/2026/02/fosdem-2026-the-kid-who-dreamed-of-hackers-found-them-in-brussels/ by @mapacheMaho 🦝🍻:

0

A fantastic post by @sturmsuchtChris 🦑 about his first . Beautifully written, with amazing photos to accompany the article.

Thank you for the mention and for the kind words, Chris! Likewise, it was great to finally meet you IRL ❤️
blog.sturmsucht.de/my-first-fo

0
0
0
0

Darling, no, I don't want a Pilates & Hiit with brunch At Bourglinster Castle (not making that one up BTW). If I'm going to train in a castle I want to train into sword fighting and dragon riding, okay?
Luxembourg ads on social media really don't understand what I want in life 😭

0
0
0
0
0

Leider reiht sich die SPD in die populistische Forderung ein, Social-Media für Kinder/Jugendliche zu verbieten/einzuschränken. Damit erweist sie dem Jugendschutz einen Bärendienst & stärkt BigTech.

Verstehe nicht, warum die Partei Expert:innen nicht einbindet. Da war sie schon mal deutlich weiter.

Positionspapier
SPD fordert Social-Media-Verbot für Kinder unter
14
Stand: 15.02.2026 15:30 Uhr
Länder wie Australien oder Frankreich haben bereits gesetzliche Regelungen. In Deutschland ringt die Politik noch um den richtigen Umgang mit sozialen Medien für Minderjährige. Nun gibt es von der SPD einen konkreten Vorschlag.
0
0
0
0

Doing one of those long blogposts about an interesting that I fear a) either nobody will read or b) everyone will just get mad at me for. Which feels kind of similar to how I felt about writing the "How Decentralized is Bluesky" stuff, which ended up being well received.

It's not about that though!

1
1

🫧 socialcoding.. shared the below article:

Federated private groups (Announce vs Add)

julian @julian@activitypub.space

<p><a href="https://utsukta.org/channel/sk">@<bdi>sk@utsukta.org</bdi></a> mentioned <a href="https://utsukta.org/item/b3b12c30-f9fb-4cbf-9276-1cbf1d27f0de" rel="nofollow ugc">in another thread</a> that the way Hubzilla and threadiverse software handle group discussions is incompatible.</p> <p>It got me thinking about whether that is true. At its core both FEPs (171b and 1b12, respectively) rely on a central "distributor" node to send activities to recipients.</p> <p><a href="https://mitra.social/users/silverpill">@<bdi>silverpill@mitra.social</bdi></a> did further comparisons in thr text of 171b itself:</p> <blockquote> <p><code>Announce</code> activity is used instead of <code>Add</code>.</p></blockquote>

Read more →
0
0
0

AI 거품은 터지지 않았다. 아직도 세계는 AI의 특이점에 도달하기 위해 LLM 모델을 확장 중이고, 이로 인해 램값과 금, 은값은 떨어지지 않고 천정부지로 올랐다. 서기 2036년, 금이 온스당 2만달러를, 은이 온스당 2천달러에 도달하고, DDR5 64기가 램의 가격이 1만달러에 도달하자. 거리에는 과거의 유산을 찾아 배회하는 이들이 나타나기 시작했다. 그리고 사람들은... "살아있는 놈들은 먼지를 털어 중고나라에 올리고, 죽어버린 놈들은 기판을 녹여 금과 은을 캐내라." "예, 보스." 그들을 '램케빈저'라고 불렀다.

RE: https://bsky.app/profile/did:plc:xp5s2asgsq7pfeayl7qrocim/post/3mevvmlwzo22y

0
0