Pocket migration to Firefox accounts

> Why is Pocket migrating to Firefox accounts?

... nonsense omitted

What's the point of acquiring something if you don't leverage it to coerce their users into using your other products?

https://en.wikipedia.org/wiki/Pocket_(service): > On February 27, 2017, Pocket announced that it had been acquired by Mozilla Corporation, the commercial arm of Firefox's non-profit development group. Mozilla staff stated that Pocket would continue to operate as an independent subsidiary but that it would be leveraged as part of an ongoing "Context Graph" project.

I recently set up a Firefox Accounts server - basically the minimum parts necessary for a self-contained FFSync, without either calling home to Mozilla or their integrated third-parties (mostly payments and analytics; AWS, GCP, Paypal, Stripe, and a few others). A handful of microservices and a few MySQL databases and I think a Redis or two? I only recommend doing it if you enjoy it for the challenge, the stack it's clearly not engineered with an independent self-hoster in mind (though they do support it and people are helpful). It took several days to get up and running. I will share this soon, I hope...

In the meantime, if this all sounds like too much but you'd still like self-hosted FFsync, you can run the syncserver docker image standalone and piggyback on the rest of Mozilla's hosted FXA stack.

I'm not certain just how big the gap is for Pocket ATM (I know they've continuously been opening up since acquisition).

EDIT: Just to not be that guy, microservices as this isn't clearly documented anywhere:

  * pushbox (mysql)
  * fxa-auth-server (redis, 2xmysql, smtp)
  * browseridverifier
  * syncserver (actually tokenserver+syncstorage, if you're not running the docker image. db of choice)
  * fxa-contentserver
  * fxa-graphql-api
  * fxa-profile-server (mysql)

...and "just glue them together" with JWT tokens (look for the scripts in the repo instead of trying to find enlightenment through the source code, docs and issues... heh) and your reverse proxy or load balancer of choice.

When a company with a huge user base (Mozilla) acquires a company with a much smaller user base (Pocket), they're probably not doing it to cross-sell the smaller user base.

I thought Mozilla was going to be investing in Pocket and giving them the resources to grow, as well as sending them Mozilla's users — a fraction of whom would become premium Pocket subscribers.

But as far as I can tell, there haven't been any notable new features in the last 5 years. In fact, some stuff like the web app have gotten noticeably worse. I used to use Pocket almost daily, but now I use it maybe once every couple months.

So, how to fully disable it via `about:config` now?

Somewhat tangentially related. Pocket seems like a dead product. I have been using it since it can out but it feels old, slow and quite behind.

I use it extensively to capture a reading list and then trim it occasionally. Any recommendations for alternatives?

Offline web-rendered article views are a must - something pocket can’t do. And their text mode misses quite a few important details when there are equations or illustrations in the content.