Mtg

Hello there!

Public Key

npub1zug85tns97cfxafjpa2rh28d45d6h4txgxt3vr8rxe9czr85j47qntdx38

Profile Code

nprofile1qqspwyr69eczlvynw5eq74pm4rk66xat64nyr9ckpn3nvjuppn6f2lqprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqywhwumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9ws2r6kkl

Publishing to

relay.snort.social

nostr-pub.wellorder.net

nostr.swiss-enigma.ch

relay.damus.io

Author Public Key

npub1zug85tns97cfxafjpa2rh28d45d6h4txgxt3vr8rxe9czr85j47qntdx38

Show more details

Last Notes

2023-12-20 07:35:35 UTC

- reply

Yup, you'll be able to request a nostr badge for any badge you get.

2023-12-20 07:34:50 UTC

- reply

After you get any badge on your bolt.fun profile, you will be able to choose a nostr pubkey to which you want us to issue the nostr badge to. This is for the case where a maker has multiple nostr keys connected on his profile.

2023-12-13 10:46:32 UTC

- reply

Really glad to hear that!
btw, the design of the app is SUPER nice & easy to navigate through!
Great work on that!
Looking forward for when the app is ready to be used.
So keep us updated.

2023-12-13 10:40:00 UTC

- reply

The work that you've been doing on this project guys is truly admirable!
Wishing you the best of luck.

2023-11-28 08:41:22 UTC

- reply

Really nice work Bruno! 👏

2023-11-22 09:43:26 UTC

- reply

Nice! 👏👏

2023-11-17 10:52:13 UTC

- reply

Ah, I see.
This is indeed a nice approach.
Thanks for sharing!
I think it shouldn't be long before generative AI will be able to generate consistent media. & once that happens, it will be a game changer.

2023-11-13 10:39:12 UTC

- reply

Yes please!!
This will be very useful & saves everyone a lot of time recreating the same parts over & over again.
Keep us updated on this project's progress.

2023-11-13 10:31:13 UTC

- reply

Nice work.
I'm particularly impressed by the art works being generated by AI.
One of the main drawbacks of AI generated art is consistency, but I don't see this issue here.
How are you able to generate different art works while maintaining the same style??

2023-11-13 09:35:01 UTC

- reply

Nice!
I'm excited to see the new look of the app.

2023-11-13 09:32:04 UTC

- reply

This is super cool secondl1ght!
What were the main challenges you faced while creating this application??

2023-11-13 09:25:40 UTC

- reply

This is looking very nice, clear, & easy to use. 👌
I really wish we could migrate our voting in bolt.fun to use bitcoin connect. But I think we will have to migrate & change a lot of things in the codebase.
If I start working on a new project that needs lightning payments, I'll definitely start with this.

2023-11-09 13:31:45 UTC

- reply

