Hello, I'm an open source software engineer in my late 30s living in #Seoul, #Korea, and an avid advocate of #FLOSS and the #fediverse.
I'm the creator of @fedify, an #ActivityPub server framework in #TypeScript, @hollo, an ActivityPub-enabled microblogging software for single users, and @botkit, a simple ActivityPub bot framework.
This patch for @vite is blocking #Fedify's Cloudflare Workers support. They say it'll be included in #Vite 7, but I can't wait that long, so I'm not sure what to do… 🤔
For those concerned that Fedify might drop Deno support in the future: Fedify will continue to support Deno. When I mentioned considering leaving Deno, I didn't mean dropping Deno support; I meant considering using Node.js instead of Deno in Fedify's development environment. In fact, many packages that support Deno (e.g., Hono, Valibot) don't use Deno in their development environments, yet they have no problem supporting Deno. Anyway, please don't worry.
Deno의 침체에 대한 소문은 크게 과장된 것입니다 ------------------------------ - 최근 Deno Deploy, KV, Fresh, 전반적인 회사 및 프로젝트 *모멘텀* 에 대한 비판과 우려가 등장함 - 비판 중 일부는 타당하고, 자체적으로 진행상황을 *충분히 공개하지 않아* 혼란을 키우기도 했으나, 이 소문 및 비판 중 많은 부분은 근거 없는 * 추측이나 사실과 다른 내용*임 - Deno 2 출시(2023년 10월 … ------------------------------ https://news.hada.io/topic?id=21027&utm_source=googlechat&utm_medium=bot&utm_campaign=1834
I've created a GitHub issue to explore this idea further: https://github.com/fedify-dev/fedify/issues/234. Feel free to share your thoughts there if you're interested in contributing to the discussion!
I've been thinking about adding a debug dashboard to #Fedify that shows all #ActivityPub activities being sent and received in real-time. This would include filters by activity type, detailed inspection of JSON-LD content, signature verification details, and retry management for failed deliveries.
As a #fedidev, would you find this useful for troubleshooting federation issues? Any other features that would be helpful in such a debugging tool?
Came across this thoughtful post on the fediverse about the need for ActivityPub-based platforms for public institutions.
This resonates deeply for South Korea too. 🇰🇷 Our public services shouldn't depend on centralized platforms like Naver, Kakao, or Instagram for critical communications.
Projects like @fedify and @botkit could enable our government agencies to build ActivityPub-native services with minimal effort—imagine following 災難安全文字 (emergency alerts) or local traffic updates directly in your fediverse timeline!
Not just convenient, but a matter of information sovereignty. What government communications would you want to follow in the fediverse?
Maybe there are some #Canada based #fediverse devs already working on this, but I so wish there was a publishing platform that was #ActivityPub and #socialweb first, and specifically for public institutions in 🇨🇦
Very similar to how #Ghost works (built-in to core). Followable anywhere on the social web. Bus route updates, water restriction updates, weather alerts...one domain per municipality, difft accts per agency.
This is a national security issue if Musk & Co can cut off our govt comms.
Maybe there are some #Canada based #fediverse devs already working on this, but I so wish there was a publishing platform that was #ActivityPub and #socialweb first, and specifically for public institutions in 🇨🇦
Very similar to how #Ghost works (built-in to core). Followable anywhere on the social web. Bus route updates, water restriction updates, weather alerts...one domain per municipality, difft accts per agency.
This is a national security issue if Musk & Co can cut off our govt comms.
각 개인이 GPT로 지브리 스타일 프사 만드는걸 뭐라고 하고싶진 않다. 오히려 수백만명이 그걸 했다는건 미야자키 하야오가 창조한 스타일의 우수성을 직접적으로 증명한다. 미야자기 하야오 본인이 원한 방식은 아니었지만.
근데 샘 알트만이 저 기능을 광고하는 행동은 정말 꼴보기 싫었다. 일단 미야자키 하야오 본인이 그걸 매우 싫어할거란걸 몰랐을리 없는데도 그냥 강행했다. 여기선 일종의 트롤링 내지는 악의가 느껴지는데, 등산객들이 쌓아놓은 소원돌탑 무너뜨리는 행동과 비슷하다. '미신이나 믿는 멍청이들ㅎㅎ'이 '예술에 인간의 영혼 어쩌고가 들어있다고 믿는 멍청이들ㅎㅎ' 로 바뀐 것이다. 샘 알트만의 메시지는, 우리 OpenAI가 예술의 가치를 재정의했으니 너희들은 거기 적응하라는 거다.
물론 미신도 구라고 인간의 영혼 어쩌고도 구라지만, 그래도 좀 덜 asshole이 될 방법은 언제나 존재한다. 심지어 이미 이룰거 다이루고 돈도 많은 사람에겐 더 선택하기 쉽기까지 하다.
일단... "지브리 스타일로 그려줘"로 유료 제품 프로모션 마케팅을 한 AI 회사는 법으로 족쳐야 한다고 생각함. 아티스트의 스타일 + 지브리라는 회사의 상표를 생성형 AI가 상업적 이용한 거고...
앞으로도 개인 창작자가 만들어낸 독자적인 스타일이 그 권리를 인정 받을 수 있느냐 없느냐의 중요한 고비가 될 것.
미야자키 하야오 할아버지가 샘올트먼의 멱살을 잡아주길 기대함.
@mcc@0xabad1dea all smalltalks do this; the idea is that each class speaks for itself, in the code as “self” and in the documentation as me/I. Twisted tried to adopt this idiom (my dad was a smalltalk programmer in the 80s, and it rubbed off a bit) but everyone else objected so much that it never caught on. I still wish it had.
@mcc@0xabad1dea all smalltalks do this; the idea is that each class speaks for itself, in the code as “self” and in the documentation as me/I. Twisted tried to adopt this idiom (my dad was a smalltalk programmer in the 80s, and it rubbed off a bit) but everyone else objected so much that it never caught on. I still wish it had.
참고로 스프린트 모임이란 함께 모여서 오픈 소스 코딩을 하는 자리인데, 한국 연합우주 개발자 모임의 스프린트에서는 새로운 연합우주 서비스나 앱을 개발하거나, 번역이나 문서에 기여하는 등 연합우주와 관련된 다양한 오픈 소스 활동을 모여서 함께 합니다. 지난 스프린트 모임의 기록을 스프린트 블로그(@sprints.fedidev.kr)에서 살펴보실 수 있습니다.
저는 그날 Fedify, Hollo, Hackers' Pub에 기여하시고자 하는 분들을 옆에서 도와드릴 예정입니다. Fedify, Hollo, Hackers' Pub에 기여해보고 싶었던 분들이 계시다면 모임에 참가하여 저와 함께 스프린트를 해보는 것도 좋을 것 같습니다.
아아~~~ 기여맛집 하나 더! 생겼습니다!!! 플러터로 만드는 마스토돈 클라이언트!! 잘하면 이번 반기안에 출시가 가능할지도!? 여러분의 기여가 함께 한다면 속도가 더 붙을지도 몰라요!?!?
플러터 앱 개인개발하고 있는거 생각보다 속도가 잘 붙고 있어서, 이번 fedidev kr 스프린트 모임에서 기여받을 수 있을 정도는 준비가 가능할 것 같습니다.... SNS 클론코딩이지만 클론코딩이 아닌 실제로 쓸 수 있는 플러터 기반의 소셜앱 만들고 싶은 분들 붙으세요,,
@hongminhee Indeed, East Asia (Japan, South Korea, Taiwan) currently lacks large foundations like NLnet or NGI that specifically fund open source projects.
NLnet primarily receives public funding from the EU's NGI program, while East Asian public sectors have relatively limited awareness and support for FOSS. I believe East Asian communities shouldn't overly expect "angel investments" from their public sectors;
a more realistic path might be: first strengthening through cross-national community collaboration, after which public sectors might follow with support.
We've just submitted an #application to the Sovereign Tech Fund for the #Fedify project! Hoping to further develop and enhance the framework for a more robust federated web.
We're pleased to announce the release of LogTape 0.10.0 today. This version introduces several significant enhancements to improve security, flexibility, and usability.
What is LogTape?
LogTape is a simple, zero-dependency logging library for JavaScript with support for multiple runtimes (Node.js, Deno, Bun, browsers, and edge functions). It features structured logging, hierarchical categories, template literals, and is designed to be used in both applications and libraries.
Key Highlights
New Data Redaction Package
The most notable addition in this release is the new @logtape/redaction package, designed to help protect sensitive information in your logs. This package provides two complementary approaches to redaction:
Pattern-based redaction: Uses regular expressions to identify and redact sensitive patterns like credit card numbers, email addresses, and tokens in formatted log output.
Field-based redaction: Identifies and redacts sensitive fields by their names in structured log data.
The package includes several built-in patterns for common sensitive data types:
Credit card numbers
Email addresses
JSON Web Tokens (JWTs)
U.S. Social Security numbers
South Korean resident registration numbers
Both approaches can be used independently or combined for maximum security. Comprehensive documentation for these features is available in the Data redaction section of the manual.
Timestamp Formatting Improvements
Text formatters now support omitting timestamps entirely from formatted messages. The TextFormatterOptions.timestamp option has been extended to include "none" and "disabled" values, giving you more control over log output format.
Lazy File Sink Option
A new FileSinkOptions.lazy option has been added, allowing file sinks to open files only when actually needed, which can improve resource utilization.
Config Error Detection
The configure() and configureSync() functions now check for duplicate logger configurations with the same category and throw a ConfigError when detected. This prevents unintended overriding of logger configurations.
Acknowledgments
We'd like to thank our external contributors who helped make this release possible:
Ooker for implementing the ability to omit timestamps from formatted messages (#35)
