mindingdata

>Google Analytics doesn't report visits for users that have ad-blockers on, right?

It's not really on GA but rather the ad blocking plugin you use (Or even if you are using some browsers that try and block trackers).

As an example, if you use UBlock Origin, I think by default it uses the "Pete Lowe" list to block, which by the looks of it Simple Analytics is also blocked on : https://github.com/simpleanalytics/roadmap/issues/200

Typically UBlock is just a "block all" type thing. Adblock is a little different in that they started allowing through "Acceptable Ads" (Not sure if that extends to trackers), which people went absolute ape about because now "Ad Block" doesn't block "all" ads, just ones that it deems not acceptable.

But anyway. TL;DR; Any tracker, ad, CDN, hell even HTML Fingerprint can be blocked in ad blocking plugins, just depends on the will of the people maintaining the block lists to add it.

>It is the current generation's Rosetta Stone

To be fair. Rosetta Stone got it's "reputation" because of it's insane price point comparative to what you learnt. Duolingo on the other hand is completely free.

I actually went back to an old school casio watch recently because my Fitbit refused to connect to my phone. It had the incorrect time on it and you cannot set the time on the watch itself (Must be via the phone app).

I get that a fitness tracker is kinda worthless without syncing the data up. But I was happy just seeing my daily steps and being able to tell the time and I couldn't even do the latter.

For those of us sitting here reading this and thinking it sounds like the ramblings of a madman writing on a public bathroom wall, can someone explain what this is about?

I never really feel like these can get off the ground because they immediately go too broad. Realistically most cross platform apps will talk to a central API that does most of the logic processing, so really all you are looking for is a way to implement UI that can be re-used.

But I always find that the differences between how we expect a Web App, UWP App and Mobile App to work and behave are too different to really share a UI. Even between Android and iOS, there are paradigms that belong in one but not the other. I feel like you end up writing enough special case code to just handle one platform that it really defeats the purpose.

That being said, the one benefit is being able to write C# on any platform. But is it really that hard that if you want to write a mobile app, to learn Swift?

Others are sharing out of the box solutions.

But I will say that many moons ago when I did actually write stuff for Mongo. The oplog was a god send. You can "tail" the oplog, and get every transaction in near real time. We used this for updating Elasticsearch indexes etc in what is basically realtime, without having to poll or modify existing code at all.

Maybe, but I think you would be surprised.

I wrote to the CEO of a company with a market cap of ~6bn (For comparison, WD40 is 1.95bn) about opening an office in a town where I wanted to move (Also his home town), basically so I could work there. And I got a reply within a few hours. It wasn't a crazy big reply but it was still personal.

I think what really hit it in my case was the fact the town in question was his home town, so it was personal to him. We don't know what was in the letters that were sent to these other companies, but they may have hit a chord because they were pet projects of the CEO's, or because they had already invested capital into it and failed and it was already a mark on their resume etc. CEO's are pretty passionate people.

There was this thing called "Hostile Subdomain Takeover" where a company would point a subdomain to a particular SaaS product (Say Zendesk), sometime later, they would cancel their subscription but not change the A record.