Great tips Dalia!
Thanks for sharing.
I would also add a few things that came to my mind while reading the story.
\-- It's one of the biggest mistakes in new projects to not validate your project's idea before spending sooo much time working on it.
Naturally, most people would like to keep their awesome new project ideas close to their chest, work on it for a year or two, release it, just to discover that no one actually needs it.
The earlier you reveal it, the better.
Don't worry about people stealing it.
Ideas are cheap, it's all about how you implement them.
Also, the earlier you get feedback on your idea, the earlier you can steer your project in the right direction.
\-- "There are no stupid questions, just stupid answers"
This is especially the case if you are working on something lightning related or nostr related.
There are still a lot of use cases that we yet have to figure out the best way to approach them.
& the learning materials are still unfortunately too scarce. (That was one of the main reasons of creating bolt.fun)
So asking, & sharing with others will push the boundaries of what's possible, & make us reach the best solutions needed for mass adoption.
\-- It's VERY VERY VERY important that you continue working on your project after the tournament's ends.
The tournament end is not supposed to be your project's end, but its start.
Tournaments are just to give people some extra motivation to start working on that idea that they have putting aside for too long, & getting a chance to share it with other makers.
There are several projects who didn't "win" in the previous tournaments, but they continued working on their projects, & ended up receiving HUGE funding!
Finally, keep this picture in mind:
![](https://imagedelivery.net/wyrwp3c-j0gDDUWgnE7lig/61d671af-1fdd-4ad5-0b72-514e2c61a800/public)

2023-11-09 10:22:18 UTC

- reply

Another few points to keep in mind:
\- Having a nostr account connected in my BF profile does NOT mean I can use this account to comment.
To be able to comment means that I'm able to sign my comments using either an extension or some tool.
\- Syncing profile data between BF profile & nostr profile
These are 2 different profiles, think like your google profile, & any other profile you signed-in to using your google profile.
Updating one profile data doesn't mean (most of the times) that the other profile is getting updated automatically.
Cause there will be several issues if this would to happen.
Also, updating nostr profile data also requires signing the update event by the private key.
I personally think that we don't necissarly need to allow the user to update his nostr profile from bolt.fun
(& I think we should definitely not try to automatically update it)
2 reasons:
\- It can get out of sync easily. Whenever the user changes any of his info from any other nostr client, the profiles data will be out of sync with our BF profile.
\- We are almost not using the user's profile data anywhere.
We try to see if this nostr profile is connected to one of our BF profiles, & if so, we always display our BF profile data.
So we are not making any use of his nostr profile data if it's created on some other client.
\- Should we allow users to comment using a nostr profile that is NOT connected to a BF account??
Currently, we do.

2023-11-09 09:32:37 UTC

- reply

Nice!
Good luck in LoL2

2023-11-08 13:21:53 UTC

- reply

Hey Dalia & Lana.
The new UI is looking nice & clear enough imo.
But this will be a big restructure for both the commenting feature & some parts of the user's profile, so there are several things on my mind that I would like to throw.
I think first of all, we should precisely determine what are the problems or difficulties we have with our current system.
Are they actually problems that should be "solved"?? (Cause with nostr, some features are supposed to be in a specific way).
& How are the other nostr clients handling them.
I know that for people who don't know what nostr is, it's not that clear to use.
But at the same time, (& this is my personal opinion), we shouldn't confuse people who are already using other nostr clients & are expecting some things to work in a specific way.
I think the term bolt.fun identity will not be very clear on what it is.
I am not sure at the moment what it is exactly...
I think the first assumption will be that it means your bolt.fun profile.
I know that the modals content for when the user chooses the boltfun identity option are still not finished, so this might not be the case, but I would think that any user on bolt.fun has a bf identity, & it's his profile.
I think that's it.
I know my feedback isn't structured very well propably. So let know if you have a different opinion on any of the points.
Nice work tho. 👍👍

2023-10-31 11:50:42 UTC

- reply

I like the idea of your project.
& gotta say, the UI looks nice & neat!
Nice work man 👌

2023-10-31 11:14:36 UTC

- reply

That's awesome man!!
A lot of people would just discard his project as soon as the hackathon's end, when the MAIN goal of the hackathon is to give people the first push (& a possible monetary prize), hoping to encourage them to continue working on their project's ideas/prototypes to see it realized as full valuable projects.
Keep going man & keep us updated on your progress even after the hackathon.
Best of luck!

2023-10-28 14:37:51 UTC

- reply

👋👋👋

2023-10-28 14:27:20 UTC

- reply

I'm of the same opinion as Kumulynja.

2023-10-28 14:23:04 UTC

- reply

Well, this change must have been quite the challenge.
What made you decide on using basic tools/libraries like bootstrap instead of the more "modern" alternatives??

2023-10-28 14:13:40 UTC

- reply

The UI is looking very nice & "natural" 😁with this palette.
Also, I like the logo.

2023-10-28 09:46:19 UTC

- reply

Looks very nice man!!
Very seamless & the UI is good 👌

2023-10-24 08:22:57 UTC

- reply

Nice!! 🤩

2023-10-16 07:51:00 UTC

- reply

I'm very looking forward to this one!!
In the last hackathon, I tried adding 'nostr-connect' to my workshop project, but unfortunately, I wasn't able to get it to work reliably, so I had to omit it. (Maybe my usage of it was wrong 😅)
But if it works nicely now, this could help a lot with some nostr features on websites that are currently not very UX friendly.
Please keep us in the loop of this project's progress.

2023-10-16 07:31:40 UTC

- reply

I LOVE the new website! Looks very cool👌🤩
& thanks for sharing the video, will definitely watch it soon.

2023-10-12 11:17:56 UTC

- reply

Well....
I think I'll change the rendering method again to the old one because I discovered that the image above broke for a very specific case, which is that the image tag was immediately after a link, & there was no space between them, so any markdown renderer wouldn't consider the image as an image, but a part of the link. (& that's the right way), so I had to revert this part which means the image above will break again now...
But uploading the images is now working properly, so @SF feel free to re-upload the image & make sure there's a space or a new line after the link, & it should work.
Thanks for bringing our attention to this issue 🙏.
Testing Image 1:
![](https://imagedelivery.net/wyrwp3c-j0gDDUWgnE7lig/589a3d36-6a91-4ace-af54-e0dd52015400/public)
Testing Image 2:
![](https://imagedelivery.net/wyrwp3c-j0gDDUWgnE7lig/df090ef8-d6d7-4e93-95e8-88cdf0396000/public)

2023-10-12 11:10:51 UTC

Hello World!
Here are a bunch of images:
![](https://imagedelivery.net/wyrwp3c-j0gDDUWgnE7lig/db795794-8670-48b4-4310-bbfdcf661c00/public)
Image 2: ![](https://imagedelivery.net/wyrwp3c-j0gDDUWgnE7lig/b708730c-7e99-4821-f711-50cb8d1d4800/public)
Hope you like them

2023-10-12 10:57:04 UTC

- reply

Technically, rendering images in comments was working previously, however, in the case of the comment above, there was not space between the text & the image text, so it ended up being not parsed.

2023-10-12 10:49:04 UTC

- reply

Well....
Now it is!! 🎉🎉

2023-10-10 07:23:35 UTC

- reply

The nostr client is only front-end. (So it's mainly javascript).
What you have on the back-end is totally up to you.

2023-10-09 12:09:03 UTC

- reply

Hey there
So regarding the Nostr Login, I gave a workshop in the last tournament that included that, the workshop was 2 parts & you can find it here:
[https://www.youtube.com/watch?v=O9bzEvv-oFE](https://www.youtube.com/watch?v=O9bzEvv-oFE)
[https://www.youtube.com/watch?v=djUS6GvU9pM](https://www.youtube.com/watch?v=djUS6GvU9pM)
Depending on your use case, you will likely still need some addition parts, but this should give you the core needed for a nostr-login.
Good luck.

2023-10-06 09:20:58 UTC

- reply

Hey there!
The stack that you should go with of course depends on your projects' requirements.
But if you don't have any previous experience with web technologies, then just proceed at first with the bare basics that is enough to get you an MVP.
So for example, on the front-end, just learn the basics of HTML, CSS, & JavaScript. (Probably not a framework cause that will take some time). & you could also use some ready templates or use one of the apps that allows you to build a web page using no-code or low-code. (But since you need some nostr features, I think you will have to go with an option that allows you to write your own javascript)
For the back-end, nodejs in my opinion can be learned quickly & used to build small apis in no time.
If you have a good python knowledge though, you could also look into backend frameworks for Python like Django & Flask. Flask in particular is very easy to get started with.
And yeah, that is my opinion.
If you have any other questions, just shoot.

2023-10-05 12:52:27 UTC

- reply

I like this use case 😆😆

2023-10-05 12:36:57 UTC

- reply

Hey Lana
I'm going to start developing the front-end components for this feature next week.
So I had a couple of thoughts on the UI of the badges components that I wanted to share with you.
\- We should consider that the badges description will in most cases be longer than 1 sentence. Since we will be using the badges to educate people about some parts of the platform that they might not have used.
So I think the description for some badges will be multiple lines.
\- The images are nice & neat. But I feel that they are a bit too "abstract" or "generic".
I saw the images at the top of the figma file (the ones that seem to be generated using mid-journey) & I think they look more "interesting".
\- The progress bar should be bigger so that in the case of badges that require a lot of progress steps (e.g. write 50 stories), the progress is kind of visible.
\- I think it would also be a good idea to have a progress count close to the progress bar somewhere (saying something like: "14/30")
For most of the points above, I think making the layout of the badges component list-like instead of grid-like would fix them.
So the items list would look something like:
\\\\\\\\\\\\\\\\\\\\\\\\ TITLE
\\\\ IMAGE \\\\ PROGRESS BAR
\\\\\\\\\\\\\\\\\\\\\\\\\\ DESCRIPTION
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\\\\\\\\\\\\\\\\\\\\\\\\\\ TITLE
\\\\ IMAGE \\\\ PROGRESS BAR
\\\\\\\\\\\\\\\\\\\\\\\\\\ DESCRIPTION
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\\\\\\\\\\\\\\\\\\\\\\\\\\ TITLE
\\\\ IMAGE \\\\ PROGRESS BAR
\\\\\\\\\\\\\\\\\\\\\\\\\\ DESCRIPTION
Let me know your thoughts on my thoughts 😄

2023-08-02 08:19:32 UTC

- reply

This was a really nice & useful read! Thanks for sharing with us.
I personally strongly believe that a PM can make a huge difference for projects in hackathons that are 1-2 months long. It's hard otherwise to stay on track for a team of more than 2.

2023-02-07 12:49:12 UTC

- reply

& this is the second comment