The same side of the Moon always faces Earth, but not in exactly the same way. Due to its tilted axis and elliptical orbit, we see about 59% of its surface over time. This simulation compresses a year into 60 seconds, making the Moon's wobble, called libration, visible.
[📹 NASA]
https://video.nostr.build/bfbd2551b883589f665e7a51f8edbdba1a8446ee87c8f0c56bf04b2fda5a65f0.mp4
beautiful although i think not totally accurate
I mean a simple client-server + decentralized would be cool
Should we all just gang up and start using BitTorrent? nostr:nevent1qvzqqqqqqypzqamkcvk5k8g730e2j6atadp6mxk7z4aaxc7cnwrlkclx79z4tzygqy88wumn8ghj7mn0wvhxcmmv9uq3jamnwvaz7tmswfjk66t4d5h8qunfd4skctnwv46z7qpq0whdnwrrhu0khs96vm7vncfzw87p89accdj5u4h7aq9luuzzzacq9jsvq5
why torrents? why not a simple client-server with https://github.com/hzrd149/blossom
yes i mean nostr-related, something in the browser not mobile, for long videos. didn't know storage is such a big deal
almost not working for me, can only see 2 videos one of them is broken.
i found https://zap.stream/videos is better but seems still too early
#asknostr where is the youtube alternative?
sent from coracle either way. they private?
how can I DM? it is in a good state but I'm shy until I complete some features.
basically it's a single html file linked to a js hash router that renders html elements and js
Thanks, after much analysis paralysis to pick a framework, I took an advice from a golang dev (not a frontend dev) to just keep it with vanilla, and it just worked for me, but yes I only did simple things and haven't worked on real projects, still can't see what vanilla can't do.
been building a NIP-99 client, just the fact nobody is using vanilla makes me feel awkward and missing something very obvious that I will find out later.
I thought it may be good to share (do you agree?):
"I'm not really a frontend dev so take my opinions as Grandpa Simpson shouting at the clouds. Honestly, for most cases, plain HTML, CSS and JS is just fine for what you need. A lot of the tooling to "make things easier" (on the unfounded premise that vanilla is too hard) ends up making things harder. So instead of having a single HTML file with CSS and JS in it, you now have to contend with some framework concepts and conventions. Guess what? You're now divorced from the technology that underpins it and are now dealing with an abstraction. Something goes wrong, a version of one of the thousands of dependencies has a bug in it. Now you're hunting around forums trying to solve a problem for a tool that was supposed to make your life easier. Even worse, none of the knowledge you have is transferable to other frameworks so now you're in this technology echo chamber and instead of having frontend developers, you have "react" developers, who manage concepts like "react component lifecycles".
Plain HTML, CSS and JS are so well documented, you're only upskilling, not "trying to fix build issues".
No build times, instant reload, well documented, no weird concepts. What's not to love about Vanilla?"
Thanks, after much analysis paralysis to pick a framework, I took an advice from a golang dev (not a frontend dev) to just keep it with vanilla, and it just worked for me, but yes I only did simple things and haven't worked on real projects, still can't see what vanilla can't do.
been building a NIP-99 client, just the fact nobody is using vanilla makes me feel awkward and missing something very obvious that I will find out later.
I thought it may be good to share (do you agree?):
"I'm not really a frontend dev so take my opinions as Grandpa Simpson shouting at the clouds. Honestly, for most cases, plain HTML, CSS and JS is just fine for what you need. A lot of the tooling to "make things easier" (on the unfounded premise that vanilla is too hard) ends up making things harder. So instead of having a single HTML file with CSS and JS in it, you now have to contend with some framework concepts and conventions. Guess what? You're now divorced from the technology that underpins it and are now dealing with an abstraction. Something goes wrong, a version of one of the thousands of dependencies has a bug in it. Now you're hunting around forums trying to solve a problem for a tool that was supposed to make your life easier. Even worse, none of the knowledge you have is transferable to other frameworks so now you're in this technology echo chamber and instead of having frontend developers, you have "react" developers, who manage concepts like "react component lifecycles".
Plain HTML, CSS and JS are so well documented, you're only upskilling, not "trying to fix build issues".
No build times, instant reload, well documented, no weird concepts. What's not to love about Vanilla?"
what have you picked? why is vanilla javascript a no-no for pro devs?
it looks like it was paid for with shitcoins
For years I've seen people asking for a way to request only IDs from a relay and not the full event, so I suppose there will be great public commotion when it becomes known that https://github.com/fiatjaf/nak now supports this very dangerous flag:
~> nak req --ids-only --since 'yesterday' -k 20 offchain.pub
c4888c4ea325677cd56798c28ea70a2a21ad15899c11e25973e7fe8d10681dd1
0d19706d839fc529f061dd477d317f6d32ce708bace2f689be02b2607142b9fc
f278ada73cce757b91f1733636a698b93cd7985417b3a7f141bd900a85a074de
328e05fcf397085ff19fe10ff9ee5592590b68f584fce9e2484b271e2852f35e
1ad4890180b12ff569aef251211ea645674cec555ecaf702dc812c5a1d162a80
11c84308a092f5ac8fbf226b3ec968ac42c961b9435a722229a06fbf10a66ff8
0ecc3972d3715a13f181a16bc437897a8d477fd722ba3cea55c996cfa2af1f77
d1f4260bdb40aa3049600d94fd9bb6ce43464d2b329478f6aa363ea33805a3a0
17781a89078d3eb5b63db6ce95026d2ce00b086d98aafc436e64bb093425d8a7
6957568c6412cad04f4e2b869e7d9af4be58f4483123207d2b9fd65c9a1e1004
0918ffa33aa95bcc1ecff96627c8e7224c29692e58948e219b1388bd7155dcbb
d9b0a89fce1102e9048f08705b724c37558969ff2e47c657a73c2c83231c4f8c
91747d307329bf7e35c195a504b4cbc4a18b2e2210bbb82606966a19b856e0c0
8aa7ab17361a4159732cb3c6cfb391a85ea90677cba2f70e32ce6c70f7b57f27
3de79712e48dbe8fa41d4b4cc707a54dbce92609b2eca69073a7e740faf4366c
f966742694ca67b1dcb06d3953bbb3b0544b22c9dfb77b239eb98284e2232176
29a16716bd6372f091dd9f6e450321d8ca053258061e2b1382700a466eb679f2
540bd290bf1f8239bd2cf07334da7bf63a244eff0f6461039ec5f66de7417b6b
Powered by NIP-77/Negentropy.
very dangerous why?
Building the Bitcoin circular economy one relationship at a time, here with nostr:nprofile1qqsxqnz6zax7rxcdn2m8tgzvd4w2sz85pad3y9rja69qzayxjzlgz3gwdf3sy
I brew coffee daily, and because it's something I don't produce myself, I need to buy it regularly. Around a year ago, Otis bitmeyer started attending meetups in my area and with him he brought his home roasted coffee. At the time, the coffee source I had been using for years was having supply shortages so I was often running out of coffee and couldn't buy enough to have any in reserve. I jumped on the opportunity to buy fresh locally roasted coffee with Bitcoin directly from the roaster.
Now I buy all my coffee from Otis, and it's some of the best coffee I've ever had. I don't think I had ever drank coffee made from freshly roasted beans before because the difference is huge and I look forward to restocking every month.
After participating in meetups and working hard to earn Bitcoin instead of buying it, I've noticed something interesting. High quality goods that meetup participants need on a regular basis seem to be the most successful items when it comes to earning Bitcoin. If each participant can provide something that a few others in the group need each month, then the Bitcoin literally circulates amongst the members.
https://fountain.fm/episode/xbgxc8vcXlnsiZY8rrCu
#bitcoin #bitcoinmeetup #circulareconony #plebchain #coffee #meshtadel
That is the way 🏆
#asknostr anyone else likes vanilla javascript? let's be friends