Unable to screenshot atm, but upon opening the DM tab, the input box briefly flashes on screen, then vanishes. Messages load but do not scroll. (This under firefox-esr on Linux, will test via Chromium when back at desk.)
That's the guy.
"NOOOOOO! YOU NEED 2 LAPTOPS AND 53 CD-RW's TO EVEN THINK ABOUT SECURE BITCOIN!" - Some moron with a Chewbacca pfp whose name I forgot.
Just deployed a massive redesign of Snort.
Say hello to Snort V2 design, huge shoutout to nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac as usual.
https://void.cat/d/RGhg4innbi5cTEfgV1DReP.webp
https://void.cat/d/JkpX5fmKyzGwMASB54sLSU.webp
As usual there are a few rough corners but we should get to them very soon, if you notice anything glaring please let me know.
This redesign has been in progress for over 2 months, the PR changed almost every file in the project.
Tested the browser version, even after nuking cache search broken and the DM section overflows the page. Looks nice on the surface, but old version at least worked.
It's sorta like that bit in "The Office" where Ryan makes a blog for Creed, but it's really just a MS Word document.
GM #nostr and happy Friday!
You can shove any .rss feed into https://atomstr.data.haus/ and it will spit back a npub to follow with the feed. With YouTube it's a bit more involved, since they don't advertise rss but tl;dr is you grab the channel ID and add it to this crafted url: https://www.youtube.com/feeds/videos.xml?channel_id=THE_CHANNEL_ID_HERE
Add one of these relays:
wss://nostr.data.haus
wss://spore.ws
wss://relayable.org
Everytime a new video/stream is posted to memefaggotry YouTube, it will automagically post here.
Extremely rare nostr:npub1zh36wt34eav4tugmd3r7f4tr99suj6p9ps2ezneugdvyfvrw3rpqtx4qq9 pepe, do not steal. #pepethon
ok more from the vault for #pepethon
#pepethon
Reply: "Ada gonna fall like Charles Hoskins did out of that helicopter in Afghanistan while working for the CIA. Ada not likely to limp back though".
?cid=586b07f0yqvo3c3jnvmn3tkunujd6i79iss17hiwdbbivsbt&ep=v1_gifs_search&rid=200w.gif&ct=glol it's 42°C today where I live. I'd be outside grillin if only 32. 🤣
Out of curiosity, which lightning setup are you using?
Tried with 10, then 5. Still same:
ERROR: Payment failed. Does the receiver have enough inbound capacity? (no_route) (Request failed with status code 400)
According to the dashboard I have 55 sats of incoming capacity. Did you send less or more than that?
Ah I zapped higher amount than inbound capacity so that explains it.