- We're planning no new user visible features. Instapaper will continue to work just the way you've grown to like it, and we're not planning to change stuff around.
- We're working on making text extraction even more reliable. Besides blog posts and news articles, we hope to improve text extraction from PDFs, slide decks or even twitter threads. Whatever textual content you find on the web, with Instapaper you can save it for distraction free reading, now or later.
- Our apps will see ongoing development to improve compatibility (eg. support new devices/OS updates as they come out), but no major new features. Quality assurance will be our top priority.
- and last but not least, our goal is to establish a small, but profitable company to keep the project alive! Besides the technical aspects, our new business plan will make sure that we're thinking ahead and that we're never caught off guard by something like the GDPR again.
I could believe they will think of other things I want besides continuing to work well. But I don't want them to feel like they have to be on a feature treadmill.
So, it is not realistic to expect that they'll not do much. Ultimately, this is the bane of a consumption drive society.
You get a parsed html email with the article without the adds. It literally supports every app there is for saving (you just share via email). You can read it from any email client and easily share it with your friends. I also use fastmail which has a great full text search so finding old articles is a breeze. You can also do many cool stuff with IFTTT because again, it's just email.
GDPR blackout was a big misstep.
To me it’s a better product than pocket, reason enough for me to switch back.
At first sight, https://getpocket.com/privacy doesn't look GDPR-compliant. It doesn't mention rights of the data subject, there's no address of a data protection representative in the EU and so on … In addition, Read It Later Inc. is apparently not Privacy Shield-certified – the don't mention it and I cannot find their entry at https://www.privacyshield.gov/participant_search.
To be fair, https://www.instapaper.com/privacy includes some GDPR-related information, however, they don't have a data privacy representative in the EU or a Privacy Shield certification either.
Unfortunately it's very hard to set Wallabag up without having access to VirtualHosts.
The ability to facilitate "archiving a webpage" seems to be simple, but read-it-later software needs to be more than that to the modern internet user it seems.
It needs to;
+ Save video and images
+ Most people require a TTS service of sorts
+ Even more people want text-extraction (and boy-oh-boy this is hard)
+ Cross-platform apps & syncing
Where are the big costs here?
1. Scale (Syncing all that multimedia must be expensive)
2. Talent (doubt it's this all the teams seem to be extremely small teams)
3. AI & Scraping development (Most services are poor in their offerings here, not sure its this)
I've been thinking about the space a LOT and started to try and develop some pieces of software that eventually I hope people will be able to stitch together into something great.
When i've observed problems like this before it seems that eventually a large open source project comes along and kills the markets chance of generating any money, and read-it-later services seem to fit in that fuzzily-defined-in-my-head-only market segment.
So the plan seems that they are hoping up to $350 in revenue per Premium user over that ten year span will cover it. Which seems …low.
Please note: To ensure easy account creation, minimal customer errors, and reduced support inquiries, Instapaper accounts initially do not have passwords. If left without a password, anyone can access your account if they know or guess your username.
This sounds like a serious security issue if you ask me.
 = https://www.instapaper.com/privacy
The article hammers on accessiblity over security and I think you've taken this too far. A minimum password length of 8 is not a 'strange requirement'.
With Overcast - his podcast player, he also doesn’t require a username or password anymore if you’re just using the iOS apps. You can add a username and password to your account if you need to use the web client. But of course this is more secure. It’s piggybacking off the fact that you are logged into your Apple account (no, the Apple ID that is being used is not your actual email address, it’s a token)
It contains highlighting, send-to-Kindle, decent mobile apps, and all the other features you would usually rely on!
Feature-wise, no alternative compares to it.
The only problem: UI. It's not the UX (things are where you expect them to be), but UI just looks... wrong. The same thing applies to their website(s) as well.
Needs a jailbroken Kindle...
It lets you save complete articles and webpages to your email inbox. If it fails to extract useful text, EmailThis will save the page to a PDF and send it as an attachment.
There's no need to install additional apps on your phone or login to any 3rd party service.
I really love Instapaper and use it a lot. Especially the send to kindle feature. Luckily for them I did not stumble upon an easy 1:1 replacement.
But not even explaining the challenges seems quite a bit off and suspect. It is not like I keep my health records there (at least to my knowledge :) )
I have major respect for Brian & co for continuing on the project and trying to make it a long term indie play.
I finally gave up a few weeks back and migrated to pocket, turns out it has an importer for instapaper's CSV export, so it took about 5mn and it worked well enough for my purposes (saving articles from my twitter feed and new chapters of serials from feedly for later reading), so meh.
 $3 per month subscription https://p2k.co/
 $5 one time payment https://www.crofflr.com/#/home
+ QR-codes at the end of articles to go back to them
+ Clean configuration
+ Scheduled delivery
- Often misses images and, sometimes, even text from the original page. To be fair, I have found to be the problem of every web->ebook converter out there.
- It says it supports Kindle Back Issues, but they don't seem to work for Crofflr ebooks even on a top-of-the-line (Oasis) Kindle.
Matter of taste:
~ I'd prefer for every article to be in a separate book so I can read out-of-order, and delete and bookmark them separately. But the navigation interface within the single book (issue) is very nice.
Most likely, Pinterest's lawyers and executives were not OK with risking the fines, and also did not want to devote enough development resources to GDPR compliance for such a small subsidiary like Instapaper. Also explains why they'd spin it out -- GDPR changed the calculus.
This is speculation, but I've seen this GDPR fear play out elsewhere. Large parent companies are very worried about those worst-case fines and want to ensure there's no risk whatsoever.
The "Instapaper must be up to something sketchy if GDPR compliance took so long" narrative here seems pretty unfair. If their former owners are to blame for the long EU outage, it's understandable that Instapaper isn't going to publicly call them out -- they may even have agreements preventing this. And the whole spin-out probably took some time and logistical effort, so they couldn't reasonably focus on GDPR immediately after that either.
(Edit: not trying to knock Pinterest either; their actions would be completely understandable given the max potential fines.)
In Pinterest's case where an Instapaper complaint could have triggered a general review of their business practices, I'd roughly estimate the costs of talking to the regulator at a half million dollars. Start with their counsel ordering sales & marketing leadership to grab engineers to create and review a consent log for every outbound sales and marketing contact in their system.
Also, what you probably meant is still not possible: As Instapaper was free under Pinterest, market share was connected to $0 of revenue. So any fine would be greater than the revenue of the app's European customers.
Personally, I like the UX of Instapaper better - it's cleaner, more minimalist, and easier to read.
(I think the choice is obvious :D)
Ideally though, you can host your own FOSS solution on a raspberry pi or something. (Wallabag)
(Unfortunately, useful notifications for iPhone apps depend on an Apple Watch app.)