I have a particularly based trans friend who absolutely will not allow me to call them they/them for this reason 😹
If anyone at BBB wants to hang out, reach out! I should be at the Hilton later in the afternoon.
Let's go gay camping! We have rainbow campfires, baked jellybeans, and mushroom hotdogs. And the company is fabulous, honey.
#artstr #aiart #midjourney #gay 
Slides for the presentation I'm currently giving at PlebLab Startup Day:
https://cryptoquick.com/files/How%20RGB%20Colors%20Coins%20in%20Secret.pdf
I wrote a simple explanation of it a few months back. Hope this helps:
nostr:note1qqqqqrtr74wf0uk3fxx6aqzf09pc05e2zuxktc26wmqt38mgxmvs8p84j9
Feel free to ask questions, too!
Right now we're just satisfying the use case of shitcoins on Bitcoin except with full privacy and minimal impact to the timechain (unlike Ordinals / BRC-20). We think in the future, invoices and receipts used in swaps for purchases might be a decent use case. But for now, we're just trying to satisfy people's demand for degen on Bitcoin without telling them to go buy an actual shitcoin, especially to pay for fees, with RGB they can make their own for free, but they'll need existing UTXOs, and will pay fees on transfers as the outputs are spent.
Remember, if your belief is to tell people to use something other than Bitcoin for anything they want to use it for, you're bearish on Bitcoin and not really a Bitcoin maxi.
They had me at "written in Rust"
Would love to support this as a Carbonado frontend.
GOSSIP USERS: If you use 'unstable', it is about to get a data migration. That means you can't just switch back, your data won't match anymore. If our luck is bad, the migration will have to change and you won't be able to keep the new migrated data. So for those that want to try to run 'unstable', I strongly recommend doing it under a different profile until it gets merged into master, or if you prefer, backing up your LMDB directory first.
To run as a different profile, set (and export if setting at the shell separately from the command) the environment variable GOSSIP_PROFILE to the profile name. For example:
$ GOSSIP_PROFILE="unstable" RUST_LOG="info" ./target/release/gossip
or if you prefer
$ export GOSSIP_PROFILE="unstable"
$ ./run.sh
If you don't want to use a different profile, you can backup your LMDB instead. Your LMDB directory is your data directory (see https://docs.rs/dirs/latest/dirs/fn.data_dir.html) then "gossip" then "lmdb". I tar it up and zstd it, but you can just move it to a different name. Just don't do that while gossip is running.
What is this data migration? I've extended the Settings structure with a lot more settings.
Noted! For others on Linux, the command to do the above would be: tar --zstd -cvf gossip-db-backup.tar.zst .local/share/gossip/lmdb
zstd compression is definitely worth it; gzip compression for my LMDB directory produced a file 362 MB in size and took 1.6 minutes. zstd produced an archive 49 MB in size and took only 10 seconds.
I also experimented with xz compression; that produced an archive 37 MB in size, but that took over 4 minutes to compress.
If you're not mad as hell about inflation, we're probably not going to agree on anything that actually matters.
8% inflation is nearly a month's worth of wages, lost. All so the rich can continue to borrow money they'll never have to pay back, and the government can spend money they don't have and don't have to ask for. Inflation is the most regressive tax there is.
It concentrates wealth into the already wealthy, and robs purchasing power from those who can least afford it.
I could give a shit if you're cool with the fact that I'm a man married to another man, or that I identify as being a mountain lion person on the internet. That shit doesn't matter when people can't afford to feed themselves because a weekly grocery bill seems to regularly exceed $100, when it didn't used to. Touchy-feely rainbow-washed identity politics doesn't solve this problem, and neither does socialism. In fact, socialism makes the problems that lead to price inflation far worse, in several ways.
I've also gotta say, I've felt way more accepted for being who I am in the community of Bitcoiners than I've felt amongst those who don't understand money. If you know what a Rai stone is, chances are, you're alright.
There's value in both appreciation and skepticism, but the value depends upon the quality of either.
A new release always gets the adrenaline going! Not sure if it's getting any easier, but we're definitely getting better at it. The product feels like it's maturing now, there's so many features that were once placeholders that now actually work. The team pushed hard on this one.
I used to work for InfluxData before they started the transition and now I'm a Rust developer. I would go back to work for them to go full circle, but I work in Bitcoin now.
Cute! I've got you added. You have a cute ID, birb.it, but you can also use ingwie@nostrfurs.com should you ever want to.
Every dang time
Contrary to the name, I don't do crypto for this reason, and I don't recommend it. Insiders always dump on unsuspecting retail investors.
Sure! As you can see, we need a little help breaking out of the Bitcoin bubble. At some point I'd like to run a relay for furries and make it so the website orders users by when they last posted, so more active users are shown first
Hi! Glad to have you here! Would you like me to add you to https://nostrfurs.com ?
In cryptography, timing can be incredibly important. Some things are made to be intentionally slow, like the argon2id cryptographic hashing function, to consume lots of memory and computation to mitigate brute force attacks.
Some things are made to be faster, like signature algorithms like secp256k1. This doesn't compromise security, but it does improve node syncing performance, and reduces hardware requirements.
Finally, some things are built to take a constant amount of time, especially when handling keys or other secrets, because certain inputs can reveal the secret depending on how long the operation takes.
Ensuring code gets executed in constant time gets complex and often this guarantee can be broken as compilers update over time. To humans, it looks like secure code, but computers just see inefficient code.
Cryptography is complex and there's a lot to know. This knowledge is built up over a lifetime. There's still a lot I don't know, perhaps some cryptographer is cringing even as I write this, but it's just what I've been able to gather so far.