Searched hn.algolia.com to see if this had been posted yet, and was presented with a confusing of dropdown of non-TWP conformant “date ranges”- hope they can fix that soon.
I was using DreamWeaver in maybe 2006-2007. I hadn’t thought about it in a long while. Back then we were CRUD web apps with a FileMaker backend and there was an integration where you could drag database fields straight out of FMP7 into DreamWeaver and it would automatically create the correct PHP (also 6 or 7 back then) code for your form.
I coded up a simple CRUD in Streamlit yesterday (needed a simple way for my Field guys to create professional looking PDF trip reports) but it still took me longer than that workflow used to. Our tooling really seems far behind where it ought to be. The whole time I was writing it, I was thinking why did I stop using PHP for stuff like this?
Tools like FileMaker, Dreamweaver and others empowered regular people to do "personal computing" and allowed them to help themselves build the tools they needed.
It seems to me like that was a golden age of genuine personal computing that went by too fast and with many avenues left unexplored.
Our 2.5 yo daughter was IVF- we were told there was “totaltubal blockage” and “next logical step [was] IVF”
after frozen transfer, genetic testing, injections, implementation etc, we were certainly close to that $50k (US.SoCal). roll in $3k to cover for a sad outcome we’d barely have noticed—
I think Id do it just to amortize the cost for other couples.
My son is due (“unexpectedly”) in March… which has me checking my copious notes and reassessing understanding of “total”
I was in Cape Cod for a wedding late last year with some friends, and came across what we later learned was a Yew. Some of us had popped into an ice cream shop, and one of the members of my party apparently decided to eat a sweet berry while they waited.
When we came out, we were initially incredulous but they clarified that the flesh of the berry was sweet, but the seed was disgustingly bitter. Which prompted the rest of us to quickly do some research on what this plant was. The mood was initially somewhat light-hearted, however articles with titles like “Why is the Yew Berry sometimes called the Death Berry?” had us on the phone with poison control pretty quickly.
Poison control was very professional, and once they confirmed that it was indeed a Yew Berry that had been ingested, things got pretty serious. Apparently even small doses can quickly cause irreversible heart failure, with death the earliest “symptom” in some cases.
My friend didn’t die— just experienced some terror and gastric distress— the latter likely exacerbated by the terror). No drugs or alcohol or involved, just an impulsive decision, and a sobering reminder about the fragility of life.
One of the other replies in this thread mentions mushrooms. Which reminds of the aphorism: _There are old mushroom foragers, and bold mushroom foragers, but there are no old AND bold mushroom foragers._
Oh wow that was a journey. As soon as I saw "yew" I started internally screaming.
The route that my kids walk to school took us underneath a large yew tree, and the road underneath is often covered in hundreds of delicious-looking pink berries. Since they were tiny they have had to know all about how yew berries look lovely but even one can kill you. What I didn't ever tell them is how apparently the flesh is actually not toxic and is tasty, and it's the seed that will kill you.
The aril (the red flesh of the “berry” surrounding the seed) is tasty, and not toxic. But the leaves, stems, roots, and seeds are poisonous. Our elementary school has evergreen yew bushes growing around it and I taught my children not to eat the seeds. A fellow parent advised use not to eat them because other children might not be so careful.
Are yew rare where you are? Here in Ireland (and also in Britain), they're traditionally found in churchyards (where grazing livestock cannot get at them) and are well known to be poisonous. (Agatha Christie used yew as a poison in one of her novels.)
I read this and thought; I sure hope so if I’ve made it this far in life not knowing. I believe someone’s rectangle plant-identified this particular one as European Yew (Taxus baccata). None of us had encountered it before and this particular plants arils (thanks drjason) were quite strikingly pink.
Apparently, there are others in North America, but mostly not in the Southwest. I lived in the Pacific Northwest about a decade ago which also has a yew (Taxus brevifolia) but I don’t recall if I ever saw the berries.
That said, most folks I know were raised with a baseline of “don’t eat random berries you don’t recognize.”
They're common in landscaping throughout the US. We had some in our front yard, but us kids knew better than to eat random berries. It's painful for me to think that there are people out there without the common sense not to eat random plants they don't recognize.
Folks visiting the desert and distractedly running straight into octillos is just good entertainment. There's not much on the east coast that prepares you for a random shrub to be so hostile. Poisonous berries though, they're everywhere. I'm surprised your fellows made it to adulthood without basic suburban survival skills.
Except for grass and most trees, suburban foliage is often quite toxic. A lot of your ornamental plants are poisonous. Think lilies, foxglove, Solomon's seal, and all the excitement of morning glories. The basic understanding that you don't eat anything you can't identify as edible is important in the suburbs too.
I don't disagree, but I'd say there's not really a big problem with people or kids trying to eat flowers. Foxglove and solomon's seal are dangerous but they also don't grow where I'm at. Lilies and morning glory do grow here, and they are also not terribly dangerous to humans (without eating a lot of them.)
Where I'm at, particularly in the suburbs, there's a distinct lack of things that are tempting to eat (like a berry) and also poisonous.
The berries (but not the seeds!) are apparently edible, and I have myself eaten one without noticing any ill effect. IIRC it was indeed the berries that were used in the Agatha Christie novel, so apparently a mistake.
This is an example that mushrooms unfairly get a bad rap - there are much nastier things in the plant kingdom. Some of them you don't even have to eat to get seriously hurt by, and they're not even that rare (e.g. giant hogweed)
I'd add hemlock in there in too. Both are plants you'll see in parks in town. A toddler died here a few years ago because his parent allowed him to play in the big plants with the pretty white flowers. They don't look dangerous and don't have to be eaten to be deadly. Breathing too much pollen is enough, especially for a child.
I'm pretty confident with berries as I've got plenty of experience, but I don't mess with wild carrot or even elderberry as I don't feel I have the knowledge at this point to make it worth the risk. There are just too many lookalikes.
Both TFA and your comment raise valid concerns. That said, some points in both seem to conflate Bitcoin with traditional monetary systems in ways that don’t quite hold for me.
TFA: Bitcoin and Quantum Risk
> Global Infrastructure can be upgraded, Bitcoin cannot.
Bitcoin has already undergone significant upgrades (SegWit, Taproot, Lightning Network). Transitioning to quantum-resistant cryptography would be complex but not impossible, which TFA acknowledges, as well as the difficulties presented by the decentralized consensus model. That said, the same quantum threat applies to existing financial infrastructure, including banking, government systems, and encrypted communications. These systems will likely upgrade, and if Bitcoin remains valuable, it seems likely to adapt as well.
> An estimated 24 million BTC—25% of all Bitcoin—resides in vulnerable wallets.
This is a legitimate concern, but the assumption that quantum attacks would instantly drain these funds without any network-wide response overlooks how Bitcoin has handled security risks in the past. Solutions like soft forks, address migrations, or layer-2 mitigations could play a role if such a threat became imminent/apparent.
WRT your comments on inflation and investment
> The normal level of inflation […] is just a consequence of the fundamental fact that certain amounts of money in the future is worth less than the same amount of money today.
This seems to assume inflation is inherent, rather than a result of policy choices. Historically, we’ve seen long periods of monetary stability under commodity-backed systems. Bitcoin, being supply-capped, follows a different model—whether that’s good or bad depends on whether you believe inflation is necessary for economic growth.
> Currencies that have a fixed cap are fundamentally bad for investments.
Debt-driven growth models rely on flexible money supply, but investment doesn’t necessarily require inflation. Gold-backed systems supported lending through alternative mechanisms like equity-based financing. If Bitcoin were to play a major role in finance, it might push economies toward similar non-debt-based structures.
As for your point on Bitcoin’s Long-Term Viability
> If it can’t attract a significant number of new people willing to stuff their money into the Bitcoin machine, Bitcoin essentially loses all of its value.
Is this not true for any asset? Gold, for example, isn’t required for transactions— it retains value because people want to hold it. Bitcoin’s “value” is similarly also tied to its properties—decentralization, censorship resistance, fixed supply. Its future depends on whether people continue to find those properties useful, not solely on its ability to attract new entrants.
Concerns around quantum security, Bitcoin’s governance, and its long-term sustainability are real, but dismissing it as “just a gamble” overlooks its existing use cases. A more interesting discussion might be: What would it take for Bitcoin to adapt?
Given its history, outright failure seems less likely than some form of evolution.
Worked for them in various capacities for 6 years. It’s still what’s mostly in my house and mostly what I recommend for lighting control on projects. I’ll admit I have been eying Casambi with some interest.
and we’re all better off for it, including PG&E, who doesn’t have to transmission lines over more (un)maintained wilderness, which is where many of the fires come from in the first place.
Same here. When you say your own email, do you mean Fastmail? I love Proton and they got me and my SO largely off of Google. Fastmail is just so good, I’m going to migrate everything there eventually.
I migrated from gmail to proton then to fastmail and I can now really appreciate how much more polished gmail was.
My biggest pain is fastmail's ios app, e.g. clicking on an email notification will in 50% of cases result in fastmail's app to open in an unresponsive state where I have to forcefully quit the app and start again. It's been like that for close to two years now.
I think most business people dont care about clients at all because they use IMAP/SMTP/carddav/caldav.
Once you have more than one mailbox then its kinda the only way. So apple mail, thunderbird etc. And then you mostly get some quality provider mailbox.org, fastmail, infomaniak or whatever but its all the same.
> When you say your own email, do you mean Fastmail?
Not sure what they mean, but at the very least I think you should have your own domain. So that you can migrate without changing the email address (and having to ask all your contacts to update to the new one).
Takes me back over a decade ago, working for a manufacturer that used a “Wi-Fi setup network” on many of their products, I started encountering early versions of “WIPS” (wireless intrusion prevention systems) that would leverage these deauth techniques in TIFA to prevent connection to rogue (read: our) Wi-Fi networks.
That might sound fine at first glance, so here’s a common scenario we’d have:
During a renovation on a high-rise building BigCorp that still occupies office space on that floor, is happily (unknowingly/uncaringly) spamming deauths and even spoofing our BSSID and to our field techs it would generally just look like “incorrect password”
I wrote a long internal bulletin about it, mostly geared towards helping our techs identifying the issue (with varying levels of networking knowledge) and getting to someone in IT to help.
This is the easy wire shark proof if you suspect it:
#filter for deauthentication frames
`(wlan.fc.type == 0)&&(wlan.fc.type_subtype == 0x0c)`
Especially looking for a reason code of 2
`Previous authentication no longer valid.`
