I'll try my best with a few highlights I think are important. As with all shared libraries noscrypt was intended to allow for the more flexibility in configuration and builds, while avoiding many assumptions. - Devs can choose from a couple crypto libraries, such as mbedTLS, OpenSSL, or Windows BCrypt at the moment. - Noscrypt does not allocate dynamic memory unless utils are used - Noscrypt uses a crypto library abstraction which supports user overrides at a function level - Does not expose any source of entropy/randomness, to avoid opinionated and "hard-coded defaults" - All low-level apis are bring your own memory. - Abstracts encryption/decryption to support both nip44 nip04 (incomplete) and future algorithms - Does handle any character encoding/decoding (base64) yet, but may offer it as a utility I also have a longer form blog I wrote last year in more detail. Essentially I didn't want to roll my own application specific crypto, with limited options and a highly specific use case for my NVault project. https://www.vaughnnugent.com/blog/d9ab8a46cfa8d6bd59cf048fec8d73ffc44f881c

> And a mom who is politically active. Found it! That's the one! > The flights were full of foreigners, by the way. LOL XD Im sure international flights do be like that.

As I'm seeing more projects release "hand-rolled" encryption and key operations. I know I need to step up noscrypt advertising. If you're building an application (client, server, desktop, etc) that targets x86_64 I maintain a library that will do your nip44 encryption and basic key operations for you :) It's called noscrypt - Noscrypt gives you consistent abstractions for nostr encryption algorithms. - Your choice of highly tested backend libraries such as mbedTLS, openSSL or BCrypt API on Windows - Advanced validation and error feedback - Low level API gives you full control over memory - Low level API will never take control of your process with allocations, aborts, forks, or threading - It has automatic fallbacks for options and platform limitations (relies on monocypher for some fallbacks) - Offers a static or shared library - Includes versioned and hand verified copies of dependencies so you don't need internet access to build once you have the package - CI tested on Windows and Linux x86_64 platforms. (more tests coming soon) - Doesn't rely solely on GitHub or public infra It also includes a C# library for .net devs :) More bindings may be coming soon. https://www.vaughnnugent.com/resources/software/modules/noscrypt

What makes a Christmas movie?

I don't that's necessarily a bad thing. But the fact that node runners have to fight over core/knots is nuts to me. It just misses the bigger picture. Reinforces and idea of poor allocations of scarce resources.

I'm testing out OpenObserve.

edit: platforms *than* adoption...

I just get to see a blip, for a minute or so, then bam, right back to normal.

I'll still die on that hill though. I made a shitty balance watcher in like 50 lines of C# with an rpc connection. LN is retarded. My complaint is it is so simple yet no wallet offers it.

Okay, it's really fun watching abusive traffic spike, balancers suppress traffic, then watch the IPs get banned by crowdsec remediation. Now with pretty graphs and charts XD

That was me. I was they... damn

I have a buddy in email marketing. Pick an eCommerce company between 50-400 mill/year revenue and he probably knows the company managing the email lists, capture portals inboxes and patterns. They have an average roi of something like 300%. I don't remember more exact numbers but it's asinine. They claim an average across the entire company is about a 40% CTO rate. They have meetings and confidences, in public, calculate where to but the close (X) button on a form every 6 months so that websites get maximum user email capture. Users get used to where the buttons are over time and some websites train people differently. They often close the offer out before reading it, and if you make it so that they feel like it won't go away without entering their email, they won't, and therefor the company is missing out on a returning customer XD Im told they have monthly industry meetings to calculate compliance costs. Like, - Do I have to make a working unsubscribe button if the user is in X state - What happens if we wait more than 30 days to remove them from the list if they've already unsubscribed - They said the _link_ has to work, it doesn't say the button has to work - California requires unsubscribe actually work, but no other states do... - After how many emails per day so the user CTO drop? Last year I was told for most eCommerce segments about 3 emails/week was peak, any more and it fell off. Sometime this summer I was told it's gone to 2/day is peak. One when users wake up, and one in their evening. These things are a calculated science. If you want to know what malevolence is going on in the world, find someone who's trying to sell it, they're not hard to find, and they will brag all about it.

Why can't we just have thin-client wallets that can use our own nodes as a read-only source of truth?

Working on my dashboards and saw a little 50-60 rps "DoS" across 3 IPs. L4 and L7 rate limiting working well and crowdsec quickly detected and blocked the IPs causing trouble. One of the worst offending IPs. https://app.crowdsec.net/cti/91.224.92.138

I've you haven't heard me rant about this, I'll spare you my whining, and instead you can listen to Linus Torvalds from 2021 instead. I think we should make tarballs great again. I ship my basically everything as tarballs. However they lack the "install" part, which is where something like makeself can come in. I just think it's whack that I can ship binaries for Windows platforms and the CRT is so compatible that it's expected to just work, and does most of the time. More specifically shared libraries. I'm a big fan of the idea of shared libraries, but we just can't trust compat on Linux so we all build giant statically linked apps. Look at every Go and Rust app that ships 3-50mb binaries. Finally don't get me started on containers, HN took it all out of me. www.youtube.com/watch?v=Pzl1B7nB9Kc

Damn, clipboard got me with that meet link...

Me instead. XD

It sounds like you're on a R & M bender? I might join you.

XD Yeah I think Im at 4 years on my big units. They're cyperpower units and the batteries are packed in a steel cage you purchase as an assembly. Its like $200/pack iirc so it's not terrible to buy them, but if I can save a few bucks that would be nice.

I think mine was about 8 years old when it failed like that. It was the original battery, so 8 years is a lot to ask from an SLA battery. It was in a closet where a return air duct was, when the hvac turned on it blew nasty smells out with a little smoke. I spent like an hour tearing the furnace apart trying to figure out then eventually traced the smell back. Never tripped the circuit breaker just sat there smoldering when the battery pack went dead short internally (pretty common for me). I was quite impressed.