home.social

#resend — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #resend, aggregated by home.social.

  1. 弄了下邮件发送服务,目前在用Webhosting(无限发送额度)和Resend(感觉Resend还算不错,有免费额度,每天100封邮件,每月3000封邮件)

    还了解到了什么是warm up(当然我不会去做,有风险):
    postmarkapp.com/guides/how-to-

    MXRouter都2026年了,活动也下架了,还挂着他的“BLACK FRIDAY 2025!”,点进去是显示售罄然后跳转到原价,“2025 Lifetime 15G Storage:15GB Domains:Unlimited Email Accounts:Unlimited... $1.00/yr”表面上是一年一美元,实际上有248美元的设置费。

    在NetCup重新配置了Beszel,让他启用和发挥了更多功能,还有就是启用:OAuth:Github登录(需要到github.com/settings/applicatio 新增OAuth App)、OTP、MFA
    只有关闭:Hide collection create and edit controls Collections/users右边才有设置按钮,才能配置OAuth、OTP、MFA

    OTP、MFA需要配置SMTP,我试了Webhosting和Resend,都显示超时,才想到NetCup的邮件防火墙是默认开启的,关闭后测试成功
    nc -zv smtp.resend.com 25 Connection to smtp.resend.com (54.205.195.44) 25 port [tcp/smtp] succeeded!
    nc -zv smtp.resend.com 465 Connection to smtp.resend.com (54.205.195.44) 465 port [tcp/submissions] succeeded!
    nc -zv smtp.resend.com 587 Connection to smtp.resend.com (54.157.71.137) 587 port [tcp/submission] succeeded!

    YAML 配置可以导出定义的客户端配置,例如:
    systems:
    - name: ClawCloud Poping Japan/Tokyo
    host: xx.xx.xx.xxx
    port: 45876
    token: xxx-xxx-xxx-xxx
    users:
    - [email protected]

    然后添加了四个服务器,用于这几天迁移的参考,可以在gatus.feddit.social 查看迁移Status

    #beszel #smtp #resend #netcup #OAuth

  2. So glad I didn't go for #cloudflare turnstile as a captcha for my #AI slop blocker extension signup.

    Though, I have to check whether #resend uses cloud flare 🤔 unfortunately email sending was the one thing I couldn't do either from my VPS or from my #homelab

    addons.mozilla.org/en-US/andro

    #aislop #CloudflareDown #Altcha

  3. So glad I didn't go for #cloudflare turnstile as a captcha for my #AI slop blocker extension signup.

    Though, I have to check whether #resend uses cloud flare 🤔 unfortunately email sending was the one thing I couldn't do either from my VPS or from my #homelab

    addons.mozilla.org/en-US/andro

    #aislop #CloudflareDown #Altcha

  4. So glad I didn't go for #cloudflare turnstile as a captcha for my #AI slop blocker extension signup.

    Though, I have to check whether #resend uses cloud flare 🤔 unfortunately email sending was the one thing I couldn't do either from my VPS or from my #homelab

    addons.mozilla.org/en-US/andro

    #aislop #CloudflareDown #Altcha

  5. So glad I didn't go for #cloudflare turnstile as a captcha for my #AI slop blocker extension signup.

    Though, I have to check whether #resend uses cloud flare 🤔 unfortunately email sending was the one thing I couldn't do either from my VPS or from my #homelab

    addons.mozilla.org/en-US/andro

    #aislop #CloudflareDown #Altcha

  6. So glad I didn't go for #cloudflare turnstile as a captcha for my #AI slop blocker extension signup.

    Though, I have to check whether #resend uses cloud flare 🤔 unfortunately email sending was the one thing I couldn't do either from my VPS or from my #homelab

    addons.mozilla.org/en-US/andro

    #aislop #CloudflareDown #Altcha

  7. Alright, well now I'm using #purelymail for an inbox and #resend for sending via #RESTAPI instead of #SMTP

  8. 实例(ControlNet Social Space; 简称CSS)搭建的告一段落了,稍微总结一下:


    1. 选型阶段(
    #ActivityPub 生态对比)

    先稍微 review 一下现在已有的
    #fediverse 平台,选择以 ActivityPub 作为协议的平台,毕竟联邦的话还是得尽可能有更多人用才行。类似于用于实时通讯的 matrix。

    然后评估了
    #Mastodon / #Pixelfed / #Pleroma / #Misskey / #Sharkey 等,确认不同实现可互联互通(Pixelfed ↔ Mastodon 等)。然后偶然得知 #Threads 也是Fediverse中的一员。

    然后,研究“主域 abc.xy 显示身份、实例跑在 social.abc.xy”的可行性。结论是这样不靠谱,所以放弃了。。最终决定考虑到Sharkey比起Misskey有一些不错的feature就选了Sharkey。

    2. 部署与运行

    按官方文档与 docker compose 在用
    #Unraid 系统的 #NAS 上部署 Sharkey。邮件服务器使用free-tier的#Resend

    然后还稍微折腾了一下如何设置管理员。

    3. 联邦互动与内容获取

    学会了站内搜索关注远端用户(用
    @user@domain 或贴对方资料页 URL 解析)。然后是关注 Threads 用户的实操(前提对方开联邦)。

    但是这时候实例里没有什么联合,时间线完全没东西,就考虑有没有订阅别人一整个时间线的方法,好像不太可行。

    4. 存储与图片体积

    了解到 Misskey/系每用户默认 100 MB 网盘,附件都会落地到服务器(非纯外链)。

    而且没办法通过引用外链来渲染图片。试了一下本地上传+压缩,发现会自动压缩到webp,勉强还行。

    6. 二步验证(2FA)故障 & 解决

    刚才开启 2FA 后出现“authentication failed”,连恢复码也无效,日志报:
    Endpoint: i/change-password ... {"message":"authentication failed", ...}

    尝试各种排查均失效,最后只能直接改数据库里的,把 2FA 关掉,然后再重新绑定 2FA和passkey。

    7. 默认不显示在线状态

    发现这个需要在用户设置里修改,并且没找到如何让用户默认就是显示的,只能先放弃了。

    8. 注册与邀请码

    觉得发放多个一次性邀请码麻烦,想找可重复使用的邀请码。结果发现不行,只支持一次性的,感觉除非自己之后魔改一个web服务用于自动发放邀请码并且自动填写,不然想分享到别的群里,确实有点难度。也没有那种私人邀请的链接。

    TODO: 未来感觉还是有很多可以做的

    1. 能够自动探索别的实例的某些方法,找到一些有意思的用户去follow。
    2. 部署一个chat agent用于增强活跃度,但是又不能感觉像是纯骚扰,如何设计是个问题。
    3. 做一个方便remote follow的工具

  9. @forgifuzzbutt Started using #resend since this week on the Free plan. Seems it's just a wrapper around Amazon SES with a 100 message limit per day for the free plan. The UI is nice, but not too advanced

  10. #Resend #Maingun 的开源替代 Plunk

    如果你申请了 AWS SES,可以部署下

    https://s.mt.ci/use-plunk
  11. Plunk: The #OpenSource #Email #Platform

    Plunk is an open-source email platform built on top of #AWS #SES. It allows you to easily send emails from your applications. It can be considered as a self-hosted alternative to services like #SendGrid, #Resend or #Mailgun.

    Features
    - Transactional Emails: Send emails straight from your API
    - Automations: Create automations based on user actions
    - Broadcasts: Send newsletters and product updates to big audiences

    github.com/useplunk/plunk

    #devops