Sometimes you need to "log out other user sessions". To prevent cookie replay attacks or - a very common use case - log out other sessions when a user changes their password. ASP.NET does not have a built-in way of doing this, but there's a simple solution.
TL;DR I spent the last month testing how CloudFlare affects my organic traffic by turning it off and on again™ and measuring the ranking changes. Looks like CF hurts SEO. So we've built our own caching proxy with blackjack and hookers AWS and nginx, while saving a couple of hundred $ a month on the way.
This post has nothing to do with tech nor startups. Today, while adding proper "right-to-left" support to our app UI (for Hebrew and Arabic languages) I got a little carried away and found myself discovering a lot about Aramaic languages and ancient numeric systems.
I've been a happy MacBook user for almost 14 years. Tried all of them - from a tiny 11" MacBook Air to the enormous 17" Pro - and in 2014 I finally ended up with the 15-inch retina model.
The best laptop I ever owned.
Even if you need to occasionally run Windows for work - MBP is still the best possible hardware to do that. The 15-inch retina MacBook had that unique blend or elegance, power, durability... And by "durability" I mean I fell off a motorcycle with this thing in my backpack - not once, not twice, but thrice.
So you're starting a bootstrapped web-based business and you're deciding on the tech stack. After running a software startup with zero funding for 13 years, here's what I have to say about this.
I see a lot of websites and apps using "box-shadow" like this
box-shadow: 0px 0px 20px 5px #ddd. Which literally means "lets have a #ddd-colored shadow, with zero offset, 5 pixels wide and 20 pixels blurred".
Which is perfectly fine, for the most part.
Everyone's being paranoid about AI these days. And the less people are familiar with the subject, the more concerned they are. Even some of my tech friends, even - believe it or not - software engineers, the ones have a very vague idea of how AI/ML works, are expressing their concerns.
Sometimes you need to allow users to post HTML to the server. And, by default, this is the error you're going to get:
A potentially dangerous Request.Form value was detected from the client
The first part of this post applies only if you run ASP.NET on Windows, you can simply skip to the regex hack if not interested, but I strongly recommend you read the whole post.
The following chart shows the impact on CPU usage after applying the Meltdown patch.