Deprecated: Return type of I::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/i.php on line 62

Deprecated: Return type of I::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/i.php on line 91

Deprecated: Return type of I::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/i.php on line 71

Deprecated: Return type of I::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/i.php on line 101

Deprecated: Return type of I::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/i.php on line 53

Deprecated: Return type of Collection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/collection.php on line 80

Deprecated: parse_str(): Passing null to parameter #1 ($string) of type string is deprecated in /home/public/kirby/toolkit/lib/url.php on line 135
One Tap Less | Feedly is Now Hijacking Shared Links And Cutting Out Original Publishers

Feedly is Now Hijacking Shared Links And Cutting Out Original Publishers

Nate Hoffelder had an astonishing surprise yesterday:

I have just discovered that Feedly has rolled out an unannounced update that changes how users share links.

Instead of sharing a link which leads to a publisher’s website, Feedly users are now sharing links that lead to the same content, only now it is hosted on Feedly’s website.

The response from Feedly about this experimental feature is even more jaw-dropping:

This is a tool we are building to help publishers increase the engaged readership in feedly. This also helps mobile users consume content a lot faster. This is still experimental but I will be happy to completely opt you out.

I don’t display ads, therefore page hits don’t affect me as much as it do to writers I follow that turned their blogs into their full-time gigs. Altogether, I think this is abusive, as Nate points out:

I really have to wonder about Feedly; it’s almost as if they don’t realize that publishers want to engage with readers directly and not have Feedly engage with readers at our expense.

It’s not like they would be sending me a check anytime soon, is it?

www.the-digital-reader.com