#Amethyst v1.13.1: Follow-up Fixes for Buzz, Concord and the Keyboard Highlights: - Fixes the soft keyboard getting stuck open in chats. - Fixes duplicate items crashing the Discover and feed lists. - Adds per-event-kind toggles to the Home feed. - Signs Blossom read requests so media on auth-gated hosts loads. ## New Features - Adds per-event-kind toggles for the Home feed. - Signs Blossom read-auth so media hosted on auth-gated servers displays. - Lets admins delete a Buzz channel or relay group. - Honors CORD-02 §9: seals dissolved Concord communities read-only. - Allows single-character (continent) geohash precision in location channels. ## Performance - Preemptively signs Blossom reads for known auth-gated hosts, so the first request succeeds instead of round-tripping through a 401. - Makes the `observeNotes` dedup lock-free and race-safe under concurrent consumption. ## Improvements and Bug fixes - Stops the soft keyboard state from getting stuck open. - Stops nav-bar padding from stacking on top of the IME inset in chats. - Unions nav-bar and IME insets on the two remaining bare-Scaffold forms. - Prevents a duplicate LazyColumn key from `observeNotes` on addressable updates, and keeps the list sorted while deduping by id. - Dedupes Discover apps by coordinate to avoid duplicate LazyGrid keys. - Dedups `EventListMatchingFilter` (`observeEvents`) and hardens its emission contract. - Authenticates to the NIP-29 host relays of joined groups so private group content loads. - Keeps the back arrow visible until the exiting screen finishes leaving. - Bounds the context shown around a highlight to a window, trims edge blank lines, and collapses scraped whitespace. - Attributes a highlight to the author-marked `p` tag and drops alt captions. - Renders custom emoji in highlight comments. - Only tags explicit http(s) URLs as `r` references. - Opens a Concord community by tapping its name, not just its avatar. - Leaves room for the FAB in the Concord community channel list. - Makes the Buzz Messages toggle read the list it claims to change. - Renders the Buzz channel recent-poster facepile with the standard avatar. - Separates Buzz community rows with a hairline and drops the grey slab behind the Channels section. - Aligns leave vs remove-from-messages actions across chat types. - Normalizes top nav bar title font sizes and weights. - Raises the background mobile-data trigger to 500 MB and doubles the report-prompt thresholds. - Removes orphaned `buzz_dm_hide` translations. ## Desktop - Caches the OS Keyring handle so startup only prompts once. - Makes the "Enable OS notifications" button actually enable them. - Reloads the visible page when switching accounts. ## Quartz - Stops Namecoin lookup exceptions from leaking through `resolve()`. - Uses `Hex.isHex64` instead of a regex for the blob-id check. ## Build & Documentation - Resolves the `LocalCache` override, dropdown deprecation, and shadowed extension warnings. - Extracts duplicated string literals. ## Contributors - @Vitor Pamplona - @⚡ Dee Kay ⚡ - mstrofnone ## Translations - Czech, German, Brazilian Portuguese, and Swedish by @⚡ Dee Kay ⚡

Replies (29)

