Nostr notes by rabble

oops fixing it.

2026-10-12T20:28:00Z

In reply to nevent1q…2g5r
_________________________

oops fixing it.

After so many bad AI model and agent harness names, i gotta give ...

2026-10-12T20:26:45Z

After so many bad AI model and agent harness names, i gotta give it to Meta... Muse and their newly released Muse Wonder Full model, it's brilliant.

https://research.meta.ai/blog/muse-wonder

He’s sort of on nostr. He’s using divine.video which is a ...

2026-10-08T16:39:25Z

In reply to nevent1q…d954
_________________________

He’s sort of on nostr. He’s using divine.video which is a full nostr app but doesn’t publish kind 1 events. It’s a nostr video app.

Keep nostr weird. ...

2026-10-08T14:06:50Z

Keep nostr weird.

https://divine.video/video/f4a37cbd6b93781272d020c7547a97cd77eab1d6934221e5cc1f77f8408f1aa6

There is nobody who has played a bigger role in inventing ...

2026-10-08T12:24:44Z

There is nobody who has played a bigger role in inventing marketing on social media than garyvee (nprofile…3r3p) I sat down with him to talk about where we came from and how to understand the future in the era of AI.

https://www.youtube.com/watch?v=VOKQsuWM40Q

Human made social media has a soul. This week we gathered amazing ...

2026-10-08T11:52:24Z

Human made social media has a soul. This week we gathered amazing humans in new york to explore using the newest release of c4a39f1291291d452405cd8ddd798c4a29a3858c52cd0d843f1f6852cf17682e (nprofile…emry) . Look at what we created! This is so much better than AI slop chasing algorithmic reach!

https://divine.video/list/fc7031a810ce4b02b6195a7e477cfe3d08c0386038bd45b4431f82d9b3f5ffb0/list_1791303467987

we need to configure relays to reject kind 4 events and drop the ...

2026-10-07T20:28:27Z

In reply to nevent1q…e33h
_________________________

we need to configure relays to reject kind 4 events and drop the old metadata leaking dms altogether.

New version of @nprofile…emry out today! If you want a freedom ...

2026-10-06T12:56:45Z

New version of c4a39f1291291d452405cd8ddd798c4a29a3858c52cd0d843f1f6852cf17682e (nprofile…emry) out today!

If you want a freedom appstore you can get it https://zapstore.dev/apps/co.openvine.app and also it's out on the big corporate appstores too.

We did a ton of work on the camera and making the app feel amazing.

Put a clip anywhere. Lift it out of the timeline and place it over another clip. Move, resize, rotate, or make it see-through. Change its backdrop, use a color mask, or put it back in the timeline.

Freeze the good bit. Hold a frame for part of your loop, then let the action continue. Music and voice-over keep going while the clip’s own sound pauses.

Mix stop motion and camera clips in the same loop.

Try 21 visual effects: glitch, block glitch, RGB split, VHS, static, old film, film grain, interference, CRT, pixelate, pixel pulse, shake, zoom pulse, mirror, kaleidoscope, split screen, wave, glow, vignette, strobe, and negative flash. Adjust their strength and choose when they appear.

Flashing effects add a Flashing Lights warning when you post.

Color mask gets more flexible. The tool formerly called Green screen can work with an evenly lit white wall, too. On supported devices, the new recording mode lets you see the replacement background while you shoot.

More fonts, less fiddling. The font picker now has 128 fonts grouped by style. Resize text with a pinch, let it wrap at the video’s edges, and add outlines or shadows to text and captions.

Make captions move with your words. Word-by-word highlighting joins the caption styles.

Keep a look you love. Save title styling and animations, or caption styles, to reuse in another video.

Choose where a slide starts. Tap a point on the video to set the starting position of a slide animation.

Find the right speed faster. One-tap speed presets sit alongside the slider. Scrub past either end of the timeline to check the loop restart, and find editing actions by their labels.

Sound like yourself. Or a robot.

Bring your own sounds. Add AAC, M4A, MP3, or WAV files to My Sounds.

Imported files stay on the device where you added them.

Share a sound without posting a video first. Publish reusable audio with credit attached, and remove it from Divine’s sound listings when you choose.

Find the sound you meant. Search community sounds by tags and credited creators, and search saved sounds by their private names and tags.

