sfilargi

Just a friendly advice. Documentation, and especially the Readme file, is like the storefront of your project. When you have lots of spelling and grammar mistakes, don’t capitalize the first letter of a sentence, and don’t use punctuation correctly, your storefront looks ugly and not cared for. People will not bother looking further than that.

Facebook is already kind of gone.

What used to be a place to hang out, share photos of last night's party, gossip, brag, etc.. is now a mind numbing scrolling experience.

It's becoming increasingly difficult to tell it apart from reddit.

And because our error handling code rarely, if ever gets executed(I often see trivial mistakes that lead to crashes in error handling case), I think the erlang philosophy of “let it crash” is the best approach IMHO.

> Anyone can index the web

Most, if not all, websites will block your bot after a couple of request even if it respects robots.txt.

Also they seem to have different rules for GoogleBot and different for yours.

My humble opinion is that at some point the started using data to steer the company, and that's why we saw an increase in the "video" and "sharing posts" and "politics", and such a push to add everyone that you have ever come across in life as "friend", because it increases the screen time for users.

Had they stuck to their original vision, share baby photos, life events, etc., the user engagement would be much lower, but it would be a happier place.

For mobile phones there is only Apple or some kind of Android, i.e. Google.

I’d rather pay $1500 for a phone than have Google in my life again.

Every time I see ReactOS in the news I get reminded of sometime in 2004 the young me telling my PC-store supervisor how commercial Windows versions will be a thing of the past now that ReactOS is around the corner.

> Good on them for removing picture messages, I can't say I'm ever happy to receive unsolicited dick pics.

Why? Unsolicited dick pics is the easiest way to weed out the creeps.

Five out of your seven arguments are directly or indirectly linked to safety. This post right here is something Dating App entrepreneurs should take a note of.

In which ways?

Only if you don’t have sufficient Google Points(TM)

I don’t think that’s true for our interactions with the recruiter. At least the ones I have talked to, couldn’t care less about my work. They only care about the odds of me clearing the interview. Their behavior is linearly related to that.

For recruiters we are literally just a product they try to sell to their internal teams. Once you understand this everything else starts making sense.

If you advertise a “privacy-sensitive” product, please don’t load css from googleapis.com and JS from googletagmanager.com on your website.

Actually don’t load anything from third parties. It’s a complete turn off.

$50 annually just to store and share photos is a bit too much for my use case. Half of that would definitely justify it. But I am a very light user.

But other than that I am 100% on-board with this strategy. Get done with the "free" accounts already.

Haven't bother to go through the T&C but I hope they have clause that say they are not allowed to use your data for data-mining/advertising.

No, we don't need the companies to split up.

What we need is a truly distributed Web. Web X.

Imagine a web where all the servers are just something like torrent nodes(or IPFS nodes). Ever user uses an Agent that just stores and retrieves encrypted chunk bytes to the servers.

No central point of control => No dominance, no monopoly, no censorship.

Hmm, it may be what you say. Makes sense.

What I have done now is covered the notch with a tape and the strain is gone. Maybe it is that I got used to it as you suggest.

At some point I will remove the tape and see if the strain comes back or not.

Your post makes sense.

What doesn't make sense to me, and drove me down this rabbit hole, is that I do the same things with the X that I used to do with the 3GS, 4, 6, 7+ and 8+. Never had a single problem.

> Stop trying to read a phone screen (or look at anything on a phone close up) in a dark room. That's it. Don't do that. It's a thing that makes your eyes and head sore. It's really well documented.

True, true. But it doesn't mean that if you sore eyes it's always because of that.

Do you ever have the feeling of wanting to know what causes something. Not to prove something, not for any other reason other than figure out why and how. I am in that rabbit hole. I am very happy with the 8+ and have no eye problems at all. But I have to known what is it in X that causes my eyes to go sore.

True, but it makes me wonder why I never had problems with 3GS, 4, 6, 7+ and 8+. Only when I got the X last year I started having the symptoms.

The difference is that when you are outside in the sun, there is visible light too, which means your pupils are about 2mm.

When you are in a dark room, they can be up to 8-9mm. This means 15x more light allowed in.

I am not saying that the LED in the video will destroy your eyes, but I do wonder if the eye-pain induced by the iPhone X that I had the past year is because of that.

Try this: https://www.youtube.com/watch?v=C0Ylyi4wW1s

Try this: https://www.youtube.com/watch?v=C0Ylyi4wW1s

+1

Yes. Just discovered, turning the “attention aware features” turns it off.

This is with FaceID turned off!

Textbook example was LinkedIn’s “Upload your Gmail contacts” prompt.

It would keep asking the user every time they visited their page.

Open source and making money can be orthogonal

It does hurt their brand. People have to go through return and re-order.

It’s becoming like eBay.

Erlang OTP’s gen_fsm and gen_statem are great for implementing state machines.

Mind you however, the immutable nature of variables really helps.

The problem here is not the Monad, but the “do” notation. Rewrite your code without it, and will be more clear and less “waste of time”