Avatar
Howard Chu @ Symas
5aeb250b3075a12bd05e16c8a3c40da91a553fa92164a39915a3a0615fe51864
CTO Symas Corp., Chief Architect OpenLDAP Project, Musician

Symas contributes to development of nostr:nprofile1qyt8wumn8ghj7un9d3shjtnyd968gmewwp6kytcqyryd36fvkxz8nq24jqh2g8x50ge4hnv6nevq3usfag9xpzxg2e24c5gdg3c . I personally don't endorse Signal; their idiotic MobileCoin venture made it clear their priority is profit, not user safety.

You actually *can* get secure private messaging without relying on centralized metadata storage or AWS.

https://fosstodon.org/@cwtch/115464360100095502

A new engineer discovers how Cloudflare used #LMDB for their distributed config https://xcancel.com/UltraSive/status/1948967694004326605#m

"99th %ile of reads dropped by two orders of magnitude!"

"LMDB stability has been exceptional. It has been running in production for over three years. We have experienced only a single bug and zero data corruption. Considering we serve over 2.5 trillion read requests and 30 million write requests a day on over 90,000 database instances across thousands of servers, this is very impressive."

New for OpenLDAP 3.0 - forget about bothersome index configuration. Just feed your entire DB into chatGPT. Search queries will be answered immediately by #AI, without maintaining any indices.

It's not a "smart" appliance if it only works while connected to a 3rd party's remote server, and can be knocked out of commission by a WAN outage. Smart appliances should only communicate with your LAN. https://mastodon.social/@augieray/113501696022120792

Most sci-fi stories involving time travel involve a mechanism that's incredibly rare and/or difficult to operate.

What if complete plans for a working time machine, including its power source, were published anonymously on the web, in a decentralized fashion? (Impossible to identify who published it, or from where, and thus making it impossible to go back and prevent the publication.) What if anybody could build their own, using commonly available parts and tools?

It's only April and my PV panels have already hit a peak output over 10% over their rated capacity (yesterday). The power graph from today clearly shows the jump around 9am when the sun is finally in front of the house. The house faces SSW so the panels aren't getting direct illumination from sunrise, though they're still producing a tiny bit of power then.

Other cryptocurrency projects talk a big game about being the future of money, but they're all just scams to separate speculators from their cash. #Monero has demonstrated time and time again that it's actually focused on being a useful currency, not a vehicle for speculators. https://blog.bitfinex.com/education/the-fortunes-of-monero/

nostr:npub1zr8c805prvez5h93zkzvuhzevv7c32uexu8wnr8pq6xnqlclqrrqa3lmdn grooming is how cats assert dominance. Imagine the opposite, if the winning cat started doing what humans do.

nostr:npub1vkumxfw5c77ysdcgjqglw0a0usazt87a0q8y2jyu6kcfjz0cje5qftvh99 probably, but the bulk of the work is in accumulating the info in the first place. That's why you need apps like Mozilla Stumbler.

First spec for storage of digital data in DNA

in case you'd forgotten that you're already living in a sci-fi world... https://www.snia.org/news_events/newsroom/dna-data-storage-alliance-releases-its-first-specifications

Bitcoin sucks, literally. Sucks electricity, among other things... https://mastodon.social/@fj/112009495941530784

nostr:npub1y0emt2wlpsezcnmxtyrpf33qe7gwy5u8yzssvv6uw53em0k32t7q7smm9n wait, what happens if you reach your max size and your application tries to write more? Or is this a “the application needs to handle this appropriately” scenario?

nostr:npub1hcesfc0fhhhl3hwqlngqaur76kvwk8qdfyakjxwzpstwk2dp2u9szsc5cz there's a resize function. But if you're using it, You've Done Something Wrong.

Digging up an older vid, from 2022-12-08 : mining Monero on my new (at the time) Android car radio

https://files.mastodon.social/media_attachments/files/111/811/786/465/788/595/original/85cb95799a36247d.mp4

We've relied on this property in the past, to prove to an installation that the database corruption they were experiencing wasn't an LMDB bug - it turned out to be a faulty DRAM DIMM in their server. Without LMDB's deterministic write behavior, convincing someone of these cases would be a lot more difficult.

But proving the presence of a bug and narrowing down its cause are really two different tasks, and thus requires two different types of logging.

There's an art to debugging with print statements. You need to show enough to be able to identify problems happening, without being so verbose as to overwhelm with useless noise. When #LMDB is built with debug logging enabled, the output can be too voluminous to sift thru.

But it shows exactly what the code is doing, in such a way that you can parse the log and rerun the exact same operations, and get an identical database as a result.

Timelines and following hashtags is still a stupid way to interact with people. The Usenet model of topics is still the better model. You can't build meaningful thoughts from a firehose of non-sequiturs.

nostr:npub1y0emt2wlpsezcnmxtyrpf33qe7gwy5u8yzssvv6uw53em0k32t7q7smm9n When you reach the top, you can only stagnate or move backward ;-)

nostr:npub1a56srf6x5rhfl3kxxfah89ky7rav04894juzyta5zpqfgfevhgaqypjgz2 true, anything we refactor in there now is likely to have no effect or negative effect.