#nukestr 🤯 nostr:note12eekgvmm8k90l6s32gvdcd07q3f55hl39wkfknak7yl3r243lezqrc9pv2

went through a lot of personally traumatic shit this week and all I can say is it's a necessary and healthy process. it's kind of cathartic to have to go through shit and find the other side. there is no yin without yang. ☯️ Night nostr 💜😘

Goodnight and wabi sabi, Nostr!

Hug your loved ones. 🫂💜🤙🏻

Imagine you're invited to a big Nostr event in your city. You arrive there and all you see is a giant piece of paper with JSON printed in it.

I have been quiet lately, but it is for some good reason.

I am turning my medical device company ( eyenetra.com ) into an open-source project.

As some of you may know, I spent the past 15 years trying to increase access to eyeglasses by developing and shipping a new class of vision-testing devices. Even though we shipped thousands of units and served millions of patients, Nostr made me realize what I was missing all along: true decentralization.

All of our hardware designs and software will be made available to the FOSS community to build their own vision-testing devices and services. And I am going to be working with design/manufacturing partners across the globe to bring them to the market in as many variations as we can.

It has been a long process but I finally have all approvals to make it happen. Thanks to all my shareholders who believed in this idea and allowed me to make it happen.

The future is bright.

If you are in a foreign country and don’t know how to eat some local dish, you can take a photo and ask chatgpt how to eat it.

I’ve also been the photo feature to identify plants and shells.

Any other cool things you’ve used it for?

One useful way to think about nostr is as a social layer for the Internet protocol stack.

Big Tech companies had to build a proprietary social graph layer within their vertical since a social graph makes (almost) everything information-based better.

Nostr pushes out the social graph from the application layer and allows smaller applications to be built on top.

#ZappyHalloween! 🎃💀⚡️👻🧛🏻‍♂️🍬🍭⚡️

Reply with your best Halloween memes for a treat!

Welcome to a text based RPG GROUP GAME by #[0]. We have selected a Halloween themed game. Anyone can participate and affect the outcome but you MUST reply directly to each specific action message with only the action number itself. The first reply each round will decide what action is taken. A pool of 1000 satoshis will be split among all that participate correctly if the game is won. Good luck! This game will time out in 6 minutes if no one responds. #games on #grownostr #bitcoin

Round 1:

You find yourself stranded on a desolate road in the middle of the night. Your car has broken down, and there is no sign of civilization nearby. As you look around, you spot a dimly lit house in the distance. It seems like your only hope for help. What do you do?

1. Approach the house cautiously.

2. Stay by your car and wait for help.

3. Walk in the opposite direction, hoping to find another option.

Choose your next move wisely. [1698776113]

Best food I’ve had in Tokyo so far 🍣 🍱 🍵 traditional breakfast, fish market bowl, red bean treat, waygu sushi, ramen xo #nostrasia #foodstr

Can it be joined via Damus?

Via reddit:

" I have been working on the side with my partner on an app since more than a year ago. I work a day job to pay off my student loans and lately, have been losing hope on the startup. At this point, I'm only in it because 1) of my co-founder and 2) I have already given it a year of my life. Everyday is a struggle to work on it. I joined my co-founder because I believed in the idea and thought it could be a hit.

Several iterations and several "pivots" later, we have still not launched the app. Pivoting too often and too much was a mistake. Even the current set of features of the app aren't really good enough.

My personal life has taken a hit, I'm not able to give my 100% to my day job. My personal relationships have suffered tremendously, and there's also a lot of "tech-debt" that has accumulated because of subpar quality of code by the freelancers. I'm just constantly fixing one bug after another and I have lost the energy because it hasnt been rewarding at all for me. I can't even sell my positions and exit.

I'm trying to gain different perspectives here and trying to find out what people have done when they found themselves in a situation similar to mine "

My thoughts ----

1. Beware of sunk cost fallacy. Just because you put a year into it, doesn't mean you're somehow going to make up for it by dedicating any more time.

2. It seems the problem is the "idea" stage. This is where a lot of "startups" fail. New ideas are hard to execute and you have to wonder why if it's such a great idea that nobody has done it that way. Chances are it's a bad idea.

If I were this person I would take my losses and get my life together, then learn from my mistakes hopefully and give it another go later (or not).

The problem with a lot of startups is that they are solving non-problems.

The cure--

First time founder should stick to something that is already somewhat validated. In other words, other similar things exist and try to solve the same problem. If you can identify at least 3 other profitable companies that are solving similar problems (or better yet, your exact problem you're trying to solve in a more novel way), then you have a validated market.

Try to bootstrap a solution. Give yourself an unreasonably short amount of time to ship a solution. Launch when you are 80% there. Have a plan B if things don't pan out.

A pivot in the idea stage before the product is even shipped usually means shiny object syndrome. This is where a "better idea" is begging for your time. It's a distractions.

It's good to ask yourself a few questions before even starting (btw I can't use colons here)

1. Who are my 3 competitors

2. Who are my customers? You should be able to give them a concrete title. Who are they and what do they do professionally? If the answer is "everyone" you need to start over.

3. What is my target market size - quantify it (chances are it's bigger than you think)

4. How will I distribute my product? (in fact, this should be your #1 question and priority).

Then, identify your product, who it is for and what problem it solves. " X is a Y for Z and it {solves this problem}"

If you get this far, now identify the absolute minimum product required to provide that solution. Often the product is not even necessary, or you can solve the product manually via a service. Do that service to validate the need for your product. Solve the problem manually for people before spending months building an automation.