See a sound’s travels. Reuse counts appear in the sound picker and creator analytics.

Give any sound track a different voice. Try high pitch, low pitch, robot, or echo, and reduce background noise. For a clip’s own sound, extract its audio to a track first. You can change or remove the effect later.

Give quiet audio a lift. Turn clips and sound tracks up to 300%, and fade individual tracks in or out.

Record voice-over with the picture in view. The muted video plays behind you as you record.

Reuse classic Vine audio again, while respecting creators who have turned reuse off.

Catch the moment

Hold the camera button to start recording. A regular tap still opens the camera.

A brighter front-camera flash. The area around the preview lights up to help illuminate your shot.

Capture comes first in the recorder’s mode picker.

Better recording recovery. We fixed interrupted recordings, missing audio at the start of iOS clips, audio drifting out of sync, and stop-motion shots not joining the right clip after a trip to the editor.

For Mac creators: improved camera support, including external USB webcams and Continuity Camera.

Make it now. Share it when you’re ready.

Schedule new posts. Choose Tonight, Tomorrow morning, or a date and time. Find scheduled posts above Drafts. For posts scheduled on this device, you can change their time, post now, cancel, or retry when needed. Posts scheduled on another device can be cancelled here.

Tag the right person. Pick an account as you type an @ mention, even when people share a display name.

Credit more than one inspiration. Add multiple creators to Inspired By.

Find crossposting more easily. Connection and reconnection prompts are easier to reach from Settings and your video’s share menu.

Know where a shared video went. Sharing feedback tells you which recipients succeeded and which didn’t.

A profile that feels like yours

Pin up to six videos at the top of your profile, and remove unavailable pins to make room.

Find bookmarks in their own profile tab.

Get a clearer picture of your audience. Open creator analytics from your profile’s Loops stat, see unique viewers per video, and see how often your sounds are reused.

Give classic loops their due. Archived Vine loops count toward a creator’s total, and live Divine loops are kept distinct from the archive count.

Open shared public people lists and browse their members, with a refreshed list view and fixes that help list videos load from the right creators.

Keep your profile information intact. Saving in Divine preserves details added through other compatible apps.

Watch your way

Hold a video to pause it while you’re pressing.

Pinch to hide the feed controls and give the video more space.

Choose which numbers you see. Viewer settings let you control the profile and video stats shown to you.

A cleaner feed layout puts more focus on the creator.

Smoother loops on iOS and Android. Fixes tackle pauses, clicks, silent starts, and freezes at the loop boundary.

Less stuttering and waiting. Scrolling does less repeated work, cached videos stay available when you switch feeds, and Android avoids downloading the same looping clip twice.

Keep your place. Full-screen feeds behave better when you open another screen or a profile updates. Editing a video no longer moves it to the front of New.

Find the right content. Changing your content language refreshes For You and Popular. Video and profile links work more reliably, and large liked-by lists keep loading.

Captions behave more consistently. Turning them off sticks across videos, classic captions don’t appear twice, and subtitle downloads preserve non-English characters.

Messages that keep up

Send encrypted videos in one-to-one chats. Open them full-screen and save received videos to your device.

Better message recovery. We fixed cases where messages or group conversations went missing, older history stopped loading, and retrying a send gave confusing results.

More honest delivery feedback. A failed send, reaction, or delete-for-everyone request is easier to spot and retry.

Better conversations with other Nostr apps. Fixes help messages and reactions reach the recipient’s chosen inbox.

Less inbox clutter and confusion. Group names, account names, message-request counts, and closed conversations are handled more consistently. We removed a mute-conversation switch that didn’t actually mute anything.

More control. Clearer answers.

Settings are organized around what you want to do, with better contrast and hierarchy in light mode.

Choose whether to share usage analytics. Marketing messages also have an explicit opt-in.

Support Divine in the app. Monthly and annual supporter plans are available in App Store and Google Play builds, with optional public profile badges. Renewal terms, purchase restoration, and checkout feedback are clearer. Membership and identity verification are separate things.

Divine now speaks Telugu, alongside translation fixes for settings, recovery messages, and sponsorship disclosures.

See what’s taking up space. Storage settings show more of the app’s disk use and let you clear leftover files. Available app updates are easier to find, too.

