fmpwizard

We have been using http://twist.com for several months and it sounds very close to what you described. You create a thread with a title and a message and replies are threaded.

The bolt has over the air update capabilities, but iirc, it was used only once in the past 4 years. And the bolt has an option to limit charge to X%. I set mine to about 80%, and it's plenty for my needs. So you can leave your car plugged in all day long

That's an awful reason to block a PR. I've been doing code review for the past 6+ years and I'm on the other side, I often ask for better, and longer code comments, for the reason you highlighted, 5 years later (or even months later) that long comment will save us hours

the password length was part of the issue, but one where I need help with is them saying: "Widely accepted by cryptographers as a more secure solution than AES/Rijndael"

We have two kids (in NC, US)), both were c-sections, we had insurance on the first one, but because she was born in Feb, we had to pay the deductible twice, because even though it was the same pregnancy, it was "over two billing years". And even with insurance we still ended up paying the rest of the bill over 3 or 4 years. Second kid was with no insurance, I think we'll finish paying that one when he turns 10 years old. I don't know about other areas in the US, but around here you can at least setup a payment plan with the hospital and they are 0% interest rate.

I think the prev. comment is accurate in the sense that Mastodon can easily be vulnerable to social engineering attacks, because as long as humans run it, humans are going to make mistakes. To be super clear, any (chat/microblogging/etc) software is going to be vulnerable to social eng attacks.

Like many others, we were also forced to use it at work, hard to pick the worse part of Teams but a big one is how slow it is from the time I click the "reply" link until I can actually type a message. So many times I click, start typing and then I notice it missed about 4 to 5 letters, and I don't even consider myself fast at typing. Oh, and how you upload a file/image, need to wait until it is fully uploaded but after that you still need to click the "Send" button to actually post the file. It's definitely an enterprise kind of app, one that makes sure you take forever to do anything.

You can definitely have the best of both worlds. People will tell you (or me here) that it's rare, etc, and maybe it is, but all you need is one. Keeping balance is not something you do once and then you are done, it is similar to, you are not a recovered alcoholic, you are a recovering alcoholic, because any day you can fall back. You don't have to say, I can either have a happy personal life or make money, you can do both.

Like others have said, check with an accountant, I have worked remotely for the past 11 years in NC, for companies in GA, CT and NY, but because I'm 100% remote, I only have to pay NC taxes. None of them ever had an office in NC

I don't know their revenue numbers, but protonmail offers paid services, unlike Keybase. I hope protonmail doesn't go the same path.

Thanks, it looks like it is IP lookup, I used another phone (not mine) and they also showed my name there.

Somewhat off topic but, when I simply typed the site bill.com on Firefox's private browsing, scrolled down a bit, they show me a popup to chat and they have my first and last name there. The same thing happened when I went on my cell using Firefox Focus, which doesn't keep any cookies. 1. Anyone else seeing this? 2. I hate it 3. Where do they get this info from?

I didn't want to include the much longer list, if we look to more recent events, Google Play Music is in the process of being replaced by Youtube Music, but with way fewer features. I was also a Google Wallet user, and they killed it, Google Notebook, I'm sure I can keep going if I try to remember for a few more minutes.

Besides the privacy risks with full on moving your banking to Google, I think another big issue is when they decide this product isn't profitable any more, and/or some other department in Google comes up with banking 2.0 and you end up having to move all your bill payments, auto draft, etc back out. If we thought killing Google Reader was bad, killing your bank app would be even worse.

If we apply this to a human, let's say I'm getting old and my eyes aren't as good any more, I don't just keep driving like nothing changed, I need to find a way to see better, because the risk of getting into an accident is higher. If the car's system cannot tell what an object is, you don't just assume it's going to be ok, you need to either get better sensors or find some other real solution.

https://www.flowdock.com , besides all the normal features you mentioned, it has excellent thread support, which is huge! So you can have multiple conversations in the same channel/flow during several days and can just ignore whichever thread isn't for you. We have been using it with a 100% remote team for over 6 years.

I think your definition of a burner phone is different than what the article describes. It's not supposed to have much in the way of navigation/UI. To place a call it should be just unlock it, open it (for flip kind), press the numbers and then press the green button :)

I bought one for my 8 yod, unknown brand "Plum" and works great, battery lasts like a week.

In my case, I got it for emergencies.

I've been working remotely for about 13 years, something that I do with every new developer we hire, is to tell them that we are all available to answer their questions, no matter how "silly" they may think it is. I tell them not to worry about interrupting what we are doing, because if we are truly busy, we will not go into the chat app (flowdock in our case), but when we have a minute, we'll come to it and if the question is already there, we can answer it right away, instead of saying hi back and having no clue what the real question was.

And we are all very polite about it, we do say things like: "Hi, if you have a minute, how do I get this code working?"

And, we also have a "water cooler" room/flow, where we talk anything that isn't work related, weather, music, etc, and there sure, you can just say hi and nothing else.

