오늘도 Emacs가 뻗었다.

내부 Emacs API가 GIL을 돌려주지 않는 탓일까? 😥

아 구현은 다른 분(Neal Ziring)이 하셨구나 ㅋㅋ

오늘도 Emacs 쓰다가 알게 되었는데 리처드 스톨만도 Emacs 키바인딩 못참고 1987년에 vi-switch-mode 만들어서 GNU Emacs에 넣었다. (b20cd8dbd051aa561257df965c0d3eaef5df069e)

emacs 동시성은 머 어케 해야하는지 몰겠다... 콜백 범벅이랑 서브 프로세싱 말고 방법이 있나

요새 코딩을 잘 못하구 간간히 리트코드나 풀고 있는데,

• 리트코드를 웹에서 풀다가 불편해서
• 리트코드를 로컬에서 편하게 풀고 싶어서 emacs 플러그인을 짜는데
• emacs 플러그인을 편하게 짜고 싶어서 emacs 테스트 플러그인을 짜는 중...

https://github.com/nyeong/org-test/

Fedify 1.9.0: Security enhancements, improved DX, and expanded framework support

We are excited to announce Fedify 1.9.0, a mega release that brings major security enhancements, improved developer experience, and expanded framework support. Released on October 14, 2025, this version represents months of collaborative effort, particularly from the participants of Korea's OSSCA (Open Source Contribution Academy).

This release would not have been possible without the dedicated contributions from OSSCA participants: Jiwon Kwon (@z9mb1wwj), Hyeonseo Kim (@gaebalgom개발곰), Chanhaeng Lee (@2chanhaeng초무), Hyunchae Kim (@r4bb1t톡기), and An Subin (@nyeongAn Nyeong (安寧)). Their collective efforts have significantly enhanced Fedify's capabilities and made it more robust for the fediverse community.

Origin-based security model

Fedify 1.9.0 implements FEP-fe34, an origin-based security model that protects against content spoofing attacks and ensures secure federation practices. This critical security enhancement enforces same-origin policy for ActivityPub objects and their properties, preventing malicious actors from impersonating content from other servers.

The security model introduces a crossOrigin option in Activity Vocabulary property accessors (get*() methods) with three security levels:

// Default behavior: logs warning and returns null for cross-origin content
const actor = await activity.getActor({ crossOrigin: "ignore" });

// Strict mode: throws error for cross-origin content
const object = await activity.getObject({ crossOrigin: "throw" });

// Trust mode: bypasses security checks (use with caution)
const attachment = await note.getAttachment({ crossOrigin: "trust" });

Embedded objects are automatically validated against their parent object's origin. When an embedded object has a different origin, Fedify performs automatic remote fetches to ensure content integrity. This transparent security layer protects your application without requiring significant code changes.

For more details about the security model and its implications, see the origin-based security model documentation.

Enhanced activity idempotency

Activity idempotency handling has been significantly improved with the new withIdempotency() method. This addresses a critical issue where activities with the same ID sent to different inboxes were incorrectly deduplicated globally instead of per-inbox.

federation
  .setInboxListeners("/inbox/{identifier}", "/inbox")
  .withIdempotency("per-inbox")  // New idempotency strategy
  .on(Follow, async (ctx, follow) => {
    // Each inbox processes activities independently
  });

The available strategies are:

• "per-origin": Current default for backward compatibility
• "per-inbox": Recommended strategy (will become default in Fedify 2.0)
• Custom strategy function for advanced use cases

This enhancement ensures that shared inbox implementations work correctly while preventing duplicate processing within individual inboxes. For more information, see the activity idempotency documentation.

Relative URL resolution

Fedify now intelligently handles ActivityPub objects containing relative URLs, automatically resolving them by inferring the base URL from the object's @id or document URL. This improvement significantly enhances interoperability with ActivityPub servers that use relative URLs in properties like icon.url and image.url.

