This is default featured slide 1 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 2 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 3 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 4 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 5 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

Saturday, September 24, 2022

New best story on Hacker News: Software I’m thankful for (2021)

Software I’m thankful for (2021)
745 by yarapavan | 473 comments on Hacker News.


Friday, September 23, 2022

New best story on Hacker News: Avoiding homework with code and getting caught

Avoiding homework with code and getting caught
673 by aabbccsmith | 147 comments on Hacker News.


New best story on Hacker News: Nightdrive

Nightdrive
686 by GeorgeHahn | 133 comments on Hacker News.


Thursday, September 22, 2022

New best story on Hacker News: Ask HN: Why is Microsoft Teams still so bad?

Ask HN: Why is Microsoft Teams still so bad?
649 by TurkishPoptart | 585 comments on Hacker News.
It's buggy, and it crashes more often than any other app I use. God forbid you try to change the audio device from speakers to headphones in the middle of a call. And then if you try to just call back on your phone, and they want to share their screen, and you go back to your PC and try to join the call from your PC so you can see the screenshare (it's not going to work). Seriously, with all the money and resources thrown at this company and this app, you'd think it'd be a little more stable, faster, and reliable. I am literally forced to use this app at work...

Wednesday, September 21, 2022

Tuesday, September 20, 2022

New best story on Hacker News: React I love you, but you're bringing me down

React I love you, but you're bringing me down
557 by fzaninotto | 436 comments on Hacker News.


New best story on Hacker News: Tell HN: Somebody implemented something I wrote a blog about

Tell HN: Somebody implemented something I wrote a blog about
552 by rexfuzzle | 152 comments on Hacker News.
So a while ago I wrote about how 2FA was missing a key feature: https://ift.tt/ChBLyI2... Having not had any feedback on it in a while and the idea not taking off, today somebody messaged me to say that had implemented it in their product. 1. Obviously I think this is great and more secure 2. Tell people about things you do that they played a part it- it might just make their day.

Monday, September 19, 2022

Sunday, September 18, 2022

New best story on Hacker News: Show HN: I may have created a new type of puzzle

Saturday, September 17, 2022

New best story on Hacker News: Crazy Thin ‘Deep Insert’ ATM Skimmers

Crazy Thin ‘Deep Insert’ ATM Skimmers
558 by todsacerdoti | 452 comments on Hacker News.


Thursday, September 15, 2022

New best story on Hacker News: Stripe has decided to nuke my entire business

Stripe has decided to nuke my entire business
869 by yaythefuture | 422 comments on Hacker News.
Saw https://ift.tt/65nsygR from a couple weeks ago and figured I'd share my own story. 3 weeks ago, I woke up to a pissed off customer telling me her payments were broken. My startup uses Stripe Connect to accept payments on behalf of our clients, and when I looked into it, I found that Stripe had decided to deactivate her account. Reason listed: 'Other'. Great. I contact Stripe via chat, and I learn nothing. Frontline support says "we'll look into it." Days go by, still nothing. Meanwhile, this customer is losing a massive amount of business and suffering. After a few days, my team and I go at them from as many angles as possible. We're on the phone, we're on Twitter, we're reaching out to connections who work there / used to work there, and of course, we reach out to patio11. All of these support channels give us nothing except "we've got a team looking into it". But Stripe's frontline seems to be prohibited from offering any other info, I assume for liability reasons. "We wouldn't want to accidentally tell you the reason this happened, and have it be a bad one." We ask: 1. Why was this account flagged? "I don't have that information" 2. What can we do to get this fixed? "I don't have access to that information. 3. Who does? "I don't have access to that information" 4. What can you do about this? "I've escalated your case. It's being reviewed." I should mention at this point that I've been running this business since 2016, my customers have been more or less the same since then, and I've had (back when it was apparently possible) several phone conversations with Stripe staff about my business model. They know exactly who our customers are and what services we offer, and have approved it as such. After a week of templated email responses and endless anxiety, we finally got an email from Stripe letting us know that they had reviewed the account and reactivated it. We never got a reason for why any of this had happened, despite asking for one multiple times. Oh well, still good news right? Except nope, this was only the beginning. This morning I woke up to an email that about 35% of my client accounts had been deactivated and were "Under review", the kicker here being that one of those accounts is the same one they already reviewed last week! This is either the work of incompetent staff or (more likely) a bad algorithm. No reasonable human could make this mistake after last week's drama. So currently, my product doesn't work for 35% of my customers. Cue torrent of pissed off customer emails. And the best part is, this time I have an email from Stripe this time: Apparently these accounts are being flagged, despite the notes on our file, and despite the review completed literally last week, as not in compliance with Stripe's ToS. They suggest that if I believe this was done in error, I should reach out to customer support. Oh, you mean the same customer support that can't give me literally any information at all other than "We have a team looking into it"? The same customer support that won't give me any estimates as to how long it's going to take to put this fire out? The same customer support that literally looked into this a week ago and found no issues!? I feel like I'm going crazy over here. These accounts have hundreds of thousands of dollars in them being held hostage by an utterly incompetent team / algorithm that seems to lack any and all empathy for the havoc they wreak on businesses when they pull the rug out from under them with no warning, nor for the impact they have on customers when they all of a sudden lose all ability to make money. And all that for an account that has been using Stripe for nearly 7 years without issue! This goes so far beyond "customer support declining at scale." If lack of customer support means that critical integrations start to fail, that's not a customer support failure, that's a fundamental business failure.

New best story on Hacker News: The Ethereum merge is done

The Ethereum merge is done
773 by mfiguiere | 993 comments on Hacker News.