Otherwise it just reads like “lots of people are mad”. Well about what exactly?
It’s fine for a headline, but not very impressive reporting.
1,074 karma · joined September 3, 2011
domain: endoftheworl.de
Say hi to mkirk at the above.
Otherwise it just reads like “lots of people are mad”. Well about what exactly?
It’s fine for a headline, but not very impressive reporting.
Another pet peeve of mine is omitting the time frame for wage increases. A 25% raise today is not the same thing as a 25% raise over the course of 4 years.
The kilometer: As part of the widespread rationalization that occurred during the French revolution, the meter was defined in 1791 as 1 ten millionth the distance of a line drawn from the equator to the north pole, through Paris.
Golden ratio: 1.618... km / mile ratio: 1.609...
So, seems like just a coincidence.
But these are fun:
https://en.wikipedia.org/wiki/Mile https://en.wikipedia.org/wiki/Kilometre
So I read it as “Given we’re trying to have an alternative to IE, it’s silly for us to further fracture the ecosystem, rather than collaborate on a viable contender.”
Wikipedia shows november 2005 browser share as 88% IE, firefox at 8%, and netscape+other at 2%. (not sure why this doesn’t add up to 100%)
Anything in it you want to highlight?
https://www.epa.gov/sdwa/and-polyfluoroalkyl-substances-pfas
> The agency’s new advisory levels aren’t requirements that drinking water suppliers must meet. The EPA only recommends that utilities notify customers when concentrations exceed the limit.
> But they set the stage for further EPA action. The agency plans to propose mandatory drinking water limits for PFOA and PFOS later this year.
So here we are, in April 2024 with some actual rules and timelines: https://www.epa.gov/sdwa/and-polyfluoroalkyl-substances-pfas
If you want to make the time to take photos and take notes, and sit down later and enter them on your computer, go for it. Likely that's a faster way to do a larger entry. In particular, I haven't seen a mobile app that does a great job of polygon geometry editing — a mouse really helps.
But I don't think it's a problem to do simple POI entry or attribute updates from a simpler mobile app like "Go Mapp!!". I think like many things, the best mapping tool is "the one that you have with you".
Am I missing something?
Often times, when I do work with them to get their changes merged, I’m tempted to make similar changes myself, rather than workshop pull requests for days and weeks. Not because I think the changes are even worthwhile to incorporate, but because it’s less painful than the back and forth to get their changes up to snuff - but “stealing their idea” is socially awkward for its own reasons.
There’s also sometimes a bias towards merging unless you find a problem, so it can feel really antagonistic. Strangers on the internet become your task masters to an extent.
The common reactions I see to not wanting these kind of contributions are “You’re looking a gift horse in the mouth!” Or “It would go more smoothly if you spent more time unwillingly being a Manager for strangers on the internet” or “You’re gate keeping.” To an extent I suppose all these things are true. But, that doesn’t mean it’s the wrong decision. It can be frustrating to experience and difficult to explain if you haven’t been in the position.
Anyway, it’s nice to hear someone else articulate my experience. It makes me feel less crazy. So I wanted to partially return the favor and say also that you may not be crazy.
Then I use ogr2ogr to convert to whatever output format I need.
> This should block just the buggy kernel. Which might help with unattended upgrades problem or just being forgetful. It might even uninstall the buggy kernel, though I didn't test that. And it shouldn't impact upgrading to 6.1.66 when it's available.
> create a file: /etc/apt/preferences.d/buggy-kernel
> with the contents:
# avoid kernel with ext4 bug
# 1057843
Package: linux-image-\*
Pin: version 6.1.64-1
Pin-Priority: -1
> (the comment isn't required but is helpful for remembering why this file
is around in 6 months.)I work on some of the rust libraries you've used. If you'd like to ask questions about rust+geo or do a show & tell, consider joining us in the georust discord: https://discord.com/invite/Fp2aape
I'm also always interested to hear new people's experience building real things with our libraries. What were the hangups?
This guy called it boring when justifying its use for discourse back in 2013.
> Ruby isn't cool any more. Yeah, you heard me. It's not cool to write Ruby code any more. All the cool people moved on to slinging Scala and Node.js years ago. Our project isn't cool, it's just a bunch of boring old Ruby code.
https://opendatacommons.org/licenses/odbl/summary/
> Share-Alike: If you publicly use any adapted version of this database, or works produced from an adapted database, you must also offer that adapted database under the ODbL.
A mapping product like Google/Apple Maps includes a lot more functionality that often gets taken for granted.
For instance: - A geocoding search engine to find places by name, address, or description - navigational directions - tiling and other data distribution (which is both software and hardware) - styling and UI
There is a huge variety of open source options for this functionality, but it's hardly a plug and play thing, and quality varies wildly. Putting it all together is no small feat.
Disclaimer: I work on Headway (https://about.maps.earth) which is trying to make this kind of thing easier.
I posted here both to advertise the new feature for people who might interested in using it, but also in hopes of getting feedback on the approach from people who are familiar with the space.
https://www.verizon.com/about/news/verizon-google-messaging-...
https://arstechnica.com/gadgets/2021/06/google-enables-end-t...
But, to your point, I think pointing people to "next steps" is important, and guiding them to useful tools to solve their actual problems is part of that.
If you can share, in what capacity have you been using whitebox tools? Maybe it'd give me inspiration into a good thematic lesson on the tool.
If you enabled Registration Lock, your account cannot be hijacked by sms, provided you’ve been actively using your signal account within the last week.
There’s an automated keep-alive for the case that you still have signal installed but haven’t been sending/receiving any messages.
Though you still have to occasionally support arbitrarily large WAL files to an extent because there’s no limit to how big any one write transaction is.
Reading between the lines a bit, I suspect unbounded growth is still possible with WAL2 - If you have an infinitely long running read transaction, data that modifies the page that’s being read from can never be checkpointed into the main DB.
So setting aside the case of readers that never progress, with WAL1, even if your read transactions were finishing and fast forwarding through commits, it was possible to be in situations where, for a very long time (even potentially forever), at least one reader was behind the most recent write transaction, which meant the wal could never be truncated.
Now with this WAL2 mode I think it should be guaranteed that so long as your read transactions are eventually ending and progressing towards more recent commits, you’ll always eventually find a time to checkpoint and truncate your WAL2 files.
It’s solving a real problem, but not considered stable for production yet.
The most popular pure rust ones are based on somewhat esoteric patterns and seem prone to being abandoned.
Within that there are some interesting options, like for functionally reactive programming and immediate mode guis, but these paradigms aren’t all encompassing and in fact cover a pretty minority use case based on what GUIs are being created today.
Maybe one day we’ll all only ever create purely functional GUIs and speak Esperanto, but until then, we’re a little hamstrung in rust.
The article is called "write it in Garamond" - the premise of the article is that the chosen font directs the words to be written.
> creative output of any kind depends upon a steady stream of tiny self-delusions — guardrails to keep yourself from veering into a pit of self-doubt and despair
You're letting iA Writer choose this effect for you, which is also valid, but it doesn't "free" you from the effect (if you buy into the article).
And let's not forget sqlite!
> There can only be a single writer at a time to an SQLite database.
edit: If you delete your reply to this, I'll delete this. and we can unfuck this whole thing. ;)
Sorry if this is obvious, but "blown up beans" pretty much universally means "overcooked". They probably would have been good if you'd cooked them less.
However, "hard" beans are trickier. It might just mean "undercooked", and you can give them another few mins in the pressure cooker, or it might mean that the beans are old/were not stored in a dry air-tight container.
So how to pressure cook good beans:
Start here for rough times: https://fastcooking.ca/pressure_cookers/cooking_times_pressu...
Cover beans with about 2-3x water. The goal is that once the beans have expanded there is no excess water. The excess is just diluting your seasoning.
prepare seasoning (in this example for something good in a burrito, w/ corn bread, or served with a braised pork shoulder): brown a lot of onions in a lot of oil. For 2 cups of dry black/pinto beans, something like 1 large onion and 1/4c of neutral oil. Add 1/2 head of chopped garlic to the mess after the onions are browned. Add another drizzle of oil and into it add ground chili (preferably a smoky one like morita), cumin, and black pepper just as you are turning off the heat. The effect of cooking spices a moment in oil is positive (see indian "tadka").
Add salt and seasoning* in with the uncooked beans. My rule of thumb is that the cooking water should taste decidedly salty - a bit saltier than you ultimately want the beans to taste, since the salt will disperse somewhat into the volume of the beans.
*Some people say don't salt or season until the beans are cooked, else your beans will stay tough.
This is definitively not true in the case of salt - in fact the opposite, salt is shown to help denature the protein in beans and decrease cooking time: https://scholar.google.com/scholar?hl=en&as_sdt=0,48&q=salt+...
It seems to be somewhat true in the case of the calcium leached from seasoning like onions and garlic, but, IMO with the pressure cooker it's not an issue in practice.
Also cooking in an alkaline solution can help denature tough, improperly stored, beans. So if you're having a rough go of it, you could try adding a tsp of baking soda to the pot.
Happy beaning!
The traditional "WhatsApp Web" and "Signal desktop" are completely different experiences though.
Though the details differ, WhatsApp's new approach, outlined in this article, is much closer to what Signal has always been doing since it introduced Signal Desktop - which, once linked, functions independently of your phone.