mooreed

## Heatache

In a real way, this article shows how 6th grade life is into the "6 degrees of separation from seeing evil"

In light of these hopefully overblown and hyperbolic headlines I am crushed for parents who lack the skills or knowhow to protect their young minds; I so hope that the article is hyperbole, but if the article contains a modicum of truth, I feel like I have a burden to help advocate for sensible parental advice to other parents.

## Call to Action

After getting the list started, it seems like there are two categorical solutions: technical + non-technical strategies. I would love your help to compile these things so I can tell them to anyone who will listen.

### Technical

1. I have a the home router set to turn off the internet to the kids at night

2. Use DNS Filtering (eg: `openDNS`) on the home WiFi

3. Copy the DNS settings to the child's device

4. Require Access to your children's social accounts and spot check it a few times so as to seem like there might be a check at any time.

5. Use Parental Controls when sensible

### Non Technical

1. Be very upfront (but age appropriate) with your kids

2. Proactive communication about sexual education

3: Delay access to a phone as long as is reasonable

## What Else?

I now put it out to the community - What are other effective strategies/methods you have used?

@hristov I am incredibly moved by your wonderfully thoughtful reply; we are just getting up to speed so had not heard about this at all. From the bottom of my heart, thanks for sending this.

Merry Christmas!

@HorizonXP first thank you for your willingness to answer questions.

1) Any idea on where to look to find out when this might become available? Looks like it was just cleared by FDA with 510(k) clearance.

2) My guess is that if you want this done - you would have to travel to UCLA? and Dr. Raman (or colleague) would perform the operation?

3) Is there anywhere to find a real discussion of down side risks with actual rates and figures?

For example, the RSNA article has a statement:

>"There were low rates of severe toxicity and no bowel complications."

4a) What does `severe toxicity` entail? 4b) Is that a operational complication that is remedied at the hospital and overcome in the short-term? or is that a long term quality of life issue?

5a) Furthermore what is this actual "low" rate? is it 2/115 or is more like 10/115? It looks like the base rate for these is perhaps around 3%-7% is how would I compare this study of 115 to something published like: [1]

Similarly RSNA states:

> "We saw very good results in the patients, with a dramatic reduction of over 90 percent in prostate volume and low rates of impotence with almost no incontinence" --Dr. Raman said.

5b) Where could I look to find the actual rates of each of these negative side effects? 5c) Or would you guess they are not published?

[1]: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2900775/

As someone whose family member recently just received a test showing elevated PSA levels (Prostate Cancer indicator); this article is a very real blessing.

# Baseline issues with prostate cancer that suck.

1. Don't treat a benign version and possibly live with trouble urinating and follow on problems from that.

2. Don't treat a malignant version and die

3. Treat it and potentially be impotent

4. Treat it and end up with bowel dysfunction

5. Treat it and rehab through surgical scars looking like an upside down T from following from belly-button to waistline or a U shape around the rectum.

6. Of course there is some tail risk of much much worse situations; and while it's worth remembering, it's not worth enumerating.

# TULSA method

So while this method is not different - it includes things that suck... if you read further upstream of the newatlas article to RSNA primary source [1] you will find that not only do they insert a spinning ultrasound device up the urethra - but it also includes a simultaneous insertion of an endorectal cooling device(ECD)[2]. Given all that: the parts that suck about this method pale in comparison to the traditional list of 6 above.

# Conclusion

There is much to be squeamish about with this method, as with any prostate remediation methodology; but if applied under careful care of patient and doctor - this looks like a very promising prostate treatment. And as a family friend once put it to me: "Welcome to the world of cancers; where pretty much everything sucks."

[1]: https://press.rsna.org/timssnet/media/pressreleases/14_pr_ta...

[2]: https://press.rsna.org/pressrelease/2019_resources/2129/fig_...

(edited for formatting)

You could stick with the `head` pun with "Headful" etc...

or to go with a different spin and a double pun.

In the world of contracts it is often asked if some language "has teeth" As in, "will be bite them if they misbehave", or "will it bite us if we misbehave". Often this is even discussed the contract has been "givien fangs" if it will bite hard.

So in a world where large corporations would like to co-opt my broser to not be my browser. You could call it "fangless" has in you have removed the teeth that can bite me from my own browser, as in this browser can bite you, or if it tries nothing will happen. Also plays nicely on the capital markets acronym term of FANG who are the largest purveyor of sites that try to use my browser to bite me.

