是不是玩的人又少了？

#cfrelay cfrelay version 0.1.0 release .

In this version, we implemented query optimizations at both the application and data layers to reduce the query load on the database.

So far, the optimization has been successful; even running the relay solo, I am nowhere near hitting the database query limits.

What is cfrelay ? It is a relay that can run for free on Cloudflare Workers. It was designed for private write and public read.

Running your personal relay and owning your data.

You can deply it with your cloudflare and github account by one click deploy:

https://github.com/haorendashu/cfrelay

完蛋了，event 数量越来越多。。。 问题也越来越多了~~~

#amethyst 有没有使用 #nip-85 ？就是有些服务商可以给用户、event 等 打分。判断用户等是否可信。

We have deployed a test relay using this storage. It typically has fewer than 200 online clients, resulting in low load and ample redundant resources. Please feel free to add it to your relay list so I can better improve its performance.

Relay address : wss://top.testrelay.top

Nostr Event Store Version v0.7.0 Release Log

This update includes numerous feature enhancements, performance optimizations, and critical fixes, improving system stability and flexibility. Key updates are as follows:

Important Features and Functionality

• Enhanced Aggregation Functionality
  • Added metadata support for aggregation operations.
  • Support for multi-index aggregation queries, improving complex query capabilities.
  • Adjusted the maximum aggregation grouping key logic, improving aggregation efficiency under large data volumes.
  • Supplemented aggregation-related documentation.
• Replaceable Kind Event Configuration
  • Added replaceable kind event configuration to both base-relay and remote-relay, supporting more flexible event replacement and deletion strategies.
• Batch Save and Validation
  • Added validation after batch save operations to improve data consistency.
  • Delete by Filter
  • Added batch delete functionality based on conditions, supporting filtering for duplicate IDs, improving the accuracy and efficiency of deletion operations.

Query and Index Optimization

• Added time limits to multi-index range construction to prevent performance bottlenecks in extreme cases.
• Removed the default limit from the query interface, supporting more flexible query needs.
• Added limits to count queries to prevent excessive resource consumption.
• Bug fixes related to index rebuilding and refreshing, including issues such as inconsistent index counts and flush errors.
• Enhanced WAL (Write-Ahead Log)
  • Added ID verification to improve log consistency.
  • Adjusted log format, fixing the bug of only having a single WAL file.

Other Fixes and Improvements

• Fixed the segment count error in the segment statistics interface.
• Repaired and improved test cases.
• Adjusted .gitignore file.
• Performance and stability improvements, including minor optimizations such as "fix too many pings".

#nostr_event_store

About nostr_event_store's Aggregation, you can read from here

About nostr_event_store's deployment methods, you can read from here

About nostr_event_store's Aggregation

What is Aggregation?

Aggregation is a mechanism for grouping, statistically analyzing, and aggregating event data. It allows you to perform statistical, trend analysis, and ranking operations on events based on different fields (such as author, event type, tags, time, etc.).

What can Aggregation do?

• Count the total number of events or the number of groups
• Analyze trends by time binning (e.g., daily, hourly)
• Group by multiple dimensions such as author, event type, and tags
• Query the activity level or distribution under a specific author, tag, or topic

Specific Examples (including parameters and calling methods)

1. Count active users and their posts on a specific day

q := &types.AggregationQuery{
    Filter: &types.QueryFilter{
        Since: uint32(dayStart.Unix()),
        Until: uint32(dayEnd.Unix()) - 1,
    },
    GroupBy:   []types.GroupByField{types.GroupByAuthor, types.GroupByKind},
    AggFunc:   types.AggCount,
    OrderDesc: true,
    Limit:     1000,
}
entries, err := s.client.QueryAggregation(ctx, q)

2. Statistics on daily event trends

q := &types.AggregationQuery{
    Filter: &types.QueryFilter{
        Since: timeWindow.StartUnix,
        Until: timeWindow.EndUnix - 1,
        Kinds: kinds,
    },
    GroupBy:           []types.GroupByField{types.GroupByTimeBucket},
    AggFunc:           types.AggCount,
    TimeBucketSeconds: 86400, // A day
    OrderDesc:         false,
}
entries, err := s.client.QueryAggregation(ctx, q)

3. Statistics on popular tags

q := &types.AggregationQuery{
    Filter: &types.QueryFilter{
        Since: timeWindow.StartUnix,
        Until: timeWindow.EndUnix - 1,
    },
    GroupBy:   []types.GroupByField{types.GroupByTagValue},
    AggFunc:   types.AggCount,
    TagName:   "t",
    OrderDesc: true,
    Limit:     20,
}
entries, err := s.client.QueryAggregation(ctx, q)

