Nip-activity < Original >

Current challenges include:

Future research should employ:

Platforms like Damus, Snort, and Amethyst rely on nip-activity for every like, reply, and repost. Unlike Twitter or Facebook, your social activity is not owned by the platform. Your kind=1 text notes follow you, not the server. If you switch clients, your entire activity history moves with you. nip-activity

Some NIPs define replaceable events (e.g., NIP-09 for deletions). In nip-activity, you cannot delete a past event. Instead, you publish a new activity that references the old one, and clients are instructed to ignore the superseded version. This creates an auditable timeline of corrections without erasing history. Current challenges include:

  "type": "nip-activity",
  "id": "<activity-id>",
  "actor": "<pubkey>",
  "verb": "<verb>",
  "object": profile,
  "metadata": 
    "text": "<short snippet>",
    "media": ["<media-url-or-id>"],
    "tags": ["type":"p","value":"<pubkey>"],
    "counts":"likes":123,"reposts":10
  ,
  "timestamp": 1670000000000,
  "visibility":"public",
  "signature":"<sig-of-actor-over-id-and-timestamp>"

Ready to integrate nip-activity into your own application? Follow this practical roadmap. Future research should employ: Platforms like Damus, Snort,