More accessible controls. Larger tap targets and clearer screen-reader labels make key feed and profile actions easier to use.

Clearer support choices. Public support submissions explain what will be published. Appeals open private support, and Support Center lets you clear diagnostic logs.

Report now, send when connected. Reports are saved while offline, and photos attached to bug reports have embedded metadata removed.

Safety controls that follow through. Report and Block remain available on other people’s profiles, unblocking updates hidden-account lists consistently, and safety-label changes arrive without restarting. We also tightened protection around key export and diagnostic data.

A simpler start. Invite-code onboarding has been removed.

Less sign-in friction. Fixes cover email verification, password-reset keyboards, rate-limit messages, and opening a restored session while offline.

Better account recovery and deletion handling. Interrupted operations have clearer recovery paths, and normal deletion processing is less likely to send you to support unnecessarily.

The fixes you should notice less

Drafts no longer grow with every edit, and failed or cancelled renders clean up their temporary files.

Export progress is more useful. Stuck renders can recover, cancellation stops work, and storage errors get clearer explanations.

A failed sound download no longer quietly turns your finished video into a silent one.

Cropped and rotated clips keep their proportions. Text stays in place on square exports with mixed-size clips. Android transitions between camera and library clips work more reliably.

Timeline dragging, very short clips, opacity controls, and repeated trimming behave more predictably. An accidental back swipe no longer closes the editor.

Newly published videos stay in your profile and can play while additional versions are still being prepared.

Deleted comments stay deleted, duplicate likes are reduced, and exact account matches rise to the top of search.

Better memory use, cache cleanup, startup recovery, and crash handling help keep the app moving.

The web app loads only the interface language you use, and removing unused components makes Android and Mac downloads smaller.

Thanks to everyone who kept testing, reporting, and making things while we worked through this. Divine gets better because we build it together.

Own what you make. Choose what you see.

Yes but talking about Nostr is like talking about TLS, yes ...

2026-10-06T12:50:44Z

In reply to nevent1q…q57l
_________________________

Yes but talking about Nostr is like talking about TLS, yes it's important, but users don't need to know how it works.

This is a great essay about why the developer moved from the ...

2026-10-06T12:09:40Z

This is a great essay about why the developer moved from the fediverse to nostr.

quoting
naddr1qv…xwj9

Written by npub18ug6hvhzxhdz6nw6t4k7ktcjx9e5w6n5tg7226y458g0vv4y9aqq3r20ex

The Promise of a Federation

My journey into decentralized social media began not at the musk of an eel, but in 2009, grounded in my understanding of value-defining network dynamics. My first encounter with the technology that would later be formalized as ActivityPub (the protocol underpinning today’s “Fediverse”) happened with a click on a link to a site called Identi.ca. What captivated me was not merely a new website, but a new paradigm.

The dream: a constellation of independent communities, each living on its own server, yet interconnecting to form a larger social network.

While it is true that my first email was very much federated, here was social media that was open: the software was free and open-source, meaning I could, in theory, run my own node. It presented a vision of the web that resisted the centralizing pull of corporate platforms. Finally a place where users weren’t locked into walled gardens that commodified their data and compromised their privacy. This was the dream: a constellation of independent communities, each living on its own server (or instance), yet interconnecting to form a larger social network.

For years, I witnessed and participated in the unique culture it fostered: a space where thoughtful discourse often trumped algorithmic rage, where one could bridge communities of interest while maintaining a sense of local belonging. The federation wasn't just a technical architecture; it was a social contract, enabling connection without central control. It felt like the future.

My identity was always subject to the will of an admin or, if I ran my own instance, this identity was simply rented from a domain name registrar.

Yet, over the years, flaws in the foundation began to show. The very structure that enabled this federation also imposed annoying limitations. While our content was decentralized our identities were not. My digital self, and all of my social graph were irrevocably tied to a specific URL. Sovereignty was an illusion; my identity was subject to the will of an admin or, if I ran my own instance, this identity was simply rented from a domain name registrar.

