devrandomguy

Is there any other type of solution?

If some service demands my mobile number, that is a clear signal that I should not give them my actual mobile number.

The reason I rejected PG's JSON store, was it's inability to update fields inside of a JSON doc, without replacing the whole document. In your case, does this constraint push you to use more types of smaller documents, or do you just read the whole doc, update it in the application, and then write it back to the DB?

Have you ever had an issue with conflicts, where multiple instances of the app read, modify and write different things to the same document at the same time?

That is a pretty loose definition of accountability. If your bank screws around, are you going fix it by voting for a different candidate in the next election? I would say that my ability to purchase and run mining hardware, at a loss if necessary, gives me more control over my altcoins than my citizenship gives me over my bank.

TL:DR QM programs can be represented by a Lisp DSL, like everything else in life. It's all brackets, all the way down /s

I visited that video specifically because the view counter was jammed at UINT_MAX. There were comments confirming that everyone was now visitor number 4,294,967,295. In fact, it might have been an HN post that brought it to my attention; I totally didn't get sidetracked on YT and end up watching K-pop all afternoon.

Have you never needed to merge datasets, that grew separately, in parallel? It is a royal pain when the rows have consecutive sequential primary IDs. Something has to make way for the other.

IMO, this is one thing Mongo got right: keys, by default, are a timestamp + some random string. This way, they still sort nicely, but don't collide with their cousins in a different instance of the DB.

(In David Attenboroughs voice): And here we have the gentle Sillysaurus in it's natural environment, grazing on a field of failweed in the tidal shallows. Notice however, that his eyes remain just above the surface of the water, ever vigilant for the dreaded Snarkasaurus Rex.

A flock of Correctosaurs glide by overhead, scanning the muck with uncanny vision for the telltale motion of their Suttlebug prey. It is their rare, mid-air collisions that give the Suttlebug away, despite their otherwise excellent camouflage.

I was about to make a note to go back to AMD CPUs for future builds, but then I found this: https://libreboot.org/faq.html#amd. Looks like we're basically screwed for CPUs this year, and the next, until one of these open source IP stacks finally gets a production run.

> It is extremely unlikely that any post-2013 AMD hardware will ever be supported in libreboot, due to severe security and freedom issues; so severe, that the libreboot project recommends avoiding all modern AMD hardware.

So, what to do... Acquire obscure military surplus gear, and attempt to port Linux?

I see the only modern recommendation from Libreboot is something called Rockchip, an ARM SoC. https://en.wikipedia.org/wiki/Rockchip_RK3288

Integrate with Facebook. Don't force people to choose one system or another. Then people will diffuse across the barrier.

Diversity, mainly. Grow many different classes of plants, not just food products. Start a nearby beehive and include plants with large numbers of tiny flowers. Include crayfish and other filter-feeders with the fish. Keep a few trees (cactuses?) around to provide bird habitat.

Basically, yeah, artificialness is a liability, and it should be minimized intelligently. Not by imitating a jungle, that is impossible, but by being highly aware of the local microbiomes and gently supporting beneficial negative feedback loops.

Make friends with a biologist.

As for the micro nutrients, this is what the fish and insect side of the system takes care of. If there is a deficiency, try to make it up through fish feed, not by directly feeding the plants. Fish hate concentrated fertilizers. Maintaining a barrel of "compost tea" is also an option, but it should be filtered through lots of grow media before the fish get it.

If you are really really brave, you might choose to experiment with a graywater system, but there is huge potential for problems like parasites and bacterial (i.e. E-coli) explosions.

I know a few hobby farmers who are big on aquaponics; one of them actually makes most of his profit by selling the live trout to stock lakes, from ~1 acre of land. Is there some reason that this is not taking off on an industrial scale? Sure, the traditional farmers won't pivot overnight, but why are there not legions of startups farming in the desert, eating the traditional industrial farmer's lunch?

Water is tightly conserved, the main loss is through plant respiration, but even that could be reduced in a greenhouse. Then the main water loss would be either the occasional emergency flushing, when a tank of fish get sick, or through exporting the product itself.

Nutrients are greatly simplified by the fish and insect side of the system. Many of the vegetable byproducts can be converted into feed pellets, or used to grow grubs as feed. Some input may still be needed, beyond atmospheric CO2, in the form of supplemental fish feed.

Automation in aquaponics is unheard of, but it should be much cheaper, because the plants are not embedded in soil. The presence of healthy, voracious predators (fish, frogs, geckos) reduces the insect-related problems. A tolerance for insects reduces fungus problems. There is little or no need to spray the crops.

Are we not scaling up because of a lack of research? Are there just too many unknowns for anyone to invest in the $100M range? Have there already been large scale failures where we were unable to analyze the root cause, due to the biological complexity of the system? This all looks so good on a small scale.

I suspect that it is also corporate propaganda, to reduce popular support for regulation, and to encourage the privatization of government services.

The React app that parses content from JSON to HTML (whyyyy?) also injects ~60 dynamic style elements (:facepalm:). Not sure whether to blame the Wix framework their app uses, or the site itself.

You would think that people who write comparisons of time-series analytics tools, and put effort into SEO, would profile and optimize their site. I hope Google buries them for their load time.

> ... there is a trend away from peer-to-peer towards client/server for multiplayer games ...

