leveraction | 3 years ago | on: Richard Stallman's thoughts on ChatGPT, AI and their impact on humanity
leveraction's comments
leveraction | 3 years ago | on: Finding the Darkest Pencil
leveraction | 3 years ago | on: Finding the Darkest Pencil
I use several pencils and like them all really. I currently use all four Blackwings (black, pearl, natural and 602) as well as as a Tombow MONO 2H if I want fine lines, and I occassionally use the Mitsubishi k9800HB which is nice but not my favorite.
Now I am going to try the Mitsubishi Hi-Uni 10B and even the KH-20 pencil sharpener. I like the manual long point sharpener from Blackwing and it is what I use daily. Overall, for general use, I like either the blackwing natural or the 602. The Black is very dark and makes normal pencil look anemic but you do have to sharpen frequently, although sometimes pausing to sharpen helps me clarify my thoughts, so I don't really mind. The pearl gives you similar quality, but is slightly harder so it last longer between sharpenings. Also a very good choice.
leveraction | 3 years ago | on: Python Asyncio
I have also never used Go, but I am comfortable saying that Python async is much easier to user than JS async. I find JS to be as frustrating as it is unavoidable.
Using aiohttp as on api is not bad at all. Once you have the event loop up and running, its a lot like writing sync code. Someone else made a comment about the fact that Python has too many ways to do async because everything keeps evolving so fast. I this this is true. The first time I ever looked at async on Python it was so nasty I basically gave up and reconsided Flask but came back around later because I so despised the idea of blocking by server that I was compelled to give it another go. The next time around was a lot easier because the libraries were so much improved.
I think a lot of people think that async Python is harder than it is (now).
leveraction | 3 years ago | on: Python Asyncio
My setup is a bunch of microservices that each run an aiohttp web server based api for calls from the browser where communications between services are done async using rabbitmq and a hand rolled pub/sub setup. Almost all calls are non-blocking, except for calls to Neo4j (sadly, they block, but Neo4j is fast, so its not really a problem.)
With an async api I like the fact that I can make very fast https replies to the browser while queing the resulting long running job and then responding back to the Vue based SPA client over a web socket connection. This gives the interface a really snappy feel.
But Complex? Oh yes.
But the upside is that it is also a very flexible architecture, and I like the code isolation that you get with microservices. Nevertheless, more than once I have thought about whether I would choose it all again knowing what I know now. Maybe a monolithic flask app would have been a lot easier if less sexy. But where's the fun in that?
leveraction | 3 years ago | on: A large collection of fraudulent web stores
leveraction | 3 years ago | on: Differential mosquito attraction to humans is associated with skin acid levels
https://us.biogents.com/aedes-albopictus-asian-tiger-mosquit...
leveraction | 3 years ago | on: What “diversity and inclusion” means at Microsoft
leveraction | 3 years ago | on: The Lilium Jet
leveraction | 3 years ago | on: At 4.4 miles, Wyoming team sets new rifle shot world record
leveraction | 3 years ago | on: At 4.4 miles, Wyoming team sets new rifle shot world record
leveraction | 3 years ago | on: GoDaddy Statement on Eth.link Domain Registration
leveraction | 3 years ago | on: U.S. annual inflation rate drops to 8.5%
leveraction | 3 years ago | on: The era of borderless data is ending
leveraction | 3 years ago | on: There Is No CD Revival
leveraction | 4 years ago | on: How I learned French in 12 months (2020)
It was nice to hear about your success with online tutors. Finding speakers was essentially impossible for me. South Carolina is not exactly a hot bed of French speakers.
You may have inspired me to pick up the torch again. Look out Chamonix, here I come!
leveraction | 4 years ago | on: A new wave of Linux applications
I had to laugh at this.
I am writing a PWA now and this is definitely an issue in "desktop mode".
The thing is though, with giant monitors (I develop on a pair of 4k curved ultra-wides) there is so much room that most non-game apps just don't need all that much space. If you do use it all, it becomes cumbersome to move the mouse all the way to the corners because it is so far away. And even if you did use it, there would still be acres of unused space most likely, white or some other color.
I suppose you could do a true re-write and put multiple mobile screen onto one desktop screen, but that would be a very heavy lift and in the case of a saas app that will largely be used on mobile, it is pretty easy to understand why it never gets done. Bad cost-benefit and it would delay your launch.
leveraction | 4 years ago | on: Upwork asking me for a $12.5k refund as the client was using someone else’s card
"Let me translate this. Robin has been using someone else’s credit card for two years..." followed by "I’m on very good terms with Robin."
Clearly, 'Robin' is a thief and it is entirely possible that Robin and the freelancer are one and the same. That the freelancer is not asking Robin for the money even though he knows him personally is telling. Does the freelancer wonder what his good client Robin thinks about the fact that Robin ran up a 12K credit card bill(payable to the freelancer, ultimately) that Robin never paid?(And we know the bill was never paid or there would be no need for the claw-back)
And I did not see any mention of where Upwork contacted Robin. Strange considering he was the one with “a credit card connected in his account that wasn’t actually his”. Is he still on the platform?
And then he sent two years worth of work to Upwork to substantiate his claim to the money. But how could Upwork know that the work he sent was legitimately related to the transaction? Could he not have created a project request for something he had already built?
Then he apparently logs ALL of his 'time' outside of the system. He said that this time was for "a brainstorming session and a few meetings" with Robin. 230 hours worth!? I notice that dates of the charge-back transactions were not provided. Was this 230 hours the entirety of the project or just a very small slice. He wrote that he had made more that 100K on Upwork and that he had other clients. That leads me to think that this 12K represented all or most of the billing on Robin's project. Was there any billing for actual implementation, or is it all brainstorming and meetings?
This story does not add up to me.
edit: I see in the graphic that apparently the work on Robin's project was for 1533 hours, so the 230 hours would have been just a portion. It makes me wonder what/how many other credit cards were used to pay for those other hours. Hard to believe Robin was above board for the first 1303 hours and then started paying with a stolen credit card.
leveraction | 4 years ago | on: I analyzed SaaS billing dark patterns
I think the original contract is enforceable at the time it was originally agreed to. Coming up with additional terms, even if they were on the same day, wouldn't not change the original contract. Imagine signing up for a credit card offer and then sending a certified letter to the bank informing them that you will only pay a lower interest rate that you designate.
I think the stronger argument is the "incorporated by reference" argument, given the fact that those could be changed at a later time. The terms of a contract need to be clear, and any ambiguity would likely be settled in favor of the party to be charged.
I have always been suspicious of the "Click to Agree" box at then end of a long contract that no one, including the company offering it, has ever read. The problem is that there are so many (generally unlikely) contingencies that have to be accounted for. What other choice is there when there may be substantial liability in question?
leveraction | 4 years ago | on: I analyzed SaaS billing dark patterns