Vic's avatar
Vic
vic@cornychat.com
npub1yx6p...7kza
https://i.nostr.build/Lqsu56YxOCvwc6G5.jpg πŸ’¬ cornychat.com - audio spaces πŸ–ΌοΈ nodeyez.com - bitcoin node images Recommends: πŸ₯£ zap.cooking 🎡 tunestr.io πŸ“² relay.tools πŸ’© turdsoup.com πŸ₯” oddbean.com πŸ”£ listr.lol πŸ•ΉοΈMy Nintendo Switch Code SW-7592-4594-7016 About: I do programming, databases, data parsing, reports, visualizations. Bitcoin maxi. Available for hire Corny Chat (https://cornychat.com) operator, running the first open source audio spaces integrated with Nostr with support for zaps, room customizations. Nodeyez developer (https://nodeyez.com) providing sovereign scripts to get more from your node. It can generate images from your node accessible in a website dashboard or slideshow output to an attached display.
They send these out whenever they have something flying overhead that they don't want people to see image
On a vacation this weekend and weather has been cloudy and cool. Meh.
Corny Chat is currently up but not talking to nostr for server side stuff. - no zap goal refresh - no live activity publishing - no scheduled events - weekly high scores won't publish Client side should let you join room if previously authenticated or enter anonymously. - zaps are likely broken - live activity text may he broken - slides and link save/load may not work View quoted note β†’
My primary development goals for Corny Chat this year will be to 1. Figure out how to build and include patched versions of nostr-relaypool module or.. gut that logic and just use a single relay 2. Decouple dependencies on nostr relays to operate so that the app can fail more gracefully when the relays puke. 3. I may have to setup a relay in the stack but that would really suck. If anyone knows a good way to talk to multiple nostr relays with a npm module from a react app let me know. No I won't rewrite the app in something else. At this point I'd consider decommissioning the service if I can't get through #1 above.
Decided to rewatch Braveheart Really good movie. One of my favorites
Just released a new noncast episode. You can't listen to it here.
The researchers found that these vulnerabilities exist in five popular home routers β€” Netgear Nighthawk x6 R8000, Tenda RX2 Pro, D-LINK DIR-3040, TP-Link Archer AXE75, and Asus RT-AX57 β€” two open-source firmwares β€” DD-WRT v3.0-r44715 and OpenWrt 24.10 β€” and across two university enterprise networks. This shows that the issue is not just limited to how manufacturers make and program their routers. Instead, it’s a problem with Wi-Fi itself, where its architecture is vulnerable to attackers who know how to take advantage of its flaws.
🚨 CORNY CHAT UPDATE!! πŸŒ½πŸ’¬ It's been a few weeks since the last update. For now, I'm shifting focus to bugfixes instead of new features until satisfied with the overall stability again. 🌟 Improved user feedback in zap invoice panel - LUD-06 responses that are errors can return as a 200 status ok response. This is a weakness of the specification but valid. - Previously, Corny Chat expected a wallet provider to supply a payment request matching the specification if the lightning address was valid. Alby, does not always do that, and may return a error message instead. - This enhancement halts the spinning wheel animation after requesting the invoice and bubbles up that error to the user so they know the cause and have steps to resolve it. 🌟 Zap Goal Improvements - A new background process on the server tallies server infrastructure zap goal balance across configured wallets from LNBits. This is cached (updated hourly) to improve performance - A new endpoint allows for retrieving the zap goal balance - Server zap goals now prefers fetching balance across configured wallets from LNBits, but if unreachable or 0 balance, it will fallback to the traditional interrogation of nostr relays for zap receipts - For Corny Chat, multiple wallets are configured. All payments to vic@satsilo.com or cornychatdev@satsilo.com get accumulatd towards the infrastructure goal Build 20260226.1214 #audiospace #cornychat #foss
↑