Or perhaps you could smush them together for a `reheaded (as in opposite of be-headed) fangless` browser.

TLDR; If you share the many dirty secrets of your employer, and then write a tell-all book about them. Your employer will sue you for breach of NDA.

This is especially true if your employer is The USA(NSA/CIA) and your last name is Snowden.

The briefing is largely about how the US wants to stop Snowden from collecting proceeds from the book, and how he has violated his NDA by not letting them preview a pre-published draft.

Fair points. Good feedback. I was clearly “feeling grand” upon first reading it.

I am not sure I fully understand your question. Perhaps restate some of your goals more concretely?

Or link to a longer form post?

For me, I can’t tell if you are looking for some architectural patterns you hope apple will adopt?

Or for a discussion about DuckDuckGo, DNS over https, and VPN usage, Firefox focus, etc?

I wished I had followed Joe's career closer while he was alive.

I first encountered Joe in this video - a wonderfully funny account of modern computing (from 2014)

https://www.youtube.com/watch?v=lKXe3HUG2l4

Similar reading from WaPo: https://www.huffingtonpost.ca/2014/08/28/deadmau5-purrari-ce...

TLDR; Ferrari != John Deere - sounds like registered trademark violations at play - more so than just the paint job.

Seems like when you buy an exotic car its good practice to not name it something that rhymes with the manufacture's name. The "Purrari" also has custom badges that remix the Ferrari logo into the Nyan Cat theme. Which IMO might be the straw that broke the camel's back - and got Ferrari's attention not to mention the media spectacle it creates.

I want to really love this post. But I am not smart enough to know why it’s awesome. Anyone care to give a digest for mere mortals?

Nice examples and readme. But the question I keep asking myself is why add 4k to a bundle, or spend extra time leaning this package - when it seems like it is replicating a very common “map filter reduce” pattern.

Overall nice package, I just could not help but wonder that perhaps I am not your intended audience, given I think the better use of time is to learn the built-in js “map filter reduce”

To summarize, can you give a motivating example of when and why would would reach for THIS tool in the readme?

I would loved to have seen a list of other clients considered and discarded before the conclusion arrived at `DBeaver`.

I am curious how your criteria graded `pgAdmin`, `Postico`, `DataGrip`, or `PSequel` - for example.

Every article online for `10 Best Postgres GUIs` feels like it's a BuzzFeed article written for entertainment. I think Prabhat would be well suited to give an update on what else was considered in the `bake-off`.

...the moment when you realize you are depressed about the ubiquity of phone addictions whilst on your phone.

TLDR: is that humans have a "storied" history of using pictures to communicate. So much so that even space probes have been sent with diagrams of our solar system in lieu of text.

The site has nice interactivity with the map and the associated historic image from the some point in time.

For me the whole post was worth it just to find this little gem of a book tucked away at the end `Ost Trifft West` by Yang Liu [1]. It is a visual representation of cultural differences which I found both wonderfully light hearted and highly informative.

[1]: ISBN-13: 978-3874397339

Chromium Ungoogled repo [1] made it to the `top30` some days ago. I too have switched back to Firefox with the release of Quantum and have been very pleased.

Frankly, I am amazed every day that Ungoogled Chromium, Firefox, & DDG.co are as good as they are. (aka: slightly inferior to Google regarding product polish, but truly "good enough" 98% of the time - without selling my future data down the drain)

(edited: to fix typos)

- [1]: https://github.com/Eloston/ungoogled-chromium

1) Read the image captions - they made my day. 2) Pick Postgres unless you have a compelling reason not to. 2b) Use the time gained by not over-engineering upfront, to focus on users and business logic. 3) Optimize/Evolve away from Postgres later as needed. 4) Profit.

If we can agree that the problem defines the solution, then you will have to work backwards to a problem that your team has unique competency at.

Restated, it is impossible to have a great team without the constraints of a problem statement. It is similar to those who claim C++ is the best language. With out the context of the problem to be solved, it is merely an opinion.

Really depends on your objective measure of "better".

Faster load time? Better uptime? Less data leakage to Facebook? Etc.

This practice of defining "better" is a great habbit to cultivate not only in your conversation but in your thinking too.