I think the @fedify project has now reached full maturity. What this means is that all the low-hanging fruit has been addressed, and only the difficult problems remain. 😂
I think the @fedify project has now reached full maturity. What this means is that all the low-hanging fruit has been addressed, and only the difficult problems remain. 😂
It feels like I've taken on too many projects in the last two years. The open source projects I'm currently managing are: Fedify, Hollo, LogTape, BotKit, Hackers' Pub, and Upyo. … That's quite a lot, isn't it?
We're pleased to announce the release of Upyo 0.2.0. Upyo is a cross-runtime email library that provides a unified, type-safe API for sending emails across Node.js, Deno, Bun, and edge functions. With support for multiple email providers through interchangeable transports—including SMTP, Mailgun, SendGrid, and now Amazon SES—Upyo enables seamless switching between email services without code changes.
This release introduces two significant additions: Amazon SES transport support and comprehensive OpenTelemetry integration. These features expand transport options and add production-ready observability capabilities to the library.
Amazon SES Transport
Upyo now includes support for Amazon SES through the new @upyo/ses package. This transport provides AWS Signature v4 authentication with zero external dependencies, maintaining Upyo's commitment to cross-runtime compatibility. The implementation supports both AWS access key credentials and session-based authentication for temporary credentials.
import { SesTransport } from "@upyo/ses";import { createMessage } from "@upyo/core";const transport = new SesTransport({ authentication: { type: "credentials", accessKeyId: process.env.AWS_ACCESS_KEY_ID!, secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY!, }, region: "us-east-1",});const receipt = await transport.send(createMessage({ from: "sender@example.com", to: "recipient@example.com", subject: "Hello from SES", content: { text: "Sent via Amazon SES!" },}));
The SES transport includes regional configuration support, comprehensive IAM role integration through external credential providers, and efficient bulk sending capabilities. Like other Upyo transports, it provides the same consistent interface while leveraging Amazon's proven email infrastructure for reliable delivery at scale.
Configuration sets, message tagging, and rich content features are fully supported, allowing teams to take advantage of SES's advanced tracking and analytics capabilities. The transport handles AWS authentication complexity while maintaining the simple, unified API that Upyo users expect.
import { createOpenTelemetryTransport } from "@upyo/opentelemetry";import { SmtpTransport } from "@upyo/smtp";// Wrap any existing transport with observabilityconst transport = createOpenTelemetryTransport( new SmtpTransport({ host: "smtp.example.com" }), { serviceName: "email-service", metrics: { enabled: true }, tracing: { enabled: true }, });// Use exactly as before - observability is automaticawait transport.send(message);
The OpenTelemetry transport automatically instruments email operations with traces and metrics, tracking delivery rates, latency distributions, and categorizing failures by type. It integrates seamlessly with existing OpenTelemetry infrastructure, supporting both global providers and custom configurations for different deployment scenarios.
Performance optimization features include configurable sampling rates for traces and metrics, ensuring minimal overhead in high-throughput environments. The transport provides automatic resource management through Disposable/AsyncDisposable support and includes specialized monitoring capabilities for bulk email operations, making it suitable for production workloads of any scale.
Getting Involved
We're continuously working to improve Upyo and would love to hear from the community. Whether you're trying out the new Amazon SES transport, implementing observability with OpenTelemetry, or using any of our existing transports, your feedback helps shape the library's future.
If you encounter issues, have feature requests, or want to contribute, please visit our GitHub repository. We also welcome discussions about new transport implementations, documentation improvements, and integration experiences across different runtime environments.
We're pleased to announce the release of Upyo 0.2.0. Upyo is a cross-runtime email library that provides a unified, type-safe API for sending emails across Node.js, Deno, Bun, and edge functions. With support for multiple email providers through interchangeable transports—including SMTP, Mailgun, SendGrid, and now Amazon SES—Upyo enables seamless switching between email services without code changes.
This release introduces two significant additions: Amazon SES transport support and comprehensive OpenTelemetry integration. These features expand transport options and add production-ready observability capabilities to the library.
Amazon SES Transport
Upyo now includes support for Amazon SES through the new @upyo/ses package. This transport provides AWS Signature v4 authentication with zero external dependencies, maintaining Upyo's commitment to cross-runtime compatibility. The implementation supports both AWS access key credentials and session-based authentication for temporary credentials.
import { SesTransport } from "@upyo/ses";import { createMessage } from "@upyo/core";const transport = new SesTransport({ authentication: { type: "credentials", accessKeyId: process.env.AWS_ACCESS_KEY_ID!, secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY!, }, region: "us-east-1",});const receipt = await transport.send(createMessage({ from: "sender@example.com", to: "recipient@example.com", subject: "Hello from SES", content: { text: "Sent via Amazon SES!" },}));
The SES transport includes regional configuration support, comprehensive IAM role integration through external credential providers, and efficient bulk sending capabilities. Like other Upyo transports, it provides the same consistent interface while leveraging Amazon's proven email infrastructure for reliable delivery at scale.
Configuration sets, message tagging, and rich content features are fully supported, allowing teams to take advantage of SES's advanced tracking and analytics capabilities. The transport handles AWS authentication complexity while maintaining the simple, unified API that Upyo users expect.
import { createOpenTelemetryTransport } from "@upyo/opentelemetry";import { SmtpTransport } from "@upyo/smtp";// Wrap any existing transport with observabilityconst transport = createOpenTelemetryTransport( new SmtpTransport({ host: "smtp.example.com" }), { serviceName: "email-service", metrics: { enabled: true }, tracing: { enabled: true }, });// Use exactly as before - observability is automaticawait transport.send(message);
The OpenTelemetry transport automatically instruments email operations with traces and metrics, tracking delivery rates, latency distributions, and categorizing failures by type. It integrates seamlessly with existing OpenTelemetry infrastructure, supporting both global providers and custom configurations for different deployment scenarios.
Performance optimization features include configurable sampling rates for traces and metrics, ensuring minimal overhead in high-throughput environments. The transport provides automatic resource management through Disposable/AsyncDisposable support and includes specialized monitoring capabilities for bulk email operations, making it suitable for production workloads of any scale.
Getting Involved
We're continuously working to improve Upyo and would love to hear from the community. Whether you're trying out the new Amazon SES transport, implementing observability with OpenTelemetry, or using any of our existing transports, your feedback helps shape the library's future.
If you encounter issues, have feature requests, or want to contribute, please visit our GitHub repository. We also welcome discussions about new transport implementations, documentation improvements, and integration experiences across different runtime environments.
사실 ARPANET 이전에도 미국 전역은 물리적인 회선으로 연결되어 있었고, 터미널을 통한 소셜 네트워킹이 활발했다. 나도 ARPANET을 미국 지도 위에 그려진 그래프로 처음 접했고, 최초로 컴퓨터를 연결한 기술이라고만 생각했다. 이 글에서 가장 인상적인 대목: "초기 시분할 네트워크를 무시하면 지난 50년간 미국의 디지털 문화가 어떻게 발전했는가에 대한 이해가 빈곤해지며, 모든 업적을 건국의 아버지들이 가진 천재성으로 돌리는 '실리콘 밸리 신화'에 여지를 준다" https://twobithistory.org/2021/02/07/arpanet.html
Sun 17 August, the final day of PyCon Korea at Dongguk University! Brilliant sessions, fun tutorials, and the Python community awaits you. Long live Python 🐍