Someone could then go and register a new Zendesk account (If the service doesn't require proof of ownership of domain), and say that they want to use the same subdomain. Now they have a Zendesk account with the URL of http://help.somedomain.com as an example. And they can phish people quite easily.

Anyway, the reason I bring it up is because for a while, I saw people spamming the shit out of bug bounties with this stuff. Because it's super simple to do.

So I'm not sure what is more lucrative for an average joe, actually learning proper techniques or trying to piggy back on some low hanging fruit that may be easy to automate.

>.NET Standard is a standard that the 3 different implementations of .NET try implement (.NET, .NET Core and Mono). Any implementation of .NET Standard can add in extra functionality, hence superset, it's a bit silly.

It's actually pretty smart if it's implemented correctly (Which it's not, there is another article floating around the moment which says that .net standard isn't working correctly because people pick and choose what to implement anyway).

So the .net standard is essentially like "interfaces" in code. It says, if you want to say you are .net standard 1.6 you must implement these things.

When you go to write a library and you want to release it to the masses. You would normally have to go "OK, do I want to write this for .net core or .net framework?". With .net standard you can write it in a way that you know that a call to some method will always be there no matter what platform is actually running the library.

A bit more info here : http://dotnetcoretutorials.com/2017/01/13/net-standard-vs-ne...

They take the 85% of 100k because it's assumed when you retire, you won't be saving any of your income, just drawing down.

This calculator is often uses to demonstrate different savings rates : https://networthify.com/calculator/earlyretirement

The reason why saving more quite rapidly lowers your retirement age is because it's a twofold saving. Firstly you are saving more money which is good, and secondly you are learning to live on less.

To take a super simple example. Let's say you can live on 50k a year. And you can get 3.5% on term deposit rates (You can in NZ). Then you should need 50,000 * (100/3.5) = 1.4 million approx to retire and be able to earn 50k a year off interest alone.

I don't know too many of Ferris' investments, but the few I did know seemed like he would have to change the world almost to make them work. Whereas other investors might have a couple of moonshots like that, but they also have a bunch of investments that solve problems that people face right now, not ones they might face in the future.

I remember he was talking about those protein bars made out of crickets. And there is valid concerns about the future of food with synthetic meats etc. But cricket bars... I mean we are so far off from that being a mass selling product.

Do you really need to burn people and go bankrupt before you can call out other people for doing so?

I get what you are saying, but not taking pre-orders while they are teetering on the edge of going bust seems like the "decent" thing to do.

Just jumping on in terms of the "architecture" certifications. I'm currently doing the Azure architecture certification (And have the course materials for the AWS ones too). They are REALLY light on implementation. It's literally like reading a feature list of every single thing the cloud provider offers.

It's for when a question comes up like "Hmm. How can we we send a message that allows a yet to be decided amount of subscribers to act on that message? I know! Azure Service Bus!".

It's not that expensive to get the certifications so I usually say go for it. But it can be really dry and not as "real worldy" as you might expect.

In Elasticsearch a "river" is the description for the pushing of data from your primary store (A database more than likely) into the elasticsearch index.

ES actually started with Rivers being part of Elastic but since deprecated it. You will still find people talking about "rivers" though as a description for however they are updating the index.

Is it really a ponzi scheme? Sounds just like any other startup mentioned here where they burn a tonne of cash while working out how to be profitable. Just because they don't make money now and there is a shortfall doesn't mean it will always be that way. Maybe they believe eventually prices will fall due to the volume, or people will continue buying membership but not use it as much etc.

The issue with this is that there are so many "grey" areas for different people. Google themselves don't really want you building links manually, they think that if you have good content, you will get links naturally and all will be right in the world.

At one point years ago I got half way through finishing an eBook/info product that was an SEO checklist. But half way through I felt that some people would find link building "spammy" no matter what. At that time, I was manually building large Web 2.0 networks with good quality content, and having it all funnel up to my main site. Even this can be seen as "grey hat" at the very least to some.

We've seen this come up a lot recently with Tesla's move to fine drivers who "park" at charging stations. Many see this as actually worsening the problem as people are happier to pay the (relatively small) fine.

Well yes because .net standard is simply the specification, and .net framework, mono, core etc are the implementations.

Think about it in a web sense. We have ECMAScript which is slowly being added to. ECMAScript is the specification and it has it's own version. Then we have browsers that "implement" that specification and they also have their own version numbers because they aren't ONLY building something to handle ECMAScript, they are building other features on top of that.

So in terms of .Net Core vs Mono for example, while they both may implement the .net standard, they can also have their own features unique only to one. It's not a straight implementation with nothing else added.

Now say you are building a website and you want to target all "modern" browsers. It doesn't matter what version of ECMAScript is up to, it matters what each browser has so far implemented. If you are building a library for .net, then you can say "OK, I implement this standard. That means Mono Version X and .net Core version Y can be used". Similar to how you would say "You need Firefox version X or Chrome verson Y to use this feature".

>On PaaS, it still makes a lot of sense to use Windows as the underlying OS

Why is this the case? I would have thought PaaS of all things would be OS agnostic as the end user doesn't really care about the OS or how things are being done in the background as long as it's simple to deploy/configure etc.

For example if Azure Websites suddenly made this big shift to Linux for some reason, it wouldn't affect anyone actually using the service.

The whole "mouse over a video and see 5 stills taken from the video" is a crazy good innovation first seen on pornsites (AFAIK) and it always blows me away.