Avatar
Josua Schmid
e989aa6e0137d52a410ecd89ae59f7adbfb0bdec9786b9181c3707954b4cfa69
Engineering software, brewing beer
Replying to Avatar Gzuuus

## Introducing LowEnt

https://lowent.xyz

Lowent is a new chat client that uses the concept of low entropy keys to create anonymous chat rooms. It generates a key pair using the SHA256 hash of a word or string, allowing users to create rooms with any combination of words or characters. Each room has its own key pair, so all messages in a room are public on Nostr through the public key of the room. This can be useful for creating public streams of notes, like live events or news.

In these rooms, all users are anonymous, as they use the room's key to send messages. Lowent stores the ID of messages you've sent locally to show them to you in a meaningful way. However, if multiple people are writing in the chat, all messages will appear to come from the same source, except for the ones you send. To solve this and add authorship to messages, users can log in with their Nostr identity, allowing them to write messages in any room with their public key as the author.

To make this cryptographically sound, users must sign the message they want to write in the room with their Nostr identity, creating a valid ID and signature for the event. The event is then published from the room's key, including the user's public key, ID, and signature, allowing others to verify that the user's public key has issued a valid signature for the event published by the room's public key.

Lowent also features cipher rooms, which encrypt all messages using the room's public key. Only participants who know the string used to generate the room can decrypt the messages.

Lowent is a work in progress and an experimental idea that needs more research and feedback from developers and users. However, it's a fun project that has the potential to improve privacy, as all users in a room use the same key to communicate, making it impossible to guess who they are or how many users are participating in a conversation. Apart from these there are many other features that are under development.

#sovEnt #atlantis

Interesting idea

Yeah, nobody was fired for buying IBM…

I often argue from the security angle: closed source is security by obscurity. Well-chosen open source libraries are clearly better off.

I have the advantage that we develop custom software. Normally the problem we solve wasn‘t solved already or the licenses are very expensive. So the customer mostly doesn‘t care what tech we use.

I‘m more often challenged over the choice whether a standard software should be used or a custom solution is needed.

Let‘s see what comes to mind first:

- LotR

- Clean Code, Clean Coder

- Das Kapital im 21. Jahrhundert

- Harry Potter

- Thinking slow and fast

- Name of the Rose

- Lustiges Taschenbuch (does this count?)

- Führen, leisten, leben

- Durch die Wüste

- Die Säulen der Erde

- Black Swan

Could it be that ChatGPT answer quality was at its peak a year ago because as soon as something is good enough capitalism kicks in and they press more users on the same amount of CPU/RAM to maximize profit? So another company must come and actually do something better?

From what Damus feeds me I cannot rid the impression, that the amount of nostr software increases rapidly.

This chart could be a good example for https://callingbullshit.org/

The range has been selected so that it looks like there was a plateau.

I love the example about how time does not pass:

1. Are they written as end-to-end tests?

2. Let‘s say using Selenium?

3. What‘s the abstraction level in practice? Is it „when I click button X…“ or is it „when a salesperson creates a discounted offer“?

Please tell me when I ask to much.

Do you outsource the programming work? Or are the Gherkin specs used in house?

What is AC?

I‘d like to start using Cucumber in the context of domain driven design. My problem is that the initial design phase of projects never leaves space for this budget-wise. While I learned in engineering school that 10% of the project budget is to be allocated for an architectural prototype, the situation on our agency projects is completely different. It starts from selling the shiny thing and then underpinning the business logic in a move-fast-break-things manner. We are at least disciplined enough to have 100% unit-test coverage. But how do I make a proper argument for long-living domain logic tests which are readable for the business side and serve as a discussion base for business model design changes?

I just listened to Joe Rogan #2109 with Abigail Shrier. Then I felt the sudden urge to listen to „Skills in Pills“ by Lindemann. I have a new angle to this song now: „All the left is right“