One thing you can do to help is upvote Flotilla on alternativeto: https://alternativeto.net/software/flotilla-chat/about/

Ok guys, help a dev out. I'm an awful marketer — hopefully I'll get some real help on this soon, but in the meantime, what are the highest leverage suggestions you have to catch the Discord wave that I can execute on right now? Flotilla is like 90% stable, which needs to improve, but it's enough to start catching early adopters. I can't really market myself as having feature parity with Discord (RBAC and voice chat are required), and Flotilla's trajectory is slightly different than just a Discord clone. But with Discord's market share and the level of annoyance people are showing with it, I figure if I can catch just a fraction of a percent of the outflow it'll be a pretty large number. View quoted note →

MLMs are the absolute worst. Way shadier than advertising based business models. We need a parallel parallel economy I guess.

I'm writing a guide for self-hosting a zooid relay right now, any favorite VPS providers that are privacy focused and accept bitcoin I should promote?

I resonate with Fred Rogers when he said "I got into television because I hated it so."

Flotilla 1.6.4 is out! (App stores lagging as usual, also working through some issues with zapstore) This release was all about push notifications. My previous approach, which powered Anchor, turned out to be not really feasible for a bunch of reasons, so I finally resorted to drafting a new NIP to ask relays to "push" events to callback URLs. You can read the NIP here:

GitHub

Add NIP 9a for push notifications by staab · Pull Request #2194 · nostr-protocol/nips

Read here

The neat thing about this is that while it is a new relay feature, you can use it today with any public-read relay via wss://npb.coracle.social, which will bridge any relay to your callback URL. This is useful for many things, but I'm using it to power push notifications. I've also added support to https://github.com/coracle-social/zooid, so anyone using that will immediately get push support through Flotilla after an upgrade. Be aware though, that this release switches the nip11 `supported_nips` field to a list of strings (because of NIP 9a). Keep plugging Flotilla as a Discord replacement! Lots of work to be done, but I feel like we're slowly getting there. Full changelog: * Clean up modal design * Fix overflowing popovers * Use space urls for relay hints * Re-work notification badges * Add push notification support via NIP 9a * Optimistically load messaging relays to avoid unnecessary warning * Recover from indexeddb not being available * Fix safe area inset support * Show space URL in top bar on mobile * Fix calendar detail page * Improve relay synchronization, especially for pyramid and relay29 * Improve invite code error handling * Add wallet receive flow * Fix safari image uploads * Re-work recent activity page * Add classified listing content type * Use address for page param for replaceable events * Refine discover page to avoid slowness * Upgrade som dependencies * Tag event author when tagging parent event * Disable macos build * Add room muting

@franzap getting a new error with zapstore publish: ⠼ Uploading https://github.com/coracle-social/flotilla/releases/download/1.6.4/app-release-signed.apk (23efb478e3c602b8024cf58457b050633025f8c0eb3b7255c97216aa24a95045)... ERROR ClientException with SocketException: Connection reset by peer (OS Error: Connection reset by peer, errno = 54), address = cdn.zapstore.dev, port = 57000, uri=https://cdn.zapstore.dev/upload #0 IOClient.send (package:http/src/io_client.dart:154) <asynchronous suspension> #1 BaseClient._sendUnstreamed (package:http/src/base_client.dart:93) <asynchronous suspension> #2 _withClient (package:http/http.dart:167) <asynchronous suspension> #3 BlossomClient.upload (package:zapstore_cli/publish/blossom.dart:94) <asynchronous suspension> #4 Publisher.run (package:zapstore_cli/commands/publish.dart:63) <asynchronous suspension> #5 PublishCommand.run (package:zapstore_cli/main.dart:253) <asynchronous suspension> #6 CommandRunner.runCommand (package:args/command_runner.dart:212) <asynchronous suspension> #7 main (package:zapstore_cli/main.dart:58) <asynchronous suspension>

At least if an attacker ever compromises my computer he won't know which nostr secret key is the real one