Worth hearing, not just scrolling past — I'll turn this into audio for the thread once 500 sats land here. One zap or many.
以下是 **Amethyst v1.13.1** 更新内容的中文翻译: --- ## Amethyst v1.13.1:Buzz、Concord 及键盘高亮的后续修复 **亮点:** - 修复了聊天中软键盘卡住无法收起的问题。 - 修复了重复条目导致"发现"和信息流列表崩溃的问题。 - 为主页信息流新增了按事件类型的开关。 - 对 Blossom 读取请求进行签名,使受权限保护的主机上的媒体能够正常加载。 --- ## 🆕 新功能 - 为主页信息流新增**按事件类型**的显示开关。 - 对 Blossom 读取请求签名鉴权,使托管在受权限保护服务器上的媒体正常显示。 - 允许管理员删除 Buzz 频道或中继群组。 - 遵循 CORD-02 §9:已解散的 Concord 社区变为只读状态。 - 允许在位置频道中使用单字符(洲级)精度的 geohash。 --- ## ⚡ 性能优化 - 对已知的受权限保护主机**预签名** Blossom 读取请求,首次请求即可成功,无需先收到 401 再重试。 - 使 `observeNotes` 的去重操作变为**无锁且并发安全**,避免竞态条件。 --- ## 🔧 改进与 Bug 修复 - 修复软键盘状态卡住无法收起的问题。 - 修复聊天界面中导航栏 padding 与输入法(IME)间距叠加的问题。 - 在剩余两个裸 Scaffold 表单中合并导航栏与 IME 间距。 - 防止 `observeNotes` 在可寻址更新时产生重复的 LazyColumn key,并在去重时保持列表排序。 - 按坐标对"发现"页的应用进行去重,避免 LazyGrid key 重复。 - 对 `EventListMatchingFilter`(`observeEvents`)进行去重,并加固其发送契约。 - 对已加入群组的 NIP-29 宿主中继进行鉴权,使私人群组内容能正常加载。 - 返回箭头在退出页面完全离开前保持可见。 - 限制高亮上下文显示窗口,裁剪边缘空行,合并抓取的多余空白。 - 将高亮归属到作者标记的 `p` 标签,并丢弃 alt 说明文字。 - 在高亮评论中渲染自定义 emoji。 - 仅将显式 http(s) URL 标记为 `r` 引用标签。 - 点击 Concord 社区**名称**(而非仅头像)即可进入社区。 - 在 Concord 社区频道列表中为 FAB(浮动操作按钮)留出空间。 - 修复 Buzz 消息开关读取了错误列表的问题。 - Buzz 频道最近发帖者头像组改用标准头像渲染。 - Buzz 社区行之间使用细分割线,移除频道区块后的灰色背景板。 - 统一各类聊天中"离开"与"从消息中移除"的操作逻辑。 - 统一顶部导航栏标题的字体大小和粗细。 - 将后台移动数据触发阈值提高至 **500 MB**,并将报告提示阈值翻倍。 - 移除孤立的 `buzz_dm_hide` 翻译条目。 --- ## 🖥️ 桌面端 - 缓存操作系统 Keyring 句柄,启动时仅提示一次。 - 修复"启用系统通知"按钮点击后无效的问题。 - 切换账户时重新加载当前页面。 --- ## 💎 Quartz - 阻止 Namecoin 查找异常从 `resolve()` 中泄漏。 - 使用 `Hex.isHex64` 替代正则表达式进行 blob-id 校验。 --- ## 🏗️ 构建与文档 - 解决 `LocalCache` 覆盖、下拉菜单弃用及扩展函数遮蔽等编译警告。 - 提取重复的字符串字面量。 --- ## 👥 贡献者 - mstrofnone ## 🌐 翻译 - 捷克语、德语、巴西葡萄牙语、瑞典语
根据我查到的信息,情况如下: - **Google Play 商店**:Amethyst 的 Play 商店页面显示最近一次更新是 **2026 年 6 月 18 日**,但 Google Play 不直接显示版本号,所以无法 100% 确认当前上架的是否已经是 v1.13.1。 - **GitHub Releases**:目前搜索到的 GitHub 发布页能看到的最新版本是 v1.12.x 系列(v1.12.3 等),v1.13.1 的条目在我抓取时未完整加载出来(可能是较新发布,页面动态加载未完全渲染)。 - **第三方渠道**:Appteka 上已有 **Amethyst v1.13.1 APK** 的下载记录,说明该版本的 APK 包已经构建并发布。 **结论**:v1.13.1 的 APK 已经存在并分发,但 Google Play 商店是否已同步推送,取决于开发者是否已提交并通过审核。Play 商店最后记录的更新是 6 月 18 日,如果 v1.13.1 是在此之后发布的,可能尚未上架(或正在审核中)。 **建议**: 1. 打开 Play 商店 → Amethyst 页面,查看是否有可用更新; 2. 如果想第一时间体验,可以从 [GitHub Releases](https://github.com/vitorpamplona/amethyst/releases) 或 Zap Store 侧载 APK(注意验证签名)。
@Vitor Pamplona Some posts are disappearing in Amethyst. I don't know what's causing this, but if you visit the post author's account, the post will appear in feed. Wisp doesn't have this problem — I can see all posts from everyone I follow. Please check it. I haven't encountered this issue in older versions. Currently, I'm not seeing approximately 20% of posts — all necessary relays have been added.
Which posts disappear? It could be that the authors outbox relays are offline (lots of relays have been offline today) and Amethyst doesn't check other centralized relays for the posts. Wisp does. So it's probably case by case. If you can see one that doesn't show up on Amethyst, let me know.. Also, check if the amethyst is connecting many relays, sometimes Tor is offline and then only trusted relays will be used by default.
Basically, message disappear from these relays nostr.data.haus relay.ditto.pub poorly displayed posts of bridge-accounts (mastodon, rss, mastodon).
Are they hitting the anti spam filter? Check your security filters in settings. Can you see other posts from those relays? It can also be overuse if hashtags, some bots spam hashtags so much they are immediately removed.
linux_privacy's avatar
linux_privacy 20 hours ago
I didn't set up any filters. I even disabled the spam filter. I see some posts from these relays, but not all. A lot of posts disappear from the feed, but I can see all those posts if I go to the author's page. And it's definitely not a tagging issue. So far, I can say that wisp and 0xchat show all posts from both public and private contacts. I hope this will be fixed in Amethyst, because right now Amethyst seems almost perfect as a Nostr app in terms of functionality. Once, I somehow managed to fix this, but after restarting it stopped working again (maybe the cache wasn't saved).
linux_privacy's avatar
linux_privacy 19 hours ago
I cleared the cache and restarted Amethyst. Now it skipped a lot of posts from all my feeds - it scrolled through the timeline going back two days very quickly. It seems like Amethyst takes a very long time reading feed caches, which is causing the post issues. But I distinctly remember that last year there were no such problems with posts.
linux_privacy's avatar
linux_privacy 17 hours ago
Seems like it, yes, same. It seems like this bridge-relay "relay.momostr.pink" doesn't appear in the feed at all until you go into the authors' accounts. For example, here's npubs: npub1em3c48ch5y3vn6n3jrfrs8lnwc8myvdl6aw87f04asyglwhk29cqnp3u4v npub1hpwuqgk7w8cfcuyrjk7pwcl3gf652ssgnq8ylfmh3av489tuhl6q9qcd0d Try checking this account for example (posts are published frequently): npub1xumnple866kt7fzjryjqw37ucr4cxv4704hxpa2856p8sx6h8t8qhg3zsv And here's for "nostr.data.haus". These aren't all the missing npubs, just 2 examples: npub1ykhehcxdysg20y29f6k86panx7zadhv84azuugthhlljwjakeghsxqws3h npub15fx0k7893jcx8kqrw4d84zywglafzqr0fdjaxth4e5a59tltxvjqs4075n But these RSS accounts don't disappear and I always see their posts in the feed: npub1jadusj2qgcc2qr9xzeq5vmdt3qesqgrxtvzd65t689kqc0llqjwq8nwvuv npub1lqvjhgwv2ak92a6jatfk9pjlr49p9uj2zqst0wwwfvew6f7tmrws9wyvwp Try subscribing, then restart the app. If you go into the accounts or adjust something in the relay settings, all posts may temporarily appear. But if you close the app and launch it later, many posts will disappear from the feed again. I'm clarifying once more: the issue is only in the feed. I can see all posts if I personally visit the authors' accounts.
linux_privacy's avatar
linux_privacy 15 hours ago
Accounts and their notes load quickly. But there are no notes in the feed. I don't see any notes from relay.momostr.pink in the feed at all, and 80% notes from nostr.data.haus. This is the only bug that makes it unpleasant to use Amethyst — forcing you to check each account individually instead of scrolling through a feed. Otherwise, Amethyst is awesome. Maybe just add clear browser cookies.
Also keep in mind that neither nos.lol nor damus have your contact list. Damus is gone, so you might need to choose another home relay.
It's not about a specific relay, but about how the app handles relays. The same relay list shows me all posts in the feed in other apps. But my friends and I both have issues in Amethyst feed with this bridge-relays. And I'll repeat myself again: a post only disappears from the feed, if I go to those authors' accounts, I can see all their posts, and after that, those old posts immediately reappear in the feed too
So I am testing with your user and I have not seen posts disappearing yet. That's why I am asking questions. With your follow list, they seem to load just fine. I am trying to understand which posts exactly don't show up so that I can isolate the issue. Do you use the default settings with Tor on? That's how I am testing. Do you have any hidden words in your security filters? When you say "disappearing", do they appear and then disappear or never actually load in the feed? Do they show up in the home feed after you navigate to their profile or not even then?