// Previously required manual baseUrl specification
const actor = await Actor.fromJsonLd(jsonLd, { baseUrl: new URL("https://example.com") });

// Now automatically infers base URL from object's @id
const actor = await Actor.fromJsonLd(jsonLd);

This change, contributed by Jiwon Kwon (@z9mb1wwj), eliminates a common source of federation failures when encountering relative URLs from other servers.

Full RFC 6570 URI template support

TypeScript support now covers all RFC 6570 URI Template expression types in dispatcher path parameters. While the runtime already supported these expressions, TypeScript types previously only recognized simple string expansion.

// Now fully supported in TypeScript
federation.setActorDispatcher("/{+identifier}", async (ctx, identifier) => {
  // Reserved string expansion — recommended for URI identifiers
});

The complete set of supported expression types includes:

• {identifier}: Simple string expansion
• {+identifier}: Reserved string expansion (recommended for URIs)
• {#identifier}: Fragment expansion
• {.identifier}: Label expansion
• {/identifier}: Path segments
• {;identifier}: Path-style parameters
• {?identifier}: Query component
• {&identifier}: Query continuation

This was contributed by Jiwon Kwon (@z9mb1wwj). For comprehensive information about URI templates, see the URI template documentation.

WebFinger customization

Fedify now supports customizing WebFinger responses through the new setWebFingerLinksDispatcher() method, addressing a long-standing community request:

federation.setWebFingerLinksDispatcher(async (ctx, actor) => {
  return [
    {
      rel: "http://webfinger.net/rel/profile-page",
      type: "text/html",
      href: actor.url?.href,
    },
    {
      rel: "http://ostatus.org/schema/1.0/subscribe",
      template: "https://example.com/follow?uri={uri}",
    },
  ];
});

This feature was contributed by Hyeonseo Kim (@gaebalgom개발곰), and enables applications to add custom links to WebFinger responses, improving compatibility with various fediverse implementations. Learn more in the WebFinger customization documentation.

New integration packages

Fastify support

Fedify now officially supports Fastify through the new @fedify/fastify package:

import Fastify from "fastify";
import { fedifyPlugin } from "@fedify/fastify";

const fastify = Fastify({ logger: true });
await fastify.register(fedifyPlugin, {
  federation,
  contextDataFactory: () => ({ /* your context data */ }),
});

This integration was contributed by An Subin (@nyeongAn Nyeong (安寧)). It supports both ESM and CommonJS, making it accessible to all Node.js projects. See the Fastify integration guide for details.

Koa support

Koa applications can now integrate Fedify through the @fedify/koa package:

import Koa from "koa";
import { createMiddleware } from "@fedify/koa";

const app = new Koa();
app.use(createMiddleware(federation, (ctx) => ({
  user: ctx.state.user,
  // Pass Koa context data to Fedify
})));

The integration supports both Koa v2.x and v3.x. Learn more in the Koa integration documentation.

Next.js integration

The new @fedify/next package brings first-class Next.js support to Fedify:

// app/api/ap/[...path]/route.ts
import { federation } from "@/federation";
import { fedifyHandler } from "@fedify/next";

export const { GET, POST } = fedifyHandler(federation);

This integration was contributed by Chanhaeng Lee (@2chanhaeng초무). It works seamlessly with Next.js App Router. Check out the Next.js integration guide for complete setup instructions.

CommonJS support

All npm packages now support both ESM and CommonJS module formats, resolving compatibility issues with various Node.js applications and eliminating the need for the experimental --experimental-require-module flag. This particularly benefits NestJS users and other CommonJS-based applications.

FEP-5711 collection inverse properties

Fedify now implements FEP-5711, adding inverse properties to collections that provide essential context about collection ownership:

const collection = new Collection({
  likesOf: note,  // This collection contains likes of this note
  followersOf: actor,  // This collection contains followers of this actor
  // … and more inverse properties
});

This feature was contributed by Jiwon Kwon (@z9mb1wwj). The complete set of inverse properties includes likesOf, sharesOf, repliesOf, inboxOf, outboxOf, followersOf, followingOf, and likedOf. These properties improve data consistency and enable better interoperability across the fediverse.

CLI enhancements

NodeInfo visualization

The new fedify nodeinfo command provides a visual way to explore NodeInfo data from fediverse instances. This replaces the deprecated fedify node command and offers improved parsing of non-semantic version strings. Try it with:

fedify nodeinfo https://comam.es/snac/

This was contributed by Hyeonseo Kim (@gaebalgom개발곰). The command now correctly handles various version formats and provides a cleaner visualization of instance capabilities. See the CLI documentation for more options.

Enhanced lookup with timeout

The fedify lookup command now supports a timeout option to prevent hanging on slow or unresponsive servers:

fedify lookup --timeout 10 https://example.com/users/alice

This enhancement, contributed by Hyunchae Kim (@r4bb1t톡기), ensures reliable operation even when dealing with problematic remote servers.

Package modularization

Several modules have been separated into dedicated packages to improve modularity and reduce bundle sizes. While the old import paths remain for backward compatibility, we recommend migrating to the new packages:

• @fedify/cfworkers replaces @fedify/fedify/x/cfworkers
• @fedify/denokv replaces @fedify/fedify/x/denokv
• @fedify/hono replaces @fedify/fedify/x/hono
• @fedify/sveltekit replaces @fedify/fedify/x/sveltekit

This modularization was contributed by Chanhaeng Lee (@2chanhaeng초무). The old import paths are deprecated and will be removed in version 2.0.0.

Acknowledgments

This release represents an extraordinary collaborative effort, particularly from the OSSCA participants who contributed numerous features and improvements. Their dedication and hard work have made Fedify 1.9.0 the most significant release to date.

Special thanks to all contributors who helped shape this release, including those who provided feedback, reported issues, and tested pre-release versions. The fediverse community's support continues to drive Fedify's evolution.

For the complete list of changes, bug fixes, and improvements, please refer to the CHANGES.md file in the repository.

@bglbgl gwyng @lionhairdino nix/src/libfetchers/git.cc 보고 왔는데 시스템에 git이 있으면 HEAD 찾아서 쓰는데, git도 없고, 찾으려는 저장소의 ref도 명시되어있지 않으면 master를 기본값으로 쓰네요

@lionhairdino @bglbgl gwyng 둘이 기본 설정이 조금씩 다른 것 같아요. 아까 전 상황에서는, 내부 구현체는 시스템 git과 다르게 master를 먼저 찾아서 빌드에 실패했어요 🫠

#오늘배운거

Nix는 시스템에 git이 있을 때와 없을 때의 동작이 다르다. 왜지... nix 내부에서 쓰는 git 라이브러리랑 git 패키지랑 뭔가 차이가 있나.

Excited to share some great news from the #creative community! Oeee Cafe, a fantastic oekaki #drawing platform, just added #ActivityPub support today. This means all the amazing artwork being created there can now be shared and discovered across the #fediverse, which is such a wonderful step toward connecting creative communities.

Big shoutout to my friend @jihyeokJihyeok Seo for building this platform and bringing it to the fediverse. It's always inspiring to see developers creating spaces for artists and then opening them up to the broader federated community. If you're into digital art or just appreciate seeing creative work, definitely worth checking out what people are sharing from Oeee Cafe on your timeline now. You can find me there at @hongminhee洪兔 if you want to connect!

#oekaki

뭔 작업에 쓸려고 패키징해서 깔았는데 정작 패키징하다가 뭐 할려고 했는지는 까먹었다

#오늘배운거

오늘은 cursor-agent를 써보고 싶어서 깔아보려고 했는...데... nix라서 패키징을 했고 makeWrapper 사용법도 배웠다

오이카페에 ActivityPub 지원이 들어갔습니다. 이제 좋아하는 작가나 커뮤니티의 새 그림을 연합우주에서도 받아 보세요!

작가 프로필이나 커뮤니티 메인 페이지에서 ActivityPub 핸들을 확인할 수 있습니다.

인용된 그림은 ActivityPub 연동을 도와주신 @hongminhee洪 民憙 (Hong Minhee) 님이 오이카페 초창기에 그려 주신 고양이 그림입니다. 감사합니다!

Robert C. Martin이 트위터에 짧게 올리는 영상이 영어 공부 하기 좋을 것 같아서 종종 듣고 모르는 표현 정리하고 있는데... 기술 용어가 아니라 미국식 키배 표현만 느는 것 같기도 하고...

진짜 미치겠네 왜 같은 WebDAV 서버에 요청보내는데 iOS랑 macOS랑 웹브라우저랑 결과가 다르지

하 오늘은 작업하는데 LLM이 자기 맘에 안 든다고 홈서버 tailscaled를 꺼버렸다... 집에 가야지...

않이 깜짝이야 왜 갑자기 비밀번호에 접근하세요

... 지난번에 이야기했었는데 warp 터미널로 뭐 하다가 틀리면 가끔 기계한테 상황을 물어보는데 얘가 상황 분석한다고 커맨드 막 넣는걸 보니 오싹하더라고요. 그리고선 “이 명령으로 해결할수있어 할래? (y/n)" 이러는데 ....... 약간 스카이넷 작동시키는 느낌 .....

https://hackers.pub/@nyeong/01989d45-41f1-7bfa-8f0a-f46fbe8fbaba

않이 에이전트가 ssh로 이러는 건 좀 무서운데...

We're thrilled to announce Fedify 1.8.1, a mega release made possible through the incredible efforts of contributors from South Korea's #OSSCA (Open Source Contribution Academy). This release marks a significant milestone in #Fedify's development, bringing major architectural changes, new packages, and numerous enhancements across the board.

Note: Version 1.8.0 was skipped due to a versioning error.

🎉 Major Milestone: Monorepo Architecture

Fedify has been restructured as a #monorepo, consolidating all packages into a single repository with unified versioning. This change streamlines development and ensures all packages are released together with consistent version numbers.

Consolidated Packages

All existing Fedify packages now live under one roof:

• @fedify/fedify — Main library
• @fedify/cli — CLI toolchain
• @fedify/amqp — AMQP/RabbitMQ driver
• @fedify/express — Express integration
• @fedify/h3 — h3 framework integration
• @fedify/postgres — PostgreSQL drivers
• @fedify/redis — Redis drivers

🆕 New Packages

This release introduces four new packages to the Fedify ecosystem:

• @fedify/elysia — Elysia integration for Bun-powered applications
• @fedify/nestjs — NestJS integration for enterprise Node.js apps
• @fedify/sqlite — SQLite driver compatible with Bun, Deno, and Node.js
• @fedify/testing — Testing utilities with mock Federation and Context classes

@fedify/fedify

Custom Collection Dispatchers

A powerful new feature that allows you to create custom collections beyond the standard ActivityPub collections. This enables implementation of domain-specific collections while maintaining federation compatibility.

Contributors: ChanHaeng Lee [#310, #332]

• Added comprehensive types and interfaces for custom collection handling
• New methods on Federatable interface: setCollectionDispatcher() and setOrderedCollectionDispatcher()
• Added getCollectionUri() method to the Context interface
• Full support for paginated custom collections

Compare-and-Swap (CAS) Support for KV Stores

Key–value stores now optionally support CAS operations for atomic updates, enabling optimistic locking and preventing lost updates in concurrent environments.

• Added optional KvStore.cas() method
• Implemented in MemoryKvStore and DenoKvStore
• Useful for implementing distributed locks and counters

Fediverse Handle Utilities

New utility functions make working with #fediverse handles more convenient.

Contributors: ChanHaeng Lee [#278]

• parseFediverseHandle() — Parse handles into components
• isFediverseHandle() — Validate handle format
• toAcctUrl() — Convert handles to URLs
• FediverseHandle interface for type safety

Enhanced HTTP Request APIs

Contributors: Lee ByeongJun [#248, #281], Hyunchae Kim [#51, #315]

• Added LookupWebFingerOptions.maxRedirection option for controlling redirect behavior
• APIs now support AbortSignal for request cancellation
• New DocumentLoaderOptions interface
• Added signal options to LookupObjectOptions, LookupWebFingerOptions, and DoubleKnockOptions

@fedify/cli

New Commands and Enhancements

The CLI has received significant improvements thanks to our OSSCA contributors:

fedify webfinger Command

Contributors: ChanHaeng Lee [#260, #278], KeunHyeong Park [#311, #328]

Look up WebFinger information for any fediverse resource:

• Supports handles (@user@server) and URLs
• --user-agent option for custom User-Agent headers
• --allow-private-address for local testing
• --max-redirection to control redirect following

fedify nodeinfo Command

Contributors: Hyeonseo Kim [#267, #331, #168, #282, #304]

Replaces the deprecated fedify node command with improved terminal rendering.

Enhanced fedify lookup Command

Contributors: Jiwon Kwon [#169, #348, #261, #321]

• Terminal-specific image display for Kitty, WezTerm, Konsole, Warp, Wayst, st, and iTerm
• -o/--output option to save results to files

Improved fedify inbox Command

Contributors: Hasang Cho [#262, #285], Jang Hanarae [#191, #342]

• --actor-name and --actor-summary options for customizing temporary actors
• Now displays object types contained in activities

fedify init --dry-run

Contributors: Lee ByeongJun [#263, #298]

Preview project initialization without creating files.

Better Terminal Support

Contributors: Cho Hasang [#257, #341]

Correctly handles color output based on TTY detection and NO_COLOR environment variable.

@fedify/elysia

Contributors: Hyeonseo Kim [#286, #339]

New Elysia integration brings Fedify to Bun-powered applications with a simple plugin interface:

import { Elysia } from "elysia";
import { fedify } from "@fedify/elysia";

const app = new Elysia()
  .use(fedify(federation, { /* options */ }))
  .listen(3000);

@fedify/nestjs

Contributors: Jaeyeol Lee [#269, #309]

Enterprise-ready NestJS integration with dependency injection support:

import { FedifyModule } from "@fedify/nestjs";

@Module({
  imports: [
    FedifyModule.forRoot({
      kv: new MemoryKvStore(),
      queue: new InProcessMessageQueue(),
      origin: "https://example.com",
    }),
  ],
})
export class AppModule {}

@fedify/sqlite

Contributors: An Subin [#274, #318]

SqliteKvStore implementation compatible across all major JavaScript runtimes:

import { SqliteKvStore } from "@fedify/sqlite";

const kv = new SqliteKvStore("./fedify.db");

@fedify/testing

Contributors: Lee ByeongJun [#197, #283]

Comprehensive testing utilities with mocking support for Fedify applications:

import { MockFederation, MockContext } from "@fedify/testing";

const mockFederation = new MockFederation();
const mockContext = new MockContext();

// Track sent activities with full metadata
// Support custom path registration
// Multiple activity type listeners

🙏 Acknowledgments

This release represents an extraordinary community effort, particularly from the participants of South Korea's OSSCA (Open Source Contribution Academy) (Note: page in Korean). We extend our heartfelt thanks to all contributors:

Core Contributors

• ChanHaeng Lee (@2chanhaeng초무) — Custom collections, fediverse handles, WebFinger command
• Lee ByeongJun (@joonnotnotJoon) — WebFinger redirections, dry-run, testing utilities
• Hyunchae Kim (@r4bb1t) — AbortSignal support
• Hyeonseo Kim (@gaebalgom개발곰) — Elysia integration, nodeinfo command
• Jaeyeol Lee (@kodingwarriorJaeyeol Lee) — NestJS integration
• An Subin (@nyeongAn Nyeong (安寧)) — SQLite driver
• Jiwon Kwon (@z9mb1wwj) — Terminal image display, output options
• Hasang Cho (@crohasang크롸상) — Color output handling, actor customization
• Jang Hanarae (@meneleHanal Ae) — Activity object type display
• KeunHyeong Park (@w8385박근형) — WebFinger redirect options

Test Infrastructure Contributors

• Oh Daeun (@ooheundaoed) — Fixed PostgreSQL test race conditions [#346, #350]
• Song Hanseo (@songbirds) — Test stability improvements for Redis and code generation [#344, #347]
• Kim Jonghyeon (@woaol벨) — CLI version management and documentation fixes [#306, #329, #330, #343]

Your contributions have made Fedify stronger and more versatile than ever. The OSSCA program's support has been instrumental in achieving this milestone release.

Migration Guide

Updating from Previous Versions

If you're using separate Fedify packages, update all packages to version 1.8.1:

{
  "dependencies": {
    "@fedify/fedify": "^1.8.1",
    "@fedify/cli": "^1.8.1",
    "@fedify/express": "^1.8.1"
  }
}

All packages now share the same version number, simplifying dependency management.

Breaking Changes

There are no breaking changes in this release. All existing code should continue to work without modifications.

What's Next

With the monorepo structure in place and new integrations available, we're excited to continue improving Fedify's developer experience and expanding its capabilities. Stay tuned for more updates, and thank you for being part of the Fedify community!

For detailed technical information about all changes, please refer to the full changelog.

Fedify is an open-source project that helps developers build federated server applications powered by ActivityPub. Join us on GitHub or Discord to contribute or get help!

#opensource #fedidev

누가 내 Cursor에 Prompt Injection Attack을 했나...? 🤔

@hongminhee洪 民憙 (Hong Minhee) 펍냥이 잘 쓰겠습니다 ㅋㅋㅋ

We're thrilled to highlight five outstanding contributions from the Korean Open Source Contribution Academy (#OSSCA) program participants who have been working on #Fedify! Their dedication and effort have significantly enhanced our #ActivityPub server framework.

First up is @nyeongAn Nyeong (安寧) with his monumental #318 PR, implementing a SQLite-based key–value store to address #274. This contribution adds the SqliteKvStore class with full cross-runtime support for Node.js, Deno, and Bun through the new @fedify/sqlite package. His implementation includes atomic operations, TTL support, comprehensive test coverage, and careful attention to SQL injection prevention. This enables developers to use SQLite as a persistent storage backend while maintaining compatibility with Fedify's existing KvStore API—a crucial feature for production deployments!

Next, @crohasang크롸상 delivered an excellent quality-of-life improvement with #341 PR, fixing #257. He enhanced the CLI to properly respect TTY status and the NO_COLOR environment variable, implementing intelligent color control across all CLI commands. The solution involved switching from @cliffy/ansi/colors to @std/fmt/colors, creating a helper function using Deno.inspect() to handle object formatting, and ensuring colors are correctly disabled when output is redirected to files. This makes the CLI much more pipe-friendly and suitable for automated workflows!

@meneleHanal Ae contributed a thoughtful enhancement with #342 PR, addressing #191. She updated the fedify inbox command to display not just the activity type, but also the type of object contained within each activity—transforming output like "Create" into the more informative "Create(Note)" or "Undo" into "Undo(Follow)". This seemingly simple change required making the display function asynchronous to fetch the enclosed objects, significantly improving the debugging experience for developers!

@woaol벨 tackled an important developer experience issue with #329 PR, solving #306. Previously, the fedify init command would often install outdated versions of Fedify packages like @fedify/redis because version numbers were hardcoded in the CLI. They created a getLatestVersion() function that dynamically retrieves package versions from local metadata files, ensuring that developers always get the latest versions of all Fedify packages when initializing a new project. This improvement includes comprehensive test coverage and eliminates the frustration of starting a project with outdated dependencies!

Finally, @kodingwarriorJaeyeol Lee made a significant contribution with #309 PR, implementing #269—NestJS integration! They created the @fedify/nestjs package with a FedifyModule that seamlessly integrates Fedify into NestJS applications. This includes proper middleware implementation, dependency injection support through NestJS's module system, and compatibility with both CommonJS and ESM environments. This opens up Fedify to the large NestJS developer community, making it easier than ever to build ActivityPub-enabled applications with this popular enterprise framework!

These contributions showcase the incredible talent and dedication of the OSSCA participants. From core infrastructure improvements to developer experience enhancements, each contribution makes Fedify better for the entire community. Thank you all for your hard work and welcome to the Fedify contributor family! 🚀

We're looking forward to seeing more amazing contributions from the OSSCA program and the broader community. If you're interested in contributing to Fedify, check out our GitHub repository and join us in building the future of federated social web! 🌟

#opensource #fedidev #fediverse

코딩 에이전트 쓸 때마다 인간의 두뇌가 위대한 걸 새삼 깨닫는다. 특히 에이전트에게 맥락 꼬박꼬박 주입할 때마다 맥락을 능동적으로 획득하고 장기적으로 기억하고 순간적으로 인출해내는 인간의 능력이 대단한 것 같음

DBMS 같은 데에서 파일을 관리 할 때엔 항상 4096 바이트 단위의 페이지 형태로 관리합니다. 왜그럴까요? 여러가지 이유가 있는데, 보통은 OS도 4096 바이트 단위로 파일 시스템을 관리하기 때문입니다. 그래서 캐시 같은 OS의 여러 가속 장치들의 도움을 받을 수 있죠.

근데 정말로 그럴까요?

그게 궁금해서 직접 한번 페이지 파일 매니저를 구현해서 실험해봤습니다. 통계적으로 유의하게 빠르네요.

와! 런타임을 세 개나 지원하니까 테스트 통과하는 쾌감도 세 배!

Nix 설정 건들다가 (1) brew cask로 설치된 앱들을 못 찾고 (2) 메인 웹 브라우저로 쓰던 Zen의 모든 설정이 날아갔다 🙃

(1)은 복구했는데... (2)는 이렇게 된 김에 파폭으로 돌아갈까 고민중

이 편지는 미래에서 최초로 시작되어 -1년에 한 바퀴 돌면서 받는 사람에게 행운을 주었고 지금은 당신에게로 옮겨진 이 편지는 -4일 안에 당신 곁을 떠나야 합니다. 영국에서 did:plc:ppk763j7o2wkinvzuqx4orrb이라는 사람은 2026년에 이 편지를 받았습니다. 어쩌고

claude max를 구독하면 월 200$씩 깨진다는 사소한 문제가 있지만, 별도 과금이 없어 인간성을 지킬 수 있습니다.

API 기반 에이전트에서 요금제 기반 에이전트로 넘어와, 이제 마음껏 감사인사를 하는 풍부한 인간이 되었습니다.

미리미리 아부 떨어서 기계화 시대를 대비하자

@makaHyeonseong Yang go를 몰라서 찾아보니 if-else가 expression이 아니군요 🤔 expression이기만 해도 삼항연산자 대체할 수 있을텐데 아깝네요

"내장 라이브러리"라는 말 조금 징그러운 것 같아

하지만 scrollableWM 쓰고 싶은데... 아사히 깔아야하나

PaperWM.spoon 미묘하게 굼뜨고 사용성이 좋지 못해서 싹 지웠다... Hamerspoon 위에서 도는 거라 한계가 있는 듯.

특히 최근에 Wezterm이랑 같이 쓰면 Wezterm이 뻗는데 (왜인지는 모르겠다) PaperWM.spoon 구조 상 하나가 뻗으면 창 정렬이랑 포커싱이 엉망이된다 🙃

@nyeongAn Nyeong (安寧) 혹시 fetchTarball을 쓰지 않고 emacs-overlay를 flake inputs에 추가하는 건 해보셨나요? 아니면 fetchFromGithub로 받아와도 괜찮습니다. 아무리 sha256을 지정해도 fetchTarball은 이걸 다운받은 tarball을 검증하는 용도로 사용하는거지 fixed-output derivation 처럼 outpath를 찾는데 사용하지는 않을 거예요. cache TTL이 지나거나 nix daemon을 껐다 켜면 다시 다운받을 거예요.

이게 왜 재빌드를 유발하는지는 저도 지금 명확히 설명이 어렵지만 fetchTarball의 결과값이 derivation나 path가 아닌 스트링이라서 생기는 미묘한 차이점이 있기는 합니다. 일례로 remote 빌딩을 하기 위해 prerequisite들을 빌드 서버에 넘기는데 fetchTarball로 받아온 애들은 prerequisite closure에 포함이 안됐던 걸로 기억해요. 목적하는 derivation이 remote에서 직접 nix 표현을 eval 해서 얻어진 경우는 (eval 시 fetch를 해서 store에 담기 때문에) 문제가 없지만 그렇지 않은 경우는 존재하지 않는 store path에 대한 에러가 날 수 있거든요.

하여튼 다른 건 딱히 눈에 띄는게 없어 보여서 fetchTarball만 의심하게 되네요.

@jhhuhJi-Haeng Huh 아하 저도 명확히 내부를 이해하고 있지는 않은데, fetchTarball의 결과가 derivation이 아니라면 제가 의도한 상황과 미묘하게 달르네요 🤔 fetchFromGitHub 한 번 써보겠습니다 감사합니다 🙇

@jhhuhJi-Haeng Huh https://github.com/nyeong/.dotfiles/blob/684e1f1f41a8d61c9fc680f2429b5142cdeadfda/packages/emacs/default.nix#L18-L21

감사합니다! emacs-overlay를 fetchTarball로 가져오고 있습니다 👀

nix update 할 때마다 emacs 다시 빌드하는데 이거 어케 캐싱하지 🤔 input 의존성은 똑같은데 왜 빌드를 또 하지...

@2chanhaeng초무 저도 아직 프로젝트 파악이 안 되어있어서 맥락 적어보이는 #274를 집었어요 ㅋㅋ

왜 wezterm 열고 한 10초만 지나면 이 친구가 응답이 없지 🤔

MoonBit Monthly vol. 1 is out!🚀
See what’s new in MoonBit after our Beta release. 🥳
Full Updates：https://moonbitlang.com/weekly-updates/2025/07/15/index

지구 자전속도 너무 빠른거가틈

@tedpool테드풀 @kodingwarriorJaeyeol Lee @gaebalgom개발곰 @nyeongAn Nyeong (安寧) @joonnotnotJoon @crohasang크롸상 @z9mb1wwj @r4bb1t톡기 @2chanhaeng초무 @cosmic_elevatorSooji Choi @ooheunda @woaol벨 @meneleHanal Ae @devomdv @eottabom @hjleee93hyeonjeong lee 오늘 발대식에서 만나 뵈어서 반가웠습니다! 다시 한 번 앞으로 잘 부탁드립니다! 화이팅!

으악 또 몰래 껴넣었네? 너 어디살아

gemini-cli는 이상한 맥락을 기억해서 나랑 자꾸 다툰다...

자꾸 A를 B로 바꿔서 내가 A로 돌려놓고 C를 고쳐달라고 하면 또 C를 고치면서 A도 B로 은근슬쩍 바꿔둠

셸에 쳐야할 git status 명령어를 Claude Code에게 보내서 토큰을 낭비하는 모습, 스크린에 점묘화. 568 (H) x 1264 (W) px.

typ 파일 두 개 되니까 알아서 flake.nix에서 빌드 스크립트도 수정하고... 굉장한데

#claude code CLI UI도 맘에 들고 todo로 할일 정리해서 순차적으로 진행하는 것도 좋고 결과물도 맘에 든다