Really? Why? It seems obvious to me that communicating directly with other players would be faster than relaying messages through a server. Even if the server and the clients are all in the same building, the server is still going to add the latency of its entire stack. Unless that server is acting as a very simple stream-oriented traffic controller, then surely its latency is in the 5-20 millisecond range, at least?

I know WebRTC is complex, but minimal latency is such a critical feature for multiplayer gaming, that surely, if it works at all, then it is worth the trouble?

Yeah, this is all academic. What I am thinking of is basically a clean-room redesign of human civilization with little or no large vehicles, permanent structures or large population centers.

But, our bikes will need parts, and I am not willing to give up my laptop...

Dogs and chickens, I forgot about them, but with safe slow traffic, your dog can tag along. With a special purpose compartment on the bike trailer, you could bring ~4 chickens, and have a couple fresh eggs every morning, wherever you happen to be. Home is wherever you can inflate your bed; your party only moves forward, never returns.

Perhaps someone should specialize to handle sheep and goats. If you want deer or bison, then form a hunting party, and then trade 100s of kilos of sausages for your kid's first bike-trailer-home.

Let's also reduce the mass of the vehicle, to a fraction of its payload. Then, let's have the user supply the energy from their own food supply. These improvements will also improve health, safety and space/cost/energy efficiency.

https://imgur.com/gallery/DAijq#qcfLWFs

Plastic safety bumper plates around the front seems like a good idea for this build. It might save a dog's life.

A reputation system might help alleviate those concerns; it might even result in your tools being better maintained. I've never tried a car-share, but the general idea seems legit.

The primary motive for you to join, would be the opportunity to use the best specialized tool for every job, every time. If not even that would convince you, then you must have a truly awesome lab/workshop, and therefore you are out of our league, so to speak. Congratulations on your success, I hope to see your work on Youtube.

Ants walk. They live near their necessities, and they move the entire colony/city, as a single unit, when the local economy goes bad. They only own what they can carry: their larvae and their next meal. Their payload ratio is legendary, but within the range of a bicycle + trailer. When there is a big problem, they physically band together to solve it.

We have so much to learn from the ants, but 2 ton personal vehicles, four lane city roads and a 1-2 hour daily commute, are not a part of that picture.

In my experience, optimizing for perceived latency (time between user request sent and site becoming usable) inevitably leads to server side rendering, in geographically distributed availability zones. If you know this in advance, then you can choose to use tools that support code reuse across the client/server divide. This way, SSR is mostly a one time cost, and it can be implemented at the very beginning of the project, while everything is still nice and simple. It does impose additional constraints during UI development, but many of those are good practices anyway (proper use of HTML elements, prefer native form elements to fully custom inputs, use URL and history to manage state, etc).

It has been somewhat humbling to watch users on low speed connections use the app before the JS finishes loading; it shows everyone the true value (or lack thereof, for the passive content consumers who make up ~98% of the visitors) of the JS portion of the app, since they see it with and without JS. Sure, they can't drag a box on my fancy visualization, but they can see a snapshot of it, and use the peripheral controls as links to navigate to the desired application state. Then, as they are reading something that is useful to them, the ~2mb JS blob slips in and quietly brings the application to life.

Also, I love the way the 3rd party JS blobs that management mandated, are so obviously slower than the rest of the page. This gives me good ammunition for the arguments where I demand an HTTP API, not a JS blob, from our partners. They hate that, because then they can't stuff their own trackers into our clients. Fork 'em.

> The great majority of Jupiter's 69 known moons travel in retrograde orbits, meaning they travel in the direction opposite the planet's spin.

Sketchy! I don't suppose we have a prediction for the next anticipated lunar collision? Surely this system isn't stable.

If two moons in opposite orbits collide, then there would presumably be an even more spectacular event when the majority of the combined mass of those moonlets fall straight down into Jupiter. Imagine a ~1km ball of magma zipping past the Roche limit and punching a hole right through the Jovian atmosphere.

If you bring a glass of water with you, does it boil?

There was a problem in Edmonton ~10 years ago, where criminals would steal a car to get part way home in the winter. Then, they would convert it to a land missile, and launching it across a parking lot, into a mall, in the middle of the night.

Their solution was much simpler: secure the wheel using the seatbelts, jam a big snowball on the accelerator, and use a stick to nudge the transmission from neutral to drive.

"We're sorry, but you do not have access for this content"

/meh

If it's any consolation, the site is well tested in Noscript mode.

Is that really a thing? That must be such a hazard for their developers. I usually have a test for sites that I work on, that scrapes a few URLs as Googlebot, to verify that they are getting an optimized view (no JS, structural-only css).

If you change your browser's UserAgent string to Googlebot, then your client will be treated as a first-class citizen, by many of these sites. Google always wins, so let's all be Google.

The manuals have a big watermark right through the center of each page, which isn't even translucent; it completely obscures the content behind it. See https://www.manualslib.com/manual/464698/Honda-Civic.html?pa... for a random example, where the watermark completely obscures the model number of the Honda Civic's automatic transmission.

Is there some way to pay to remove the watermark? Is that how this works, these manuals are effectively just free previews?

If you hide a story, are the duplicates also hidden?

Opt in or opt out?