In my case, it is not that I'm on a tight deadline, we make sure to have almost no tight deadline, my case is, I'm probably playing with my kids, or about to have breakfast with my wife, so if you need me, and post your question along with "hi", I can answer before I step away from the computer.

Hope this gives you an alternative view.

see self driving cars run into solid and stationary objects, but human drivers do that all the time too.

Human drivers who are distracted do that all the time, AP is supposed to avoid that, it is supposed to be alert all the time, but when it sees a stationary object, the result of their algo is, "it must be a sign we can somehow go through"

We need to make it very clear that self driving cars are better than driving drunk, or when you haven't slept in 24+ hours, but if you are a driver who pays attention, don't use this tech.

And it is not that I don't want the tech to take over the world, I wish I could just put my kids in a self driving car and have the car take them to the school that is 4 miles from home, but we are nowhere close to that, even with me in the driver seat, if I only have seconds to take over before I end up on a ditch or worse.

There is no reason to fire that employee. After such an event, they will likely be one of the most attentive employees in your company. Same way you don't fire an ops/dev employee after deleting a database. You look for solutions that will prevent it, like in the article, have training in place, run simulations, etc

If we look at humans as a counter, sure, apply all the stats you'd like, but I don't think we should do that when it comes to self driving cars. if we simplify the driving risks, we have: 1. driver kills him/herself 2. driver kills person outside his/her car

* Humans and computers can make mistakes on both.

But, my wife and I can teach our kid everything we have learned over the years, to prevent 1, and try to reduce 2. I consider ourselves better than average drivers, if I get my kid a self driving car that is not as good as us, I won't care that it drives better than my neighbor or someone in California.

And in a tragic scenario, it's one thing to say, my kid made a fatal mistake vs, some random QA didn't do a good job and now my family is minus 1

if the idea is to protect users so that you don't end up clicking on https://news.ycombinator.com.myhackerdomain.com , you then open the attack of a platform where they offer custom subdomains, and you have

https://original.blogger.com

and then

https://fake-original.blogger.com

if I make them look the same, and the address will hide the subdomain, it looks like a step backwards in securing the web

now, imagine the actual platform has a payment section, and I create a fake subdomain that looks pretty similar, email you, boom, I get your cc info because I tricked you into entering new cc info (assuming your scenario of someone being distracted)

About 6 years ago we adopted Scala for our server side language, and for the past 4 years we have been migrating old code that was CPU/memory hungry to go and getting very good results. All new code, if it's going to be cpu/memory intense, we write it in Go.

For non C/C++ developers, Go is much easier to work with and get performance benefits that before would only be possible by porting to C, or you end up not writing idiomatic Scala, which defeats the purpose of using Scala (imho)

generally is because they chose to use unsafe public access points

It sounds like you are penalizing users for not using a vpn or some other method when out of their homes. Yes, people can do that, but in 2018 having https on the sites you manage is a lot easier than asking every possible visitor to use a vpn. I hope you would reconsider and enable https on all the sites you are an admin.

If your ISP is MITMing you, I think you have bigger problems then whether they change the content of my static site when you visit it. If they were, they could potentially target your initial download of your browser and downgrade to http to infect your browser so that you never realize after that that https is faked out...

They could, and maybe in countries other than the US you have plenty of ISP choices, but in many places in the US, you are stuck with just one ISP.

And so far, we know that ISPs are manipulating http traffic but so far they haven't gone all the way to give you an infected browser. Again, it is possible, but I think that a better approach is if we all do as much as we can to help each other, the internet could be a better place.

why do they say it's anonymous? I use proton, it's encrypted but not anonymous. (unless you used the hash option someone else posted (I didn't know that was a feature)

I think the sad result of this story is that they are going to keep going with the self-driving car technology. During the investigation into the fatal crash accident they had, they showed how reckless they are. It would be great if they learned anything from the death of that person and rethink QA and decisions, but I doubt it. Time will tell.

npm doens't take the code directly from the github repo, so far it looks like the new code was publish directly to npm, so there is no git commit to look at as it never was part of the official github repository

A use case I run into often is with people I trust, so I don't fear they will take screenshots, etc, but I don't want to keep that data in the chat history. Most of the time I turn to protonmail using their expire option, now I can use keybase. Most of the time is when I need to pass a password to coworkers.

When sbt came out, Gradle wasn't as popular, the choices were either Maven or Ant at the time. If you are now starting with Scala, you have more choices.

I have been using Go for about 4 years at work and I would say they have been unlucky with the code they have looked at. You have the freedom to organize your code as you wish, you can easily go from one extreme to the other, one function per file to 1000 in one file. The only thing that isn't encouraged is to have very small packages, for example, if your project ends up split into 10 packages, but each of them is just one file (or one code file plus a test file), then most Go developers would suggest to group more files into a single package.