scottmf

That isn’t “intentionally slowing phones with new firmware releases”.

That’s the phone slowing the CPU when the battery gets old to prevent unexpected shutdowns. If you think this is “planned obselence” you misunderstand the issue.

iOS 11.3 now lets you disable this, so you can have full performance at the cost of unexpected shutdowns. Or you can just get an official battery replacement for $29 and your phone will be like new.

Battery replacements are $29 at Apple stores

Ah but isn’t it true that iPhones have no right click?

Hey if any GrayKay employees wanna split the bounty let me know...

What was his position at Apple?

Now that’s how you get investors

I wouldn’t be surprised if you were right.

Buzzfeed isn’t comparable to Breitbart at all. Buzzfeed does real journalism these days.

Most of the ones shown in this article aren’t really the best examples of Dark Patterns IMO.

This trick Facebook Messenger uses to get your phone contacts is a good example of how bad these things really are: https://medium.com/@scf4/an-example-of-a-dark-pattern-in-fac...

As developers we should be refusing to build features like this.

Do you have any data to show that this is a real concern with JS?

I use Safari on desktop because it syncs that stuff so well with iOS. (And it’s much better for battery life than Chrome)

What do you think it needs?

What’s wrong with that exactly?

The standard library is improving a lot.

Pretty common on HN lately.

That’s somehow much creepier than “shadow profiles”.

This looks great. Can’t wait to try it out.

The average age of congress is about 60.

I’ve seen a few articles about this (one called it “mind reading”) and I still don’t understand how it works. What exactly is “vocalizing internally”?

Yes, it’s inspired by the pipe operator in languages like F#.

The point is it looks a lot better than several nested function calls, especially when the order of the calls are important.

In JS you can do stuff like this:

  const rules = parsedTags
    .split(';')
    .map(item => item.trim())
    .filter(item => !!item);

But in some functional languages you would have to do something like this:

  Array.filter(Array.map(String.split(parsedTags, ';'), item => String.trim(item)), item => !!item);

Which makes it a lot more difficult to write/understand. (Note the order in which the functions will be called).

With a pipe operator you can do something like this:

  parsedTags
    |> Array.split(';')
    |> Array.map(item => String.trim(item))
    |> Array.filter(item => !!item);

Now that people are writing more functional JS, a pipe operator becomes much more useful since you can't always chain function calls like the JS example above.

Besides performance concerns, if you did it on each page load it would miss any content added to the page after the initial load. It would be useless for SPAs.

The best way I can think to implement it would be listening for a copy event and replacing the text in the clipboard.

Something like:

  document.addEventListener('copy', sanitizeClipboardContent);

But such a simple system would make it easy for one user to frame another.

You would need a way of signing the username. Perhaps you could hash the user ID with a secret salt, and hide that in the text along with the username.

Looks like there’s a recent proposal for them:

https://github.com/TheNavigateur/proposal-pipeline-operator-...

This is one of my favorite proposals, along with the pipe operator and partial application proposals:

  const add = (x, y) => x + y;
  const addTwo = add(2, ?);
  let x = addTwo(5); // 7
  
  x = 5 |> addTwo |> add(?, 10); // 17

The last example is equivalent to:

  add(addTwo(5), 10);

Obviously the pipe operator is more useful when order matters.

Alt-tab behavior is more of a preference thing.

>It's basically shitty linux with outlook.

Linux is shitty Linux. Except on the server. (IMO, of course).

Spaces are still there, but what they have removed is that “X”. It’s simply “MacOS” now.

I understand your skepticism considering the behavior we've seen from some of these companies recently — but when their settlement with the FTC includes an independent company monitoring their handling of user privacy for 20 years, I think it's safe to trust them on this one.

>Snapchat servers are designed to automatically delete all Snaps after they’ve been viewed by all recipients

>Snapchat servers are designed to automatically delete all unopened Snaps after 30 days

https://support.snapchat.com/en-GB/a/when-are-snaps-chats-de...

This is why:

https://www.ftc.gov/news-events/press-releases/2014/12/ftc-a...

https://arstechnica.com/tech-policy/2014/12/snapchats-privac...