What's worse, portability was a myth, locked behind complex technical migrations and the tendency of server software developers to freestyle their own versions of the protocol. The decentralization was selective, it distributed the user-generated value, but funneled users through vulnerable single-points of entry. These pain points, inherent to the protocol's design, shifted my perspective from advocacy to skepticism. **The future **was** federated,** but I have come to believe that future was obsoleted by something more robust, more sovereign, and more decentralized.

The Sovereign Protocol: NOSTR and the Architecture of Autonomy

My disenchantment with the federated model did not lead me to abandon the dream of decentralized social networking, but to refine it. In 2022, I found a better realization of that original vision, in a very different paradigm: NOSTR (Notes and Other Stuff Transmitted by Relays). NOSTR addresses the core limitations of the Fediverse by architecting for true user sovereignty, creating a system where identity, social graph, and data are the user's property.

This portability transforms the power dynamic; it means my community and relationships are mine, not artifacts of a particular server's database.

Most notably, NOSTR establishes **sovereign identity. **Just like old, well tested and popular technologies such as GPG/PGP, my identity is not a URL granted by an admin and rented from a registrar. It is a cryptographic key pair, generated offline on my own device, on my own terms. This self-sovereign identity is completely portable. I can use it to authenticate with relays (NOSTR’s equivalent of a server) in the network, and I can leave any relay at any time without losing my identity or my social connections. Critically, my social graph (the list of people I trust to share important information with me, the people i "follow".) is part of this sovereign identity, stored as a simple, cryptographically signed list that I carry with me. This portability transforms the power dynamic; it means my community and relationships are mine, not artifacts of a particular server's database.

My followers subscribe to me, not to a specific platform or format. This eradicates the fragmentation of the Fediverse, where your digital self is scattered across multiple domain names.

This sovereign identity enables a second advantage: universal content creation under a single identity. In the Fediverse, content format is tied to server software. To microblog, you need a Mastodon account; to write long-form, a WriteFreely account; to share videos, a PeerTube account. Each requires a new identity on a new server. In NOSTR, a "post", a follow, a direct message, is simply a cryptographically signed JSON object. Because the protocol is agnostic about content type, my single cryptographic key can publish microblogs, articles, audio notes, or live streaming metadata. My followers subscribe to me, not to a specific platform or format. This eradicates the fragmentation of the Fediverse, where your digital self is scattered across multiple domain names.

Third, NOSTR achieves a better balance between permissionless networks and moderated spaces. The NOSTR network itself is permissionless; anyone with a key pair can participate. However, individual relays are not. They can be private, curated, or enforce specific rules, much like Fediverse instances. The main difference is that a user is not bound to a single relay. I can publish to (and read from) multiple relays at the same time, participating in different communities without being defined by or subject to the culture of any server or community. I can use a specialized relay for technical discussions and a family-friendly relay for general posts, or why not leverage the local pub's relay while i am there? And all with the same identity.

This architecture disempowers bad actors, both users and operators. A relay operator has no power over my identity. They cannot deplatform me; they can only refuse to host my data on their specific relay. This disincentivizes the admin "power trips" seen in some Fediverse instances, as operators are encourage to provide stable service in good faith, or the users (and their valuable content) migrate elsewhere. Conversely, I am also incentivized towards good behavior, as persistent abuse could lead to my exclusion from the relays. Reputation becomes attached to the immutable cryptographic identity, creating a more durable and user-responsible social contract.

Finally, this cryptographic foundation makes privacy a protocol feature, not an add-on. Because my identity is a cryptographic key pair, end-to-end encrypted private messaging is native to NOSTR. Of course, true privacy needs more than that. On the modern internet, privacy is more of a personal hygiene than a choice in software. But it's a good foundation to build on. A relay simply passes along the encrypted data. It has no ability to read my private communications, offering a level of privacy that federated servers, which always work with plaintext data, cannot match without complex external tools.

NOSTR replaces the fragile, admin-dependent federation of domains with a resilient, user-centric network of cryptographic identities.

In summary, NOSTR inverts the Fediverse's model. Instead of federating servers and tethering users to them, it federates sovereign users who temporarily utilize servers for the purpose they see fit. It replaces the fragile, admin-dependent federation of domains with a resilient, user-centric network of cryptographic identities.

The Burden of Sovereignty: Challenges in the NOSTR Paradigm

