kc0bfv

Maybe on Stable. Sometimes. Not so much on Testing.

I came here via ttRSS, with the Android app. I host it via the hosting service I've used for years, it only requires PHP and a Cron job. The Android app lets me keep ttRSS and its authentication behind a separate HTTP basic auth, which I think keeps the attack surface low and security high-ish.

I think it's fantastic.

This is a graph entry tool I built, which sought to make it easy to enter, link, and display many pieces of data.

One design goal was to make the tool easy to use and share even on fairly restricted corporate networks. A save file contains the data and a copy of the tool, and is simply an HTML file with JS and CSS bundled. No external resources, so it's easy to trust with sensitive data, and easy to move onto even an "air-gapped" development network.

Are you talking about Seasonal Affective Disorder (SAD) lamps? I think most "full spectrum" bulbs will work, they sell them at hardware stores.

Some communication is possible...

https://en.m.wikipedia.org/wiki/Communication_with_submarine...

The VLF section above that one is also relevant.

The hero we need.

This is beautiful and easy to use. Very intuitive.

I definitely assumed this would contain clever tips about how to handle it when coworkers don't respond to your emails, don't accomplish things they promised, or don't follow-through. Maybe some automation methods to handle those situations.

I agree. Perhaps the old user agent sniffing, from that recent age when Edge was NOT Chromium, is still mostly in place. This seems like the more likely reason to me.

I loved wicd, and had had problems with nm.

Then I had a problem with wicd - interface issues caused by the deprecation of ifconfig in favor of "ip" tools (Debian). Wicd is a set of Python scripts that call ifconfig.

So I submitted a patch to fix my issue, and tied it to the multiple bug requests already reporting the issue...

Wicd hasn't been updated in years though. With ifconfig starting to break (at least in some situations) it's going to need some updates soon.

I switched back to nm and found it's working extremely well these days.

Planet Money is a fantastic podcast that covers a huge variety of interesting topics, and only takes about 20 minutes. I highly recommend it as one of the most informative fun podcasts I've ever heard.

But here goes...

Fries don't stay delicious very long. You get a couple minutes then they're blech. They don't work great out of drive-throughs, where you might take them home before eating, and now we have food delivery services where fries might sit 40 minutes before being eaten! Double blech.

This company made a coating for fries that makes them stay fresh for drive through service. That is old news. If you've had fries from fast food you've probably had these coated fries. People like them and don't know they're coated.

But that just covers a couple minutes... Could that company make a coating that keeps fries good for 40 minutes?

Awesome lady scientist says yes! Other people say no. Awesome lady scientist says, let's do it anyway!

They succeed. NPR Journalist does the Pepsi challenge on them - the fries are good. They're in the process of selling them to companies now.

Watch out, those have been known to explode. I think this was posted here maybe a month ago: https://onezero.medium.com/unraveling-the-secret-supply-chai...

If the passwords are stored somewhere that's easier to access than your real target at the bank, then cracking the passwords might be helpful... I totally agree with your recommendations, but bank password storage/complexity definitely could be important.

If an attacker got hold of a large number of bank account user logins, I'm not sure what they'd do. My bank doesn't provide a feature to quickly transfer cash from the website... Several hundred large billpay changes would show up and be easy to cancel... Perhaps they'd just gather personal info useful to a social engineering attack...

My understanding is that asserts are for debugging, and exceptions/more robust error handling are for production.

Asserts make the code blow up, which can make a problem easier to spot in dev/testing. In production it seems better to throw an exception, even if the program can't handle it well and just has to quit nicely.

I like your defensive programming strategy - see if the tires are flat before you get out on the highway.

Several people have said that these apps are crashing at an assert. How did asserts make it into production code? Is it just a C thing to make them debug-only?

Yeah, I like:

    z=dict(x)
    z.update(y)

It's clear and concise, and it's obvious which one gets precedence, even if it's two lines.

The benefits that natural selection causes to propagate are those which improve the organism's reproductive opportunities. Those "benefits" aren't necessarily all that great when you've got a civilization. To take it to a ridiculous extreme, if a gene exists which makes you kill all the other men in your village, then impregnate all the women, that gene will be pretty popular in the next generation.

Oh, for the women there's a .25 prob that a is used, and a .25 prob that b is used, and a .5 prob that c is used. Dad's X has the best chance, and his X may have made him a better partner than his peers. Also, a .25 prob for the X that made Mom a better partner. So, a .75 prob overall of getting a great X and a .25 prob of getting an unknown X.

For the dude there's a .5 prob of getting a great X and a .5 prob of getting an unknown X.

Hrm, if you're a girl, you get 1 X from Mom and 1 from Dad. So, if Mom's X's are chromosomes a and b, and Dad's is chromosome c, then your X chromosomes will be a,c or b,c with a .5 prob for each. With your suggestion, there's a .5 prob in each case that Dad's X will be used, and so a .5 prob overall that, for a girl, Dad's X will be used.

A guy has to use Mom's X. I think the paper's argument still holds, because there's a larger amount of possibilities for women than men, but I can't take this much further without circular reasoning.

Well, I guess my point was that there are a lot of physical goods that US companies may not sell to these countries due to sanctions - political reasons. Certainly folks circumvent these measures. People also circumvent regional restrictions on Internet services with VPNs. I'm sure this company doesn't want to smuggle its service in. I have no idea why the service isn't available in some specific area, but I suspect "not being recognized by the EU" isn't the primary reason. Though that may make implementation more difficult in an area.

My impression has been that companies have prevented each other from distributing to some of those rich and democratic small countries. Through region specific licensing of their media they've limited distribution. I don't think those are political measures, although certainly in other cases companies have used political means to achieve their goals.

Many in the US have lusted over NFC payments via cellphone, available in Japan.

I suspect citizens of Iran, North Korea, China and the old USSR would disagree with that last sentiment.

Ooh! And the US (Cuban cigars).

Right. They know that, even if they haven't done much about it. They want to be able to make their page slick, and a good user experience. This post documents their problems and provides a path forward.

Kudos Facebook.

Did anyone catch the, "download our rank code so you can run Google at home", link? I didn't realize this April Fools day until I saw that...

I agree. His post smacks of the same attitude that many people (negatively) attribute to engineers in general. The, "this is how I do it, so this is how everyone should be doing it," attitude.

I agree too. I think it was naive of anybody to think that this wouldn't eventually happen. For years people have said that Google's goal was to control the information - all of it. I suppose that never bothered me because I know that I control what information I give Google, and I don't feel that Google has tried to subvert that control yet.

I'm a little disappointed that Google is returning Goog+ results above other social networks when the + results clearly are not as relevant, but hopefully they'll iron that out over time.