well that's cool but wen bitch hats

Wouldn't mind a lil explainer on what it's all about. Maybe a vlog? 👀

I downloaded bitchat at the Glasgow meetup last weekend, am just starting to learn how it works. Thanks for the freedom tech. 🧡

Way to go Jack! Thank you. Now its time to fund JackPhone. Google going full totalitarian.

Beautiful work as always, Jack.

The hash for a large country seemed to flip back and forth a few times on 1.3.1

Glorious 💜 #bitchat

Wow, that’s a smart move! Using georelays to reduce latency and fight spam while keeping chat decentralized is impressive. Excited to try the update! 🚀

It will be exciting when I see another user in my chat for the first time

This course of development is very curious. * Three platforms, three developers vibe coding * Each managing their platform's distribution systems * Each adding features in their own implementation * Features are then backported to the other codebases to maintain feature & protocol compatibility. * No protocol documents, the code (and maybe the prompts?) is the documentation

Great

what is desired is achieved.

Guys please help repost my geyserfund 🙏🏻 View quoted note →

1.2.0 seems latest .APK Android release on GitHub. Does this mean play store has later version?

🤣🤣🤣

Nice! Quick question is /me going to be added?

👏💫

Modern software development. It's a vibe.

It’s fascinating to see this in action

Any android version yet?

Thank you thank you

Add bitchat on F-Droid

Zapstore and Play store, yes.

Bitchat gives me hope

Keep up the great work, Jack. Loving the decentralized chat technology.

⭐️ View quoted note →

Careful, that's what the DAO guys said in 2016. Not sure what the lesson is, but didn't go as expected, at very least. Maybe just be wary of hubris

Correct me if I'm wrong, but doesn't that fragment the network and break these heatmap web apps (like bitmap.lat) because they cannot track events globally anymore? Unless they connect to all 300 georelays, I guess. Which seems possible for a dedicated spammer, but if hundreds of people are doing it from their browsers, it would likely be an issue.

I think it's fine for experimentation, but the likelihood it produces a long-term maintainable project is low. Eventually standards will need to be written, negotiated and adhered to. For now, the code is the only source of truth, and that is fine. No reason to get your knickers in a knot.

yes it does unfortunately. but hopefully the web apps will be more directed as a result. will see.

I'm honestly wondering if this was a good idea, at least at this time. I'm sure you had good reasons to do it, and I certainly don't understand nearly half as much about the technical aspects as you do, but being able to find active rooms on a map view was really neat. As was having a choice of a variety of different clients that could all talk to each other. Spam was a problem, yes, but Nym showed that it was fairly easy to get rid of by simply using a relay that has rate limiting (such as Damus's). I understand that it would of course cause even more centralization if everyone was going to use that, but unless traffic was already causing severe resource strains, wouldn't it have been better to wait until there is a more significant userbase? A lot of people I talked to had trouble even understanding how it worked at this stage, how are they going to understand that there may essentially be several different versions of the same room on different relays, and depending on which client you use, you might see entirely different conversations? If it is not possible or desirable to expect other relays to rate limit, couldn't that be also done on the client side instead? For instance, any single account sending more than one message per second is likely spamming, as is anyone sending the same message from different accounts (such as the semicolon troll). Other alternative clients have tried different approaches — For instance, Nym has a customizable keyword filter, and bitmap.lat has a rudimentary pattern-based filter that worked pretty well that could potentially be ported to the app (you can see what it tests for in `src/lib/spam.test.ts` on their NostrHub). Basically I'm left wondering whether this move at this time killed all the momentum Bitchat had until now. My experience today was that most rooms on the app are essentially dead, and the ones that are working are those still using the global relays.

Soooo, with relays , you did your own nostr concurrent ?

awesome View quoted note →

web apps are already migrating to georelays. the list is public on GitHub so all can stay in sync.

Requires google play services? Bah.

If i live and spend 99% of my time where I'm not in Bluetooth range of anyone else, do i have any use for this app?

... and u?