My goal here is not to declare NOSTR a perfect utopia. Its radical architecture may give unparalleled sovereignty, and enable a web of trust dearly needed in these times of disinformation, it also imposes burdens and presents problems that do not exist in the federated model. These are not mere technical bugs to be fixed, but intrinsic features of a system where the responsibility shifts from server administrators to the individual user.

The biggest challenge is the difficulty of key management. Sovereign identity means the user is their own root certificate authority. There is no "Forgot Password?" link that emails you a reset. The private key is the singular, irrevocable proof of self. Losing it means the permanent loss of that identity and every connection built with it. Compromising it means handing over the entire digital life created around an identity, past and future, to an attacker. This places a huge cognitive and security burden on users, most of whom struggle with basic password hygiene. Imagine trusting them with lifelong guardianship of a cryptographic key. Furthermore, the act of signing is a final, legal-grade attestation. Every post, every like, is cryptographically undeniable. This demands a level of intentionality and caution in communication that is alien to the more ephemeral, deletable culture of mainstream or even federated social media. It forces a coming to terms with a hard truth: privacy, and the permanence of our digital footprints, is not a feature an app can provide. It is a discipline of personal hygiene that NOSTR makes explicit and non-negotiable.

This creates a single point of failure for one's social presence, a problem the federated model largely avoids through account recovery mechanisms controlled by instance admins.

Closely related is the immaturity of key lifecycle management. Robust methods for key rotation, delegation, or inheritance (common in enterprise cryptography) are still nascent in NOSTR clients. This lack compounds the risk of loss or compromise. In the PGP "Web of Trust" model, keys can be revoked and new ones signed. In NOSTR's current state, your original key is your eternal, un-rotatable self. This creates a single point of failure for one's social presence, a problem the federated model largely avoids through account recovery mechanisms controlled by instance admins. This is also an issue for organizations: if their social properties are managed by a key, how do we allow a social manager to write, without surrendering the entire account and it's future? While multiple solutions for multi-signature are being advanced, the protocol still lack meaningful tools for an organization to leverage it.

Beyond key management, there is a significant conceptual hurdle in understanding the network's topology. The decoupling of identity (keys), data (events), and access points (relays) is disorienting. Understanding that "where" you post is subjective and fluid, while "who" you are is absolute, requires a mental model shift. Finding content, and shaping one's experience are functions of the client software. The separation of substance from form is powerful but abstract. It creates a steep learning curve that will make mainstream adoption complicated.

Finally, there is the reality of the current network culture and scale. NOSTR remains a small space. Its early adopters are heavily skewed towards cryptocurrency advocacy, with Bitcoin culture undeniably prevalent. For those opposed to this world, it can feel like an unwelcoming niche. Yet, this very origin also creates a unique strength. The embedded capability for micropayments via the Lightning Network fosters a nascent gift economy (often termed "Value 4 Value"). This allows direct, frictionless support between creators and audiences, a feature that is protocol-native rather than a corporate monetization add-on. While the community is actively building vibrant spaces for art, technology, and philosophy beyond finance, the network's size and its economic layer remain barriers for a broader public seeking a simple social media alternative.

This is not a system designed for passive consumption; it is a toolkit for active, conscious digital citizenship, with all the power and danger that entails.

NOSTR does not eliminate the problems of online interaction. It replaces the problems of _centralized control _and platform/server dependency with the problems of absolute personal responsibility and conceptual complexity. It trades the risk of an admin's capriciousness for the risk of one's own human error. This is not a system designed for passive consumption; it is a toolkit for active and conscious digital citizenship, with all the power and danger that entails.

Forging a Sovereign Future

My journey from the federated promise of ActivityPub to the sovereign architecture of NOSTR is not a rejection, but an evolution. It is the recognition that the fundamental flaw of the federated model; tethering identity to a domain, was a limiting compromise that could not be patched, only replaced. My thesis extolled NOSTR's design for autonomy; my antithesis laid bare its demanding realities. Synthesizing these reveals that NOSTR is not merely a better protocol, but a necessary step toward a user-empowered internet, one that demands and rewards greater personal responsibility.

1. Sovereignty is a discipline, not just a feature. The antithesis identifies key management and the permanence of the signed event as NOSTR's greatest burdens. Yet, these are not bugs to be wished away. They are the direct, logical consequences of the sovereignty promised in the thesis. True ownership means true responsibility. The difficulty of this model is its entire point. It forces a societal shift from viewing digital interactions as disposable, platform-managed chatter to recognizing them as durable, personal attestations. The "hygiene" it demands is the foundation of a digital society where individuals have authentic agency, not just user profiles. The technical challenges of key rotation and recovery are significant, but they are engineering problems to be solved around the sovereign core, not by dismantling it.

2. Complexity is the price of true choice. The conceptual difficulty of understanding relays and clients is real. However, this complexity is the result of decoupling form from substance, which the thesis celebrated as an advantage. In the Fediverse, the instance (form) dictates the community and rules (substance). In NOSTR, I choose my experience (client, relay filters) independently of my immutable identity and social graph. This abstraction is powerful precisely because it is complex. It mirrors the real world, where our identity is constant, but we choose which forums, gatherings, and media to engage with. Making this model accessible is the great design challenge for NOSTR clients, not a refutation of the underlying principle.

3. A network's culture is its adolescence, not its destiny. The current size and Bitcoin-centric culture of NOSTR are functions of its early stage, not its end state. The federated Fediverse, too, was once a small niche of FOSS idealists. The embedded gift economy, born from its cryptocurrency roots, is not a cultural baggage but a revolutionary core—a built-in, protocol-level alternative to surveillance-based advertising. As the tools mature and the burdens of sovereignty are mitigated by better software, the network can and will diversify. The vibrant communities I cherished in the Fediverse can be rebuilt on NOSTR, but this time on a foundation of portable identity and unbreakable social bonds, free from the threat of arbitrary exile.

The future was federated, a necessary experiment that revealed the true goal: not federation, but sovereignty.

In conclusion, I stopped trying to grow ActivityPub not because its dream of a decentralized social web was wrong, or because federation is an obsolete concept, but because its architectural blueprint was too limited. It federated servers but left users as tenants. **The future **was** federated,** a necessary experiment that revealed the true goal: not federation, but sovereignty. This doesn't mean that federation is an obsolete model, it is still very relevant in systems where a trusted 3rd party is required. It only means that, for online socialization NOSTR, and all its current difficulties, is better adapted to the modern web. It accepts that a free, resilient, and human-centric internet cannot be made convenient at the expense of user agency. It replaces the fragility of rented domains with the resilience of cryptographic keys. It is a harder path, requiring different tools and more thoughtful users. But it is currently the only known path that leads to a future where our digital selves are irrevocably our own. The work now is not to patch the old federation, but to build the accessible bridges that will allow others to cross into this sovereign territory. And then again, everything we know and think about social media may soon be obsoleted by an entirely different form of interaction. Who knows what the future holds?

I, for one, sure hope Local will be the new Social.

Tune in to the discussion 💬

(These services are bridged: join your favorite and reach them all)

🗨️ IRC

🗨️ Matrix

🗨️ Telegram

🗨️ Discord

Support Dyne 🫱🏿‍🫲🏾

Help dyne.org stay focused on hacking the planet!

🥰 Donate 💸

🪙 Bitcoins: bc1qz9wz2f9swcefra2tfrhk4fx49evqsv03m9nx4l

⚡ wittycommand234@walletofsatoshi.com

☕ Ko-Fi

🍴 Github.com

🧁 LiberaPay

🍥 Patreon.com

Ok. Who’s Tesla am I driving behind. ...

2026-09-11T23:23:41Z

Ok. Who’s Tesla am I driving behind.

Sometimes the best way to get a community to adopt a technology ...

2026-08-24T21:36:31Z

Sometimes the best way to get a community to adopt a technology like cashu and lightning is to never mention the technology or ideology of bitcoin at all.

This is what Blacksky.cash is doing.

I keep hitting subscription limits on Codex and Claude, so ...

2026-07-14T10:52:50Z

I keep hitting subscription limits on Codex and Claude, so I'm going to try adding GLM 5.2 (z.ai) to the rotation. Cheapest approach I've found: one Max plan on each, then rotate through them as their 5-hour, daily, and weekly usage windows reset. Going per-token instead is hundreds of times more expensive.

Curious what others are doing to manage cost with heavy agentic coding. Rotating plans? Cheaper models for the routine work? Something smarter?