• Why the Change?
• How It Works: The “Pay-to-Lock” Mechanism
  • 1. The Payment Request
  • 2. The User Experience
  • 3. Server-Side Verification
  • 4. Locking the Room
  • 5. Unlocking and Relocking
• Transparency and Code

At Hivetalk, our core mission has always been to foster open, public community discussions. We believe that the best conversations happen when they are accessible and inclusive. However, we also understand that there are times when #privacy is necessary—whether for a private team meeting, a confidential discussion, or just a quiet chat with friends.

For a long time, locking a room on Hivetalk Vanilla was free. As we continue to grow and refine our platform, we’ve made the decision to introduce a small cost for this premium privacy feature.

§Why the Change?

The decision to put a price tag on room locking is driven by two main factors:

1. Encouraging Public Discourse: By keeping public rooms free and accessible, we encourage users to engage in open conversations. We want Hivetalk to be a bustling hub of community interaction.
2. Sustainability: Privacy isn’t free. Maintaining secure, private connections requires resources. By charging for locked rooms, we can sustain the platform’s growth and continue to provide high-quality service for everyone.

§How It Works: The “Pay-to-Lock” Mechanism

We’ve implemented a seamless Bitcoin Lightning payment gateway directly into the room locking flow. Here’s a technical breakdown of how it works under the hood.

§1. The Payment Request

When a room host clicks the “Lock Room” button, the client initiates a request to our server. instead of immediately locking the room, the server now triggers a payment flow.

§2. The User Experience

On the client side, we use the bitcoin-connect library to display a payment modal.

§3. Server-Side Verification

Security is paramount. We don’t just rely on the client saying “I paid.”

§4. Locking the Room

Only after the payment is verified does the server allow the room to be locked.

§5. Unlocking and Relocking

If a host unlocks the room, the Paid Lock flag is reset. This means that if they wish to lock the room again later, a new payment will be required. This ensures that the cost is associated with the action of securing the room for a specific session.

§Transparency and Code

We believe in open source. The entire implementation of this feature is available in our GitHub repository. We’ve added robust logging and error handling to ensure that payments are processed reliably and that users are always informed of the status of their transaction.

We hope this change allows us to continue building a robust, privacy-focused, yet community-centric platform. Thank you for supporting Hivetalk!