#chuckya — Public Fediverse posts

本实例又宕机了，4.6.0-nightly.2026-03-28+chuckya :chuckya: 你害人不浅（）
这次是整个服务器SSH突然连不上，虽然肯定不会有啥事但是还是去SCP建了一个快照，所以就关机开机服务启动花了几分钟

#Sysadmin #Chuckya #Mastodon

4.6.0-nightly.2026-03-28+chuckya 在我睡觉的时候给我数据库干崩溃了，TimeLine消失，但是现在已经没事了

#Chuckya #Maintain #Sysadmin #Mastodon

4.6.0-nightly.2026-03-28+chuckya 在我睡觉的时候给我数据库干崩溃了，TimeLine消失，但是现在已经没事了

#Chuckya #Maintain #Sysadmin #Mastodon

4.6.0-nightly.2026-03-28+chuckya 在我睡觉的时候给我数据库干崩溃了，TimeLine消失，但是现在已经没事了

#Chuckya #Maintain #Sysadmin #Mastodon

Wanna make #Mastodon fun?

Use the #Chuckya Version ​:blobcathero:​

https://wetdry.world/@chuckya

https://github.com/TheEssem/mastodon

Mitra.Moe.Pub运行正常，唯独和我所在的Mstdn.Feddit.Social交流困难，这是为什么...查阅日志，发现大量500错误...

问题：

数据库迁移 20260311152331 Add collections URL to accounts 没有执行，导致 accounts 表缺少 collections_url 列。
当任何远端实例发来 ActivityPub 活动，Chuckya 尝试刷新对方 Actor 信息时，如果对方的 Actor JSON 里包含 collections 字段，代码就会试图写入这个不存在的列，直接抛出 500 错误。

修复（可是本来昨天就迁移过了）：

docker compose run --rm web rails db:migrate
docker compose run --rm web rails db:migrate:status | grep "Add collections URL"

#mastodon #chuckya #

今天下午，我的 Pixelfed 实例突然无法 fetch 外站的帖子和通知；折腾了一会无法解决，决定从 Pixelfed-Glitch 切换到原版 Pixelfed，期间 Chuckya（Fork Of Mastodon:Glitch-soc）也“莫名其妙”down 掉了。

具体原因：Pixelfed 和 Chuckya 都在 caddy_net 里给数据库起名叫 db，Docker 的内部 DNS 乱了，导致 Mastodon 连接到了 Pixelfed 的 DB（这个问题也出现在 Chuckya 的 Tor 上，需要指定 chuckya-web-1 解决）。

建议：
如果使用caddy-docker-proxy而且使用同一个caddy_net，不要在 docker-compose.yml 里直接用 db 或 redis 这样的通用名，使用 pixelfed-db、pixelfed-redis、chuckya-db、chuckya-redis 更好。

头像消失：
发现头像消失了，原因是 Pixelfed 默认把本站图片、视频、外站头像存储在 S3：

本站图片视频：r2:bucket pixelfed/public/m/_v2/.../.../xxx.
外站头像：r2:bucket pixelfed/cache/avatars/id/xxx.jpg

本站用户头像则存储在本地磁盘。路径也有区别：

Pixelfed-Glitch：docker-compose-state/data/pixelfed/storage/app/public/avatars
Pixelfed：storage/app/public/avatars

所以迁移实例需要运行同步：

rsync -av /旧实例根路径/docker-compose-state/data/pixelfed/storage/app/public/avatars/* /新实例根路径/storage/app/public/avatars/

强制全站 S3 存储：
因为 Pixelfed 默认不允许 filesystem 直接修改，如果一定要将所有文件全部放在 S3，需要在 .env 开启：
DANGEROUSLY_SET_FILESYSTEM_DRIVER=s3
原因：

docker compose exec pixelfed grep FILESYSTEM config/filesystems.php
    'default' => env('DANGEROUSLY_SET_FILESYSTEM_DRIVER', 'local'),

此时头像会出现在r2:bucket pixelfed/public/avatars/id/xxx.jpg
验证输出 s3 即代表切换成功：

docker compose exec pixelfed php artisan tinker --execute="echo config('filesystems.default')"

#S3 #Mastodon #运维 #Docker #Caddy #Pixelfed #Filesystem #DNS #Chuckya #migration

#Chuckya 这个非常功能非常棒

#气泡时间轴 #bubble 是一个由你选择的来自其他服务器的帖子组成的公共时间轴。它可以帮助你的服务器上的用户发现有趣的内容和新的交谈对象，而不会受到来自其他服务器和公共时间轴的干扰。

这样可以直接拉取xxx站点的帖子了，可惜的是#Phanpy 和#elk 等客户端不支持，只能通过访问实例网站使用

#mastodon #activitypub

Phanpy通知不支持chuckya的表情回复！
而elk干脆不显示了23333（

#chuckya #mastodon #phanpy #elk #notifications

大概是Misskey和Chuckya容器名称里都有web；
而torrc设置为：HiddenServicePort 80 web:3000；
所以可能找了misskey-web-1？
改成HiddenServicePort 80 chuckya-web-1:3000就好了。

本站Onion地址：http://7ghveelfljusjkantvsuloyjlmtjfo4xwf4zvcz6iaybfiq7fcbf42id.onion

#tor #proxy #onion #mastodon #chuckya

准备迁移原版Mastodon到glitch-soc或者Chuckya
Preparing to migrate the original Mastodon to glitch-soc or Chuckya

#admin #mastodon #glitchsoc #chuckya

Heyo! I've changed my instance to use #Chuckya instead of plain old #mastodon. It is the software used by wetdry.world and is a for of glitch-soc, which I tried before. I'm looking forwards to trying out all the cool features! Especially, I am happy to have my emoji reactions back <3
And I already got a #Wrapstodon2025! I guess I'm a butterfly : )

#fedi #selfhosting

OK I seem to have found some kinda bug with Chuckya? Or mastodon in general.

1. Open a post in deck that is "404 not found", aka deleted
2. Wait for new posts to come in at top of Home feed (slow refresh must be enabled)
3. Click the "X new item" banner to load the new items
4. Mastodon UI should crash with an error message/no error message/blank screen, requires a refresh.

I assume it's because it's trying to keep the 404'd post loaded or something, while loading new valid posts.

#mastodon #chuckya

#Chuckya is using the #Mastodon API descriptor

adding #Chuckya as a detected platform

Chuckya has been updated to fix a moderate-level security issue with commit 3d497d4082. Admins are recommended to update as soon as possible.

Docker images are currently being built with the tag nightly.2025-08-28-security and will be available shortly.

#chuckya

I finally figured out why my Verified checkmarks refused to show up on my Chuckya / Glitch-Soc Mastodon instance.

I was setting this in my Docker Compose environment section:

environment:
  - MAX_PROFILE_FIELDS=8

Unlike most of the "bonus" glitch-soc env variables which work in the Compose file, apparently that one MUST be set in the .env.production file. Having a line in there with MAX_PROFILE_FIELDS=8 works just fine.

EDIT: It doesn't work because I only put it on the web container. Which means all of the other mastodon containers didn't see that variable. My fault for being lazy... And I wasted way-too-many-hours troubleshooting it...

#Mastodon #GlitchSoc #Chuckya #SelfHosted #SelfHosting

Since it's "a thing" in the Glitch-Soc forks of Mastodon, I added more links to my profile, and rearranged a bit. (Along with other fun stuff like increasing character counts and allowing more poll options...)

In doing so, I appear to have angered the ever-fickle Mastodon Verified Checkmark Gods. ⚡🐘⚡

#Mastodon #GlitchSoc #Chuckya

MathML gets stripped out from HTML posts :(

#MathML #Chuckya

The GIF picker has been rewritten! Not much has changed on the surface besides minor usability improvements, but it has been completely reworked under the hood to bring privacy, security, and stability improvements.

(Note to admins: the picker is now disabled by default, you'll now need to set the TENOR_API_KEY environment variable to a valid Tenor API v2 key to enable it.)

#wdw #chuckya

Spot the new label?

Click on it to get a full list of reactions!

#wdw #chuckya

1/

I feel like this is a milestone - first Mastodon upgrade on this server!

I went a bit spicy too, moving to the #chuckya fork, itself a fork of #glitchsoc

Why? The bubble timeline!

May we have MFM in #Chuckya, pretty please :neocat_pleading_reach:

#chuckya stays winning because it has alt text for your profile picture and profile header #mastodon

Hey so at some point #Mastodon changed the way that notifications work, and I can only clear ALL my notifications instead of SPECIFIC notifications.

I hate this change and I wish it never happened.

Please someone tell me there's a way to revert this; same shit happens with Tusky too...

#mastodon4harris #help #fediverse #chuckya #glitchsoc #fedidev

我刚刚为 #Mastodon 的 fork #Chuckya 提交了简体中文补丁！
https://github.com/TheEssem/mastodon/pull/33
（顺便一提当时合并上游的时候出现了个 bug，也一并修好了，还有 Essem 似乎不咋看 GitHub 通知，花了三天请求通过的…）

Feel that only having 4 attachments max is limiting? The attachment limit is now configurable!

We've set the max attachment limit here on wetdry.world to 12. Some clients may already support this increased limit, as vanilla Mastodon actually started exposing it on the API many months ago!

For admins, this can be configured through the new MAX_MEDIA_ATTACHMENTS and MAX_REMOTE_MEDIA_ATTACHMENTS environment variables.

#wdw #chuckya

A bit of a larger Chuckya feature update: introducing the bubble timeline!

The bubble timeline is a public timeline consisting of posts from different servers curated by your server's admins. Take a look and find interesting posts, new people to meet, and more!

#wdw #chuckya

Thanks to @rosaroja10 for compiling a list of software I didn't have in #FediverseIconography @ https://fediverse.wake.st

I added the following forks: #小森林 (aka #LittleForest, by @mashiro), #kmyblue (by @official), #Decodon (by @frequency), @catodon, #Chuckya (by https://wetdry.world)
...and then we got some new non-forks: #Aardwolf (by @banjofox2), @vidzy and finally @phanpy (which is a client not a server but I think that distinction is mostly meaningless for the purpose of this project)

Thanks to @rosaroja10 for compiling a list of software I didn't have in #FediverseIconography @ https://fediverse.wake.st

I added the following forks: #小森林 (aka #LittleForest, by @mashiro), #kmyblue (by @official), #Decodon (by @frequency), @catodon, #Chuckya (by https://wetdry.world)
...and then we got some new non-forks: #Aardwolf (by @banjofox2), @vidzy and finally @phanpy (which is a client not a server but I think that distinction is mostly meaningless for the purpose of this project)

Thanks to @rosaroja10 for compiling a list of software I didn't have in #FediverseIconography @ https://fediverse.wake.st

I added the following forks: #小森林 (aka #LittleForest, by @mashiro), #kmyblue (by @official), #Decodon (by @frequency), @catodon, #Chuckya (by https://wetdry.world)
...and then we got some new non-forks: #Aardwolf (by @banjofox2), @vidzy and finally @phanpy (which is a client not a server but I think that distinction is mostly meaningless for the purpose of this project)

Thanks to @rosaroja10 for compiling a list of software I didn't have in #FediverseIconography @ https://fediverse.wake.st

I added the following forks: #小森林 (aka #LittleForest, by @mashiro), #kmyblue (by @official), #Decodon (by @frequency), @catodon, #Chuckya (by https://wetdry.world)
...and then we got some new non-forks: #Aardwolf (by @banjofox2), @vidzy and finally @phanpy (which is a client not a server but I think that distinction is mostly meaningless for the purpose of this project)

Thanks to @rosaroja10 for compiling a list of software I didn't have in #FediverseIconography @ https://fediverse.wake.st

I added the following forks: #小森林 (aka #LittleForest, by @mashiro), #kmyblue (by @official), #Decodon (by @frequency), @catodon, #Chuckya (by https://wetdry.world)
...and then we got some new non-forks: #Aardwolf (by @banjofox2), @vidzy and finally @phanpy (which is a client not a server but I think that distinction is mostly meaningless for the purpose of this project)