mike_red5hift

IDK, I feel like creating music and causing music to be created are not the same thing.

When you know what to look for, a questing tick is not too hard to spot.

If you are in an area that you suspect might have a lot of ticks. Look at the tips of any grass stems for a little brown/black spot. They climb as high as they can and then kinda "stand up" and put their "arms" up and out and wait for something to touch them. Then it's off to the races to climb as high as they can... on you. They stop once they hit an obstacle they can't easily get around and dig in.

I spray my shoes with permethrin. That seems to almost totally eliminate climbers as I'm not walking through tall grass. You know they've gotten a deadly dose when they start walking in circles. I don't feel bad for them. My doctor told me that 85% of ticks in my area are positive for Lyme.

Article mentions QAnon. I thought that would go away after "Q" stopped posting. An uptick in believers is really surprising.

What are the core beliefs of QAnon these days?

The bit about Alameda being the only account allowed to run a negative balance is in the book. There's a whole section on it. It's kind of waved away, though, as being needed for market-making in the early days when volume was thin. But, of course that was never "fixed."

The book really seems to go out of its way to paint the collapse as a bunch of super smart kids getting in way over their heads rather than fraud.

Meaning, it harps on there being "no adults in the room", how SBF played video games while talking to people and never seemed to be paying attention, how the guy in charge of figuring out what happened to the money after the collapse came off like an amateur archeologist getting everything wrong based on the accounting artifacts because he lacked the imagination to understand the ridiculous way things "really" went down. The list goes on.

I guess it's funny in retrospect. I sell my own software and have to deal with these "confidently incorrect" people all too often. Seems like they are either mentally ill or have some kind of sociopathic personality. I'm thinking about quitting the game because of it.

I guess the "smart" thing to do would be to pay someone to deal with these people, but I really don't want to subject anyone else to the abuse. Not to mention that having another person on the payroll shifts the calculus of whether or not it is even worth it.

I thought I'd get used to it. But, after 10 years, it still makes my fight or flight response kick in. Every time.

At least I get paid to take the abuse. I can't imagine having to deal with it for an open source project. I guess it explains why so many open source project maintainers seem so testy.

Thanks for letting me air my grievances. I feel a little better :)

Not even a Nightwish fan and just that little snippet of the song gave me chills. Like immediately. Maybe I'm a fan now? Thanks for that.

I have an oddly personal question with a bit of oversharing thrown in for good measure :-) What make/model of Bidet? Been looking to install one. I've been thinking of one that heats the water, like I used in Japan. But maybe that's not needed.

Might want to look at Somnium Guitars for a more refined (not DIY) version of this. They have a really nice system. Not cheap, but the build quality is excellent.

Thanks! Now I'm never leaving the house again.

No I didn't. I'll check it out. Thanks!

Do have any pointers to javascript libraries that work this way? All the libs I've looked at (not recently) require the server to keep a running log of updates for the life of the document.

For example, the automerge library linked elsewhere on this thread requires it.

My understanding (flawed) is that you need to keep all the changes on the server because you never know how long it's been since a client has pulled/pushed changes to a document.

I guess arbitrary limits based on number of updates or time can be imposed, but I haven't seen libraries that do that.

Thanks.

Stuff like diffing multiple json documents and merging adds, updates and deletes where conflicts did not exist and overwriting conflicting attributes based on timestamps (latest wins). There's some reasonably good jsonpatch libraries out there that will do the heavy lifting.

Plenty of room for problems to arise, but it did not require keeping a log of updates. My use cases did not require real-time collaboration and the structure of the document was known beforehand, though.

Does anyone take issue with the fact that CRDTs seem to require keeping a history of every change ever made to the document?

Seems like it could get unwieldy very fast. Especially, in the face of a bad actor spamming a document with updates.

I've considered using CRDTs in a few projects now, but the requirement to keep a running log of updates forever has ruled them out. I've ended up using other less sound (more prone to failure), but more practical methods of doing sync.

Perhaps, I'm missing something. Wouldn't be the first time.

Are there alternatives without this requirement, or that would at least allow a cap on the update log?

RE: #2. I remember the first time I heard that sound when I moved from the city to the woods of NH. I thought someone was trying to crank up some kind of motor, too. Then I eventually caught a glimpse of a ruffed grouse doing its thing. Neat.