4. Statistics on the most active authors under a certain topic（KOL）

q := &types.AggregationQuery{
    Filter: &types.QueryFilter{
        Since: timeWindow.StartUnix,
        Until: timeWindow.EndUnix - 1,
        Tags:  map[string][]string{"t": {"A topic"}},
    },
    GroupBy:   []types.GroupByField{types.GroupByTagValue, types.GroupByAuthor},
    AggFunc:   types.AggCount,
    TagName:   "t",
    OrderDesc: true,
    Limit:     20,
}
entries, err := s.client.QueryAggregation(ctx, q)

5. Statistical analysis of author activity trends on a specific topic

q := &types.AggregationQuery{
    Filter: &types.QueryFilter{
        Since:   timeWindow.StartUnix,
        Until:   timeWindow.EndUnix - 1,
        Authors: [][32]byte{pub},
        Tags:    map[string][]string{"t": {"A topic"}},
    },
    GroupBy:           []types.GroupByField{types.GroupByAuthor, types.GroupByTagValue, types.GroupByTimeBucket},
    AggFunc:           types.AggCount,
    TagName:           "t",
    TimeBucketSeconds: 86400,
    OrderDesc:         false,
}
entries, err := s.client.QueryAggregation(ctx, q)

These parameters and calling methods can be flexibly combined to meet various statistical and analytical needs. The core is to construct an AggregationQuery and then use the QueryAggregation method to initiate an aggregation query.

These are some relay data statistics functions that I developed based on this Aggregation feature.

Project link: https://github.com/haorendashu/nostr_event_store

#nostr_event_store

nostr_event_store supports three main deployment methods, each suitable for different application scenarios:

1. Application-integrated (e.g., demos/base-relay)

• Method: The event store is directly integrated into your Go application process as a library. API calls are direct, requiring no network communication.

• Advantages: Extreme performance (no network latency), simple deployment, suitable for single-machine/embedded scenarios, easy to develop and debug.

• Disadvantages: Cannot be scaled across multiple processes/machines; the event store is affected when the process crashes, making high availability difficult.

2. Remote deployment (e.g., demos/remote-relay)

• Method: The event store runs as an independent service process, communicating with the application via a gRPC remote interface.

• Advantages: Decoupling of the application and the event store; independent scaling, restarting, and monitoring; supports multiple client access; facilitates service-oriented deployment.

• Disadvantages: Network communication overhead; slightly higher deployment and maintenance complexity; slightly inferior performance compared to the built-in method in extremely low-latency scenarios.

3. Sharded Deployment (Under Development)

• Method: Multiple machines/processes, each running one event store instance, sharded by author pubkey hash, with a coordinator responsible for routing and aggregation.

• Advantages: Strong horizontal scalability, distributed load across single nodes, suitable for large-scale data and high-concurrency scenarios, limited impact from single shard failures.

• Disadvantages: Complex implementation and maintenance (requires coordinator, shard routing, cross-shard query aggregation), more complex consistency and recovery mechanisms, and higher initial deployment costs.

Summary:

• Small projects/single machine: Recommended for application integration, simple and efficient.

• Requires decoupling of multiple processes/services: Recommended for remote deployment.

• For ultimate scalability and high availability: Recommended for sharded deployment, but requires more development and maintenance resources.

Project link: https://github.com/haorendashu/nostr_event_store

#nostr_event_store

I just update my vscode and i found that it show its bsky's account link at the release logs.

https://bsky.app/profile/vscode.dev

Can we have a profile link like this and don't like npubxxxxx.

Why they doesn't have a nostr account.

#asknostr

Wow, this seems to be something I've always wanted to do.

果然，一堆发 spam 的。

#nostr #spam

发现 bostr.shop 上，有两个中继，在彪 event ~~~

这两个： wss://top.testrelay.top/ wss://relay.snort.social

因为很多这种请求：

2026/04/02 11:58:07 Rejecting req 10065615:: filter can't be empty {"since":1,"limit":1}
2026/04/02 11:58:07 Rejecting req 10065790:: filter can't be empty {"until":1,"limit":1}
2026/04/02 11:58:07 Rejecting req 10065723:: filter can't be empty {"until":1,"limit":1}
2026/04/02 11:58:07 Rejecting req sub: filter can't be empty {"limit":0}

不知道哪家来采集，还一下子发几个额请求，而且正好又有大量的 spam ，导致 cpu 和 流量 涨起来了。

Nostrmo version 3.5.1 release.

This version mainly focuses on bug fixes and optimizations.

Change list:

• Add inbox support for followed feed and mentioned feed.
• Sync feed change to using eventlistbox. (Fix new events not showed bug.)
• Open link in app webview support close.
• Move key to secure store.
• Webutils page change to webapps pages. (Just like nowser)
• Fix group message not update bug.
• Fix image take too much memery error.
• Mentioned feed add p tag check.

You can download from Github release:

https://github.com/haorendashu/nostrmo/releases

Other version you can find from:

IOS

APPStore

TestFlight\r\n\r\n

MacOS

APPStore

TestFlight

Web And PWA

Web And PWA

I just send this query to the relay:

["COUNT","123213343213123",{"kinds":[1]}]

And then I could almost hear the server fans spinning wildly. 😥😥😥😥

The data volume is getting bigger and bigger; now it takes two hours to rebuild an index.

Hello, i am developing a nostr event store project. I need some query sample to improve the query system. Can you add this relay wss://top.testrelay.top/ to your client ?

Thanks.

https://github.com/haorendashu/nostr_event_store

#asknostr

Briner version 0.1.1 release.

Briner is a browser extension that provides Nostr signing capabilities across Chrome, Edge, and Firefox browsers. It acts as a bridge signer, allowing users to securely sign Nostr events using different signing methods.

Briner is also support nesigner, if you want to try nesigner on web clients, you should try briner.

Change List:

• Change the way passing message between background and hardware signer page.
• Sometime origin not found bug.
• Fix nostr_script not found bug.
• Change many page's UI.
• Add auth log detail page.
• Change LOGO.
• Return a blank map when getRelays call.

You can download it from: https://github.com/haorendashu/briner/releases

#briner #nesigner #nostrmo

Nesigner Ecosystem Update Announcement

We're excited to announce the simultaneous updates of the core Nesigner project, its official website, and the js_nesigner_sdk! As an open-source Nostr hardware signer built on ESP32, Nesigner has received key optimizations for performance, usability enhancements, and rich resource supplements across the ecosystem. Below are the detailed update notes:

1. Nesigner Core Project (v0.3.0)

Repository: https://github.com/haorendashu/nesigner This v0.3.0 release focuses on performance optimization and usability improvement, with comprehensive adjustments to the underlying runtime mechanism and error handling logic. The key changes are as follows:

• Replaced dynamic memory allocation with a memory pool for improved memory efficiency.
• Pushed response messages to the task queue to optimize the message processing workflow.
• Eliminated redundant initialization of the crypto context to reduce unnecessary operations.
• Adjusted task queue configurations to align with performance optimization requirements.
• Revamped error handling methods to enhance the capability of processing exception scenarios. These optimizations have significantly improved the overall performance and usability of the Nesigner hardware signer, and we warmly invite you to experience the upgraded version!

2. Nesigner Official Website

URL: https://nesigner.nostrmo.com/ The official website has been fully updated with expanded operation workflows and development resources, making device operation and secondary development more straightforward. Key updates:

• Added a dedicated development resources section, including multi-platform SDKs (JavaScript SDK, Flutter SDK) and compatible Nostr clients (Nostrmo, Nowser, Briner).
• Implemented new practical device operation features: Secret Key Update and Batch Testing, with corresponding operation entrances and step-by-step guides provided.
• Optimized the UI/UX of basic operations such as firmware flashing and device connection for clearer step guidance.

3. js_nesigner_sdk (v0.1.7)

Repository: https://github.com/haorendashu/js_nesigner_sdk As the official JavaScript SDK for interacting with the Nesigner hardware device, v0.1.7 primarily supplements device management and diagnostic interfaces, enabling more comprehensive feature coverage for web-side development. Newly added interfaces:

• Diagnostic interfaces: ping() (tests device connectivity and returns latency), echo() (sends echo messages for device testing).
• Device management interfaces: updateKey() (updates the device key via PIN code), removeKey() (deletes the device key via PIN code).
• Ensured full compatibility between new interfaces and core functions (key management, encryption/decryption, signing, etc.).

With this update, Nesigner has formed a more complete ecosystem covering hardware-level performance, end-user operation experience, and developer tool support. We will continue iterating on the project with a focus on stability and feature expansion. We welcome all developers to submit issues, contribute code via the project repositories, and try out the new features on the official website with your valuable feedback!