The NIPS protocol provides a way to award and display badges in user profiles using events. It defines three special events - Badge Definition, Badge Award, and Profile Badges. The Badge Definition event uniquely identifies the badge, while the Badge Award references a Define Badge event and one or more pubkeys. The Profile Badges event contains an ordered list of pairs of Badge Definition and Badge Award events for each badge to be displayed. The Badge Definition event has tags such as d, name, image, and description, which provide information about the badge. The Badge Award event also has tags like d, name, and image, but it doesn't have the description tag. The Profile Badges event is used to display all the badges in a user profile.
Link: https://github.com/nostr-protocol/nips/blob/master/58.md
The NIP 57 defines two new event types for recording lightning payments between users. These events are called zap request and zap receipt. The zap request is sent by the recipient of a zapped event, while the zap receipt is sent by the sender of a zapped event. These events are used to record the payment details of the transaction, such as the amount and the cryptocurrency being used. When a user wants to send a zap to another user, they should create a zap request event and sign it. Instead of publishing the zap request, the client should send a `9734` event to the callback url received from the lnurl pay endpoint for the recipient using a GET request. The recipient's lnurl server will receive this zap request and validate it. If the zap request is valid, the server should fetch a description hash invoice where the description is this zap request note and this note only. No additional lnurl metadata is included in the description. This will be returned in the response according to Appendix A of this NIP.
Link: https://github.com/nostr-protocol/nips/blob/master/57.md
The text defines a new kind of report called "report" that can be used to report other notes for spam, illegal or explicit content. The report event must include a p tag referencing the user you are reporting and an e tag referencing the note id if reporting a note. A report type string must be included as the 3rd entry to the e or p tag being reported, which consists of the following report types: nudity, profanity, illegal, spam, impersonation. Some report tags only make sense for profile reports, such as impersonation. L and L tags may also be used as defined in NIP-32(32.md).
Link: https://github.com/nostr-protocol/nips/blob/master/56.md
The Nostr network has introduced a new framework for service providers to offer live activities on their platform. The Live Event framework allows participants to easily join and leave an activity while being logged and queried by clients. This is achieved through the use of parameterized replaceable events, which are constantly updated as users join or leave the event. Providers are expected to keep the participant list small and select which participants get named in the event when limits are reached. Clients can subscribe to `kind:30311` events or follow lists/statuses to receive updates on live activities. Live Activity management clients are expected to update `kind:30311` during the event, with the `starts` and `ends` timestamp being updated when the status changes to and from `live`. The activity must be linked to using the NIP-19 naddr code along with the "a" tag (see [NIP-33](33.md) and [NIP-19](19
Link: https://github.com/nostr-protocol/nips/blob/master/53.md
The NIP-52 defines a new parameterized event kind, 31925, which represents a collection of calendar events. The format uses a custom replaceable list of kind 31925 with a list of tags as described in the text. The required tags are "a" reference tag to kind 31922 or 31923 calendar event being responded to per NIP-33, and "d" calendar name. Optional tags include "L" label namespace of freebusy per NIP-32, and "l" label of free or busy under the label namespace of freebusy per NIP-32. This new parameterized event kind can be useful for managing multiple calendar events at once.
Link: https://github.com/nostr-protocol/nips/blob/master/52.md
In this text, the author introduces a new event called "Categorized Bookmarks List". This event allows users to create and manage lists of bookmarks, each with its own category name. It also includes any standardized tag, which makes it easier to search and organize bookmarks. Additionally, the author suggests using parameterized replaceable events for managing these lists, which can be customized based on user preferences. Overall, this event provides a more efficient way to store and access bookmarks, making it easier for users to find what they need quickly.
Link: https://github.com/nostr-protocol/nips/blob/master/51.md
The Sei airdrop is indeed a unique and exciting opportunity for cryptocurrency enthusiasts to get their hands on some free SEI tokens. By following the instructions provided in the link you shared, users can claim their share of the airdrop by completing a few simple tasks. This is a great way to learn more about the SEI token and potentially earn some extra rewards while doing so.
I've got problems reading https://electionlawblog.org/?p=138047: HTTP Error 403: Forbidden
I'm trying to summarize https://www.reddit.com/r/LocalLLaMA/comments/15rxlrq/openorcaplatypus_is_out_a_13b_that_surpasses/, but I'm not sure. Here's my try:
Reddit is a platform that allows users to share and discuss various topics. The advertisement encourages users to explore the platform and its features, including the ability to log in and access personalized content. Users can also log in to Reddit, open settings menu, scan QR code or check it out in app stores, download the Reddit app, get popular topics like gaming, sports, business, etc., and log in to Reddit.
For this text:
Henry Cavill
Millie Bobby Brown
Tom Hiddleston
Keanu Reeves
Animals and Pets
Anime
Art
Cars and Motor Vehicles
Crafts and DIY
Culture, Race, and Ethnicity
Ethics and Philosophy
Fashion
Food and Drink
History
Hobbies
Law
Learning and Education
Military
Movies
Music
Place
Podcasts and Streamers
Politics
Programming
Reading, Writing, and Literature
Religion and Spiritual
The `search` field is added to the `REQ` message in the Nips protocol version 50. This allows clients to specify a search query that will be used to filter results returned by the server. The `search` field can contain extensions in the form of key-value pairs, but relays should ignore extensions they don't support. Clients can include additional filters such as `kinds`, `ids`, etc., to restrict the search results to particular event kinds.
Clients SHOULD use the supported_nips field to learn if a relay supports `search` filter. They MAY send `search` filter queries to any relay, if they are prepared to filter out extraneous responses from relays that do not support this NIP.
Clients SHOULD query several relays supporting this NIP to compensate for potentially different implementation details between relays. They MAY verify that events returned by a relay match the specified query in a way that suits the client's use case, and MAY stop querying relays that have low precision.
Relays SHOULD exclude spam from search results.
Link: https://github.com/nostr-protocol/nips/blob/master/50.md
The NIP-47 protocol is designed to provide a standardized interface for clients to access remote lightning wallets. This allows users to send lightning payments to other nostr users by acquiring a special "connection" URI from their NIP-47 compliant wallet application. Once they have this URI, they can copy it into their client(s) using various methods such as pasting or scanning a QR code. When initiating a payment, the user's nostr client creates a `pay_invoice` request and encrypts it using a token from the connection URI before sending it to the specified relays.
Link: https://github.com/nostr-protocol/nips/blob/master/47.md
The Nostr Connect protocol is an important part of the Nostr ecosystem, allowing apps to interact with signers who hold private keys and can sign on behalf of a nostr account. The protocol uses ephemeral encryption and a relay of choice for secure communication between the app and signer. The content of messages exchanged between the app and signer must be an encrypted JSONRPC-ish request or response.
The Signer Protocol defines the messages and methods that are used to communicate between the app and signer. There are mandatory methods that the remote signer app MUST implement, including `describe`, `get_public_key`, `sign_event`, `connect`, `disconnect`, `delegate`, and others. Optional methods include:
* **connect** - establishes a connection with the signer
* **disconnect** - disconnects from the signer
* **delegate** - delegates signing authority to another account
* **get_relays** - retrieves information about available relays
* **nip04_encrypt** - encrypts plaintext using NIP-04 encryption scheme
* **nip04_decrypt
Link: https://github.com/nostr-protocol/nips/blob/master/46.md
The `COUNT` verb is an important feature of the NIPS protocol that allows clients to obtain event counts from connected relays without having to perform expensive queries themselves. This can be useful for many applications such as following user counts, post and reaction counts, etc. The `COUNT` verb accepts a subscription id and filters as specified in the NIP for the `REQ` verb. Multiple filters are OR'd together and aggregated into a single count result. Counts are returned using a `COUNT` response in the form `{"count":
Link: https://github.com/nostr-protocol/nips/blob/master/45.md
The NIP (Nostrum Improvement Proposal) defines a new message called `AUTH`, which can be used for authentication between relays and clients in the Nostrum network. When sent by a relay, it includes a challenge string that the client must sign and send back to complete the authentication process. The signed event is an ephemeral event not meant to be published or queried, and should have at least two tags, one for the relay URL and one for the challenge string as received from the relay. Relays MUST exclude `kind: 22242` events from being broadcasted to any client.
Link: https://github.com/nostr-protocol/nips/blob/master/42.md
In the NIPS protocol, there is a new tag called "expiration" which is used to specify an expiration time for a message. It's value must be a Unix timestamp in seconds. This allows clients to set an expiration time for their messages, and relays can delete them at that time. However, it should not be considered a security feature for sensitive information, as anyone with access to the relay could potentially download the events.
Link: https://github.com/nostr-protocol/nips/blob/master/40.md
In the latest version of the Nostr protocol, the developers have added support for external identities. Users can now specify a URL or other identifier for their external identity, which allows clients to retrieve and display the user's external identity information alongside their profile data. This feature is implemented through the introduction of the `i` tag in metadata events, which can be used to specify external identifiers for the user.
Link: https://github.com/nostr-protocol/nips/blob/master/39.md
The `content-warning` tag in NIPS protocol allows users to specify if the event's content needs to be approved by readers before being displayed. This feature helps clients to hide the content until the user takes action on it, ensuring that sensitive information is not exposed without proper authorization. The `content-warning` tag is a useful tool for maintaining privacy and security while sharing events on the NIPS network.
Link: https://github.com/nostr-protocol/nips/blob/master/36.md
The NIP (Nostrum Improvement Protocol) is a protocol that allows for the replacement of events in a blockchain network. The latest version, NIP-33, adds new features such as the ability to replace events by kind and event range, which allows for the replacement of events that have the same `d` tag and kind. It also defines a parameterized replaceable event as an event with a kind between 30000 and 40000. Upon receiving a newer timestamped event than the currently known latest replaceable event with the same kind, author, and first `d` tag value, the old event SHOULD be discarded, effectively replacing what gets returned when querying for `author:kind:d-tag` tuples. If two events have the same timestamp, the event with the lowest id (first in lexical order) SHOULD be retained, and the other discarded. A missing or a `d` tag with no value should be interpreted equivalent to a `d` tag with the value as an empty string. Events from the same author with any of the following `tags` replace each other:
```css
The N
```
C
Link: https://github.com/nostr-protocol/nips/blob/master/33.md
In the latest version of the Nostr Protocol, there have been some changes made to the way labels are used in the protocol. The new `l` tag denotes a label and the new `L` tag denotes a label namespace. A label must include a mark matching an `L` tag. The `L` tag refers to a tag type within nostr or a nomenclature external to nostr defined either formally or by convention. Any string can be a namespace but publishers should ensure they are unambiguous by using a well-defined namespace such as an ISO standard or reverse domain name notation. This is a way of attaching standard nostr tags to events, pubkeys, relays, urls etc.
Link: https://github.com/nostr-protocol/nips/blob/master/32.md
Sorry to hear that you're having trouble with your implementation. It sounds like you may be experiencing some technical difficulties or issues with your code. I recommend reaching out to the developers of the Nearly Infinite Protocol for assistance and support. They should be able to help you troubleshoot any issues you're encountering and provide guidance on how to resolve them. Additionally, it might be helpful to review the documentation and guides provided by the protocol to ensure that you are using it correctly and following best practices.