Mozilla Acquires Pocket
blog.mozilla.org
blog.mozilla.org
Mozilla doesn't have the resources to continue with Thunderbird.
I am increasingly baffled by their decisions and how they relate to the strategic plans [0] they've been producing for a while. Despite the worthy words in their plan they seem to have no sense of direction. That saddens me.
That said I'm happier having Pocket as an open source part of Mozilla/Firefox than a surprise integration of a commercial app.
I'm also not sure of this, but that vision thing you link to is focused on the goals of the Foundation proper (excluding MoCo), which is not all of Mozilla, and many of the decisions fall out of that scope.
No. Thunderbird was built against something that the Mozilla foundation used to tout as the future of building software in general: XUL. And there also was a XULRunner which was to Gecko/Firefox what Electron is to Blink/Chrome: a way to develop native apps using the browser engine as a UI toolkit. The difference with electron is that it was built with more native-apps facilities, like spawning up Wizard dialogs: https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XUL/Tu... All written in their XML.
It wasn't developed specifically for Thunderbird. Firefox is also built on top of the same technologies. XULRunner versions were released concurrently with new Firefox versions.
The reason why Thunderbird is a dead is because XUL is dead, or rather, will die soon. They are rewriting everything related to UI in Firefox and also terminating the traditional addon API which.. required XUL, in favor of Chrome's addon API.
Thunderbird is not the only notable app written in XUL beside Firefox. There's also Miro, Songbird, Google's adwords editor ( https://support.google.com/adwords/editor/answer/106323?hl=e... ) and many others.
Most software written in XUL has either been abandoned or going to die, anyway.
The old-school, heavy desktop apps seem to be so unbelievably light in comparison to current electron-based craziness. But I guess we deserve all the bloat for not being able to come up with sensible common API for desktop development :(
ie: They have a simple 404 page instead of some novelty page with funny text and a random webm playing in the background
...though I don't know why anyone would care about slow 404 pages either, given that they should be rarely visited and quickly left.
Unfortunately Mozilla failed to execute on that vision, leaving the field open for Electron and friends to emerge. Part of that failure was due to bad technological choices (RDF-XML was terrible), part to the unwieldy Mozilla legacy (the build system was notoriously byzantine) and part to them de-prioritizing anything that Firefox did not need. They had a working general-purpose JS-based UI runtime more than 15 years ago, and still the rise of nodeJS and html-based toolkits passed them by pretty spectacularly - because they had eyes only for Firefox and vanity projects like FFOS.
Additionally, XUL uses web tech, but it is not a standard and was never intended to be a standard (not even an informal specification exists AFAIK), so it's a stretch to say that Mozilla failed to execute on pushing XUL. What would the web gain by pushing it?
comex already named two highly popular ones (slack in particular can't be overlooked) but there are more. https://github.com/sindresorhus/awesome-electron
https://electron.atom.io/apps/
Outside of Slack, WhatsApp and Discord (see a pattern? pretty much all new chat apps are using it), I'm not sure if there's any other truly popular (among users) electron app, but among developers, electron definitely is popular and far more often used than XUL was. It's arguably more popular now for new apps than even toolkits like Qt and WxWidgets. People are writing, not one, but multiple competing implementations of things like.. unix terminal emulators in electron. These are not just webapps contained in chrome, they definitely need native access to local APIs. There's a frenzy among devs.
> so it's a stretch to say that Mozilla failed to execute on pushing XUL. What would the web gain by pushing it?
They didn't fail to "push it to the web". They failed to push it to app devs. They were rather enthusiastic at some point:
https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XUL/Th...
> Whether you need to migrate an existing web application to the desktop, are looking for a technology that will enable you to easily port your applications to multiple platforms, or want to integrate your own cool features into the browser, XUL warrants serious consideration.
And now they are arguably failing to push it to themselves as they're entirely abandoning it for Firefox and will rewrite the UI and extensions APIs to get rid of XUL.
Slack has a standalone app? I've only ever used the web version. What more does it do?
> Discord
Likewise, I never even realized Discord had a non-browser implementation.
I never even realized that WhatsApp had a non-mobile implementation.
> they definitely need native access to local APIs
Which ones?
> And now they are arguably failing to push it to themselves
Er, the whole point of Mozilla is to champion standards-based web tech. They're rewriting their UI using CSS/HTML/JS because this is feasible today, whereas it wasn't in 2005. So I ask again, why would Mozilla want to retain XUL instead of making web technologies more powerful?
Can't give an answer on slack, as it's not something I use (and I wouldn't use any of the three services if I had a choice, but you don't get to make choices for entire communities as an individual and chat apps are about communities..), but I can say something about discord.
Custom keybindings, ability to do things like push to talk while you're in game, general integration with your OS desktop features (systemtray, native OS notifications), GUI that can overlay over your full-screen window ( like this: https://youtu.be/aVQyk_GX7aE?t=98 ) and probably other features I haven't paid attention to.
> I never even realized that WhatsApp had a non-mobile implementation.
http://www.theverge.com/2016/5/10/11653606/whatsapp-mac-wind...
Released in May, 2016.. and the webapp launched in 2015.
> Which ones?
Are you seriously asking that of terminal emulators that are supposed to be drop-in replacement for iTerm or Gnome Terminal and whatever else? how do you think your bash scripts can operate without breaking on your local data in a webapp without added native calls? I feel like I'm getting trolled here.
> Er, the whole point of Mozilla is to champion standards-based web tech. They're rewriting their UI using CSS/HTML/JS because this is feasible today, whereas it wasn't in 2005. So I ask again, why would Mozilla want to retain XUL instead of making web technologies more powerful?
So a great deal of selective quoting up till here while acting sassy and not paying attention to what was quoted to support the point yet still asking the question?
Why would they retain a competitive edge when other platforms like electron are attracting all the developers to enhance their application with native access goodness, why indeed.
I'll quote it again.
> Whether you need to migrate an existing web application to the desktop [...] or want to integrate your own cool features into the browser, XUL warrants serious consideration.
Is what Electron and Chrome actually do for people now, successfully, in droves and was an aspiration they had before. As for what is feasible now that wasn't before.. electron is not going away any time soon and webapps haven't replaced native. Even more so on mobile platforms, as 90% websites are begging you to install the app with full screen popups.
Yes, because the question isn't "how is this useful", it's "how is it in Mozilla's best interest to invest in this?" Mozilla came up with XUL because they wanted a cross-platform way to develop a large graphical application, and given that they're an open source organization they figured they might as well try to popularize the framework to hopefully get some volunteer contributions to the codebase. But XUL was never an end, only a means to an end, and the technology itself no longer has any strategic advantage.
As for "failing to execute" on taking over the world of desktop apps with XUL, I don't think Mozilla will lose any sleep over it. The secret sauce to Electron isn't Chromium, it's Node.js. We can say that Mozilla failed to execute the opportunity to popularize server-side Javascript first... but that's Rhino was for, and really, nobody in 2005 would have foreseen that developers would eventually want to write their backends in Javascript. :P
Be careful with generalizations, I am surely not part of that list and know quite a few others that want their computers Electron-free.
But that's exactly how Electron and friends got popular: they allow for web-first development. Desktop support is a bonus for people who need it.
When Mozilla started working on XUL, the future of the web looked a lot like XML and fat clients. Applications would be built by desktop developers targeting the desktop in a way that would allow for the web to integrate in the background. They wanted to bring the web to the desktop, woo-hoo!
As it turns out, the opposite workflow won: applications are now built by web developers targeting the web, in a way that allows for desktops to come onboard where required. In this scenario, XUL is just too complicated for people who simply need "a web view with a couple of extra APIs". This is still "bringing the web to the desktop", the fundamental role of the runtime is exactly the same; but the paradigm is opposite to what Mozilla had envisioned.
> They're rewriting their UI using CSS/HTML/JS because this is feasible today
XULRunner/Gecko was already built on CSS and JS, but it lived in a desktop paradigm of pseudo-native widgets - because HTML interfaces were terrible back then. It wasn't even a performance issue, but rather that everything was a page refresh because nobody knew any better. AJAX had not been formalized, and XMLHttpRequest was used (guess what) to pull actual XML. HTML4 was considered a hack that was supposed to eventually go away. It wasn't a "this is not possible today" problem, but rather "why would anyone want that?". Already there were lots of arguments on whether JS was "good enough" for desktop development, whether CSS was too verbose, and so on...
> why would Mozilla want to retain XUL
XUL is battle-tested to a different level, having survived almost 20 years, and it's a better option for pure-desktop development than web views. If Mozilla had paid more attention to its evolution, rather than going on quixotic adventures like FFOS, maybe they could have competed with Electron-style apps. Alas, now it's probably too late.
Maybe for you, definitely not for me. Most of the applications I use daily are desktop ones and I'll refuse to install an electron one unless I have to.
Maybe I'm just an old fuddy-duddy (I'm in my 20s, jfc), but I don't see how Electron's popularity is considered a given. I know plenty of people who use the given services, but none who use the desktop interfaces. VS Code is the only Electron app that I've ever seen used in the wild. Am I just hanging in the wrong crowds? Which ones should I be looking at, if so?
> It wasn't a "this is not possible today" problem
Hence "feasible" rather than "possible". :P (And conspicuously not "easy" rather than "feasible", either...)
> maybe they could have competed with Electron-style apps
I sound like a broken record by now, but I still don't see what people think Mozilla has to gain by offering a native GUI framework that people have already proven they don't want. And frankly, I think FirefoxOS, while ill-fated, was at least audacious. :P
Just to note: Atom is the original Electron app. I assume you've seen more people use that than Code.
Chew up a bunch of RAM and glitch display compositing if my experience is typical.
I always thought Mozilla should have built a Linux distribution (or rather, forked debian like everyone else ha!) and implemented their Firefox UI kit (Gecko right? I'm not as familiar.) and made a Front end for it that was smooth and easy to build apps for using web technologies, but could still run native *nix apps via debion packages.
I believe that now as much as I did when I was younger, but the itme for desktop OSs may have passed.
It would have been a hit I think. Well designed, well maintained, well documented. At least in my starry eyed version of this universe where unicorns exist
It does not seem like the right place to invest to continue having relevance in the marketplace.
I see that with my colleagues, who have Gmail (Gapps for domains) in one tab and OWA in another... instead of using a mail client with unified mailbox and not having tp look after which account has the message.
Yes, Apple Mail.app user here, who is not going to switch to webapp mail anytime soon.
That Mozilla is a Corp owned by a not-for-profit isn't the real thing anymore (ie not what people may believe, not that they have any obligation beside following the rule of law) - it just frees the Corp from having to report to random share holders - instead, the Corp and the Org self-select a Board of directors that they report to.
At the end of the day, it's otherwise now similar to many corporations.
1. Do project managers, product managers, etc. count, or only real managers with teams reporting to them?
2. Do urinals count, or only real sit-down toilets?
/s
Of course that doesn't always mean more people going at the same time as some people don't like urinating so close to someone else so the second spot goes unused, and some of us prefer to sit for a no.1 anyway unless in a rush.
That's not the case anymore with this merger though, right? Pocket will now cease to make actual money.
Mozilla Corporation is a for-profit, taxable entity. Here are their articles of incorporation: https://www.mozilla.org/en-US/foundation/documents/articles-.... It is itself a wholly owned subsidiary of Mozilla Foundation, which is the non-profit thing that people call "Mozilla". The Foundation is really just a holding company. The thing that people call "Mozilla" that does all of the work is The Corporation.
Acquisitions happen when the stakeholders (founders, employees, and investors) don't think they will get the level of return on investment they will be satisfied with.
Even if they DO decide to sell, the case you describe (on the verge of being successful but requires money to get to that point) sell at a disclosed amount. Undisclosed amount mostly means the investors and founders are not proud of the result so they would rather just keep it private.
I don't think Mozilla can make meaningful impact in a world where it doesn't make products that internet users want to use. It would be a largely toothless advocacy organization at that point.
- Instead of shareholders, nonprofits have members. Members don't own the corporation (no one does) but control it insofar that they hire-and-fire its directors.
- Memberships normally can't be sold, and nonprofits have no equivalent to dividends.
- There are stronger conflict-of-interest protections, preventing officers from signing cheques to themselves or otherwise using the corporation's resources for their personal benefit - at least without someone else's approval.
A typical setup for nonprofits is to tie memberships to being a director, so that current board members choose their own successors. This is known as a "self-perpetuating board".
Regional differences may be relevant here: in Canada, you can incorporate a nonprofit corporation and later apply for charity status (which restricts the company's possible activities in exchange for a 0% income tax rate) but it's completely optional.
In the US, on the other hand, to the best of my knowledge, one has to establish a for-profit entity first and then apply to the IRS to recognize it as a charity (which is a lengthy process). The words "charity" and "nonprofit" are interchangeable in the US for that reason.
If the concept of a non-charitable nonprofit exists in your jurisdiction, you can get the benefits of a nonprofit structure (ie. no owners) without restricting the company's activities, minus tax exemption and being able to issue tax receipts.
For context: I founded a non-charitable nonprofit in Canada; I'm not super familiar with the US side of things so I'm happy to be corrected.
The US works similarly. You incorporate as a nonprofit, but you have to separately apply for tax-exempt status afterwards. If you don't, you're a nonprofit without the benefits of being tax-exempt.
These things are hard or maybe impossible in a non-profit (IANAL/correct me if I'm wrong)
Non-profits can make surplus revenues over costs and retain them; they can't return profits to shareholders or other particular beneficiaries.
Certain classes of nonprofits are restricted from certain business activities, or limited to certain activities. E.g., charities (501c3 nonprofits) must be organized and operated exclusively for purposes on an list of charitable purposes.
However, I just checked my queue and couldn't see any.
Just pocket money though.
And as a non-profit entity, could they retain some profit they have as investment or cash somewhere. In case some day they run into negatives they could use those as reserves?
But at the end of the day, Mozilla need some very serious management restructuring, starting from the very top end. Having been a Netscape user from over two decade ago, I finally left Firefox. And if you follow their decision, mailing list etc, you can feel how bureaucratic they are. Slow response to market changes, completely lack of ( actionable )vision, often having completely unrealistic target. Extreme inefficiency in development of its product. And these aren't my thoughts or comment only, their are many ex mozillian employees who felt the same. We all thought Mozilla should have been a great company achieving far then then they are today.
I think people simply aren't aware that all the major revenue associated with the NFL goes through specific teams, which are normal taxable corporations. Humorously, people also aren't aware that they gave up their tax exempt status, so I'm not sure that decision was worth it.
I'm all for them killing it.
If you like thunderbird theres postbox developed from thunderbird
There's a bunch of config tweaks that are supposed to help but so far they haven't.
Also, sometimes it'll just not find certain messages. That also means it's time to clear out and rebuild indexes.
This has been my experience every time I use thunderbird, over many years. I'm not sure what it is about my mailbox that makes me see these issues when others don't.
It's a good program but could use some maintenance loving.
I suppose I'll have to learn to live with mutt eventually.
Mutt is the only way I can keep up with my mail volume. The only time the UI doesn't react instantly is when it loads huge mailboxes. And it still does that faster than I've seen graphical clients load the same mailbox.
Add to that pretty much infinite customization, and it does indeed suck less.
If you have to deal with large amounts of mail for pretty much whatever reason, you can do it faster with mutt than with any other client I've ever used. Yes, there is a learning curve. It isn't a vim-style learning curve, but it is there. But if you're considering a command line MUA at all, you can handle it.
Why would it be slow? I can only type so fast and sending/receiving mail is mostly dependent on the connectivity, not on the software.
I have a need for more people to repeat the same process. There's zero chance I'll be asking them to download TB.
This means depending on your storage configuration and how you use folders, potentially writing 100MB, 1G, 10G, etc. back to disk on folder content change.
For batch processing though, I use the CLI tools - thunderbird is view/compose only (procmail/formail/archivemail/offlineimap,etc)
I was hitting performance probs on bigger folders, and setup some more strict archiving to archive older mails to subfolders/zap offline using an 'archivemail' job, etc, and the problem went away, with TB being quite snappy.
as I understand it there was some effort to support 1-file-per-email, which might be an option now, but this has it's problems too.
Outlook has it's PST corruption hell...
Basically, in my opinion, email is a pain, each client shows it differently, though I am admittedly not up to speed on Opera Mail.
You seem to be attempting to address just the slowness of my complain and not its overall awfulness. Start-up time, loading each email; I've never seen it work very fast it always has that android-like lag throughout the entire thing. It also doesn't feel native to whatever OS you're using it in almost like using a Swing app.
The UX is just awful.
So if you think Thunderbird should be killed, what do you suggest as a replacement? It needs to be free, and run on Windows for my company to use it.
tl;dr: I think Mozilla has actually treated Thunderbird fairly well (but not quite as well as I'd like).
Thunderbird has been difficult for Mozilla to support for a while. In many ways, Thunderbird is only in as good a spot as it is because of people at Mozilla who still care about Thunderbird. There are lots of Gecko features that are used by Firefox and Thunderbird, and often, Gecko devs who make breaking changes to something Thunderbird uses will - if not fix the bug - at least alert the Thunderbird team of the breakage and point them in the right direction to fix it. They're also willing to support (some) stuff that only benefits Thunderbird, especially in the text editor. This can be hard for both teams though, like when Mozilla made huge changes to the Firefox build system; since Thunderbird imports the entire Firefox source tree, Thunderbird had to keep up or be unable to build.
As you can imagine, these difficulties will only be magnified by the (slow) move away from XUL. Worse, Thunderbird's codebase is pretty crufty and full of decisions that last seemed good over a decade ago (e.g. libmime's decision to create its own C-based object system instead of using C++ like the rest of Gecko[1]). It would take a lot of work to make the codebase not suck, and I'm not sure Thunderbird has ever had enough paid staff to do that in a reasonable timeframe. These architectural issues are the reason that message tabs in Thunderbird aren't actually multiplexed: every time you open a message tab, it actually just rearranges the elements from the single instance of the 3-pane layout to make it look right. (That's why scroll position in message tabs isn't preserved when you switch tabs.)
Thunderbird has also has significant difficulties finding a way to make money. Those who remember the Mozilla Messaging days (and the subsequent merge back into MoCo) might recall how that's when the team pushed for features like "Get a New Mail Account" (which has partnered mail providers who could sell users a fancy email address), "FileLink" (which has partners providing file hosting), and even a planned effort to do like Firefox and make money from search referrals (this fell through for some fairly strange partnership issues that I'm not sure I can talk about).
However, despite their general desire to discontinue financial support for Thunderbird, Mozilla (the Foundation, I believe) has opened up donations specifically for Thunderbird[2] which, as I understand it, gave the Thunderbird Council the ability to hire the first paid engineer on Thunderbird in several years[3]. In addition, Mozilla has worked to help Thunderbird find a new long-term home and has provided infrastructure support when they really don't need to do either.
While I think Mozilla should place a greater focus on email, I'm not sure Thunderbird is the best way to go about that, especially as Mozilla moves away from XUL. With the rise of Electron/Positron, something like glodastrophe[4] (based on the ill-fated Firefox OS email app) might have a better long-term outlook. However, trying to replicate all (or even most) of Thunderbird's features in a new application would be a huge effort and it's unclear whether the app would be popular enough to make all that effort worthwhile; I expect Mozilla would want to feel confident that they could use such an app to influence email/messaging standards.
I don't know what's going to happen in the long run, but as a Mozilla employee who started out working on Thunderbird, I still have a special place in my heart for it. I hope that one day Mozilla will be willing to revisit email, but it might take a while.
[1] https://dxr.mozilla.org/comm-central/source/mailnews/mime/sr... [2] https://donate.mozilla.org/en-US/thunderbird/ [3] https://mail.mozilla.org/pipermail/tb-planning/2016-December... [4] https://github.com/asutherland/glodastrophe
https://github.com/nylas/nylas-mail'
(I work at Nylas)
I don't understand why people are disappointed that Mozilla has stopped actively developing thunderbird - it means it's not going to change. There is an email client that you like, as is, and want to keep using, and you're annoyed because mozilla has promised not to change it?
https://www.mozilla.org/en-US/security/known-vulnerabilities...
The people who are making these complaints are disproportionately those who have no problem using Debian or Arch, so I don't think that's the crux of the issue for them.
The team that qualifies and does the release work for Thunderbird are volunteers. I believe that the builds are done on Mozilla hosted hardware.
Something is either being actively developed or it's dieing, there is no in between with software, there is no finished state.
I wish more pieces of software would get to the finished state and would slip into maintenance mode.
By the way - the IETF standardised an OAuth2 SASL mechanism (RFC 7628) a couple of years ago, no idea why GMail doesn't support it.
Basically, the only thing that is kind-of Gmail specific is the auth support (https://bugzilla.mozilla.org/show_bug.cgi?id=849540). If Gmail sometimes in future switches from OAuth2 to some other protocol, the client will have to be updated.
Yes, XUL is dead and Firefox is evolving into a Chrome substitute and while people have serious concerns about it, fact of the matter is that Chrome was designed for web apps and almost 9 years after its release Chrome is still the best browser available for web apps. Not sure how many people here remember Chrome's original goals, beautifully illustrated by their comic book announcement, but here's a refresher and try to count the problems that Firefox still has in 2017: https://www.google.com/googlebooks/chrome/index.html
In other words, Firefox is dying because users have been trained to expect security, stability, an interface free of crappy toolbars and extensions you can't uninstall, not to mention running long lived web apps. And while people on this forum will cry out for Vimperator or other poweruser extensions that 99.9% of the world have never heard about, it's undeniable that without evasive action Firefox will become a footnote in only a couple of years.
I'm also a Firefox user and I understand their move away from Thunderbird. For work I use Gmail, personal email is Fastmail, both have really good web interfaces. And while I try using email clients like Thunderbird, the web interfaces are simply good enough and always there. These are web apps btw and guess which browser is best for web apps? It's not Firefox ;-)
And for all I care Mozilla can kill every project they have, if that means Firefox continues to improve. Because it's still the only browser that cares about my freedoms.
I do use Thunderbird for offline backups, more because of the thought of losing important work email. But without combining it with an actual backup system, that's not actual backup, because IMAP does synchronization and messages deleted on the server translate to messages deleted on the client side as well. So I combine it with Arq Backup, which does daily uploads of everything on my laptop.
I do wonder whether using Thunderbird for backups is wise. I never recovered from a Thunderbird archive. Sometimes I'm thinking that a solution like OfflineIMAP or mbsync/isync might be better.
I mean, what is wrong with bookmarks and sharing links? Firefox can even send tabs to other computers I got linked via ff sync.
Iterate on a bad idea, give it a social spin, and voilà! You have a sellable startup. Except you should not buy that.
... and yet this thread and every other Mozilla apologist thread is always filled with folks who suggest that it's no big deal to assume an always-on, always-available network connection.
Pocket provides multi-platform access. And multi-browser access -- doesn't matter if I'm on Firefox, Chrome, Safari, IE, whatevs, I can pull up Pocket.
Pocket strips all of today's utterly fucked, utterly useless, utterly counterproductive Web design. I cannot emphasize too much: Web design isn't the solution, Web design is the problem.
Offline reading. Pocket articles (via app) can be read when disconnected.
Tags. You can create, and cross-reference, tags between articles.
Scale. I've got ~3k - 4k articles on Pocket. Possibly more. (I'll get to that.) They're related to ongoing research, and the ability to find, classify, and relocate large amounts of material is useful.
Whilst Pocket doesn't have a ratings or workflow-related management, I've somewhat created these. A set of tags that relates to quality (rated 0 - 5, low to high, where 0 indicates negative information, 5 indicates a foundational document -- most content is a 2 or 3, and that's rating high. Books and scientific papers generally earn a '4': definitive or clarifying, though generally not foundational.
For workflow, I'm largely working with "readme" (a reminder to go back and read closely), and a set of tags related to specific writing projects. I need to come up with a more useful system.
Pocket also ... sort of and/or sometimes ... allows for full-text search within documents. This may have been a promotional-only feature.
Given that the Web as a whole is approaching uselessness under scope of search, the ability to look through a set of documents I've already at least partially vetted is tremendously useful.
There's a whole slew of things Pocket doesn't do, which I'll address in a top-level comment. I've shared these with the firm, though I've seen little or no progress on any of them in ages.
This desperately needs adding to the UI and tools.
When I get home, I take out my Kobo eReader, which has Pocket built-in. It's very nice to read articles on an eInk display, without the distractions of an iPad or a computer.
It's HARD.
Don't blame them from not being the perfect champion we used to idealize. They are doing everything they can.
Vivaldi browser (unofficial Opera successor) is working on an HTML5 powered email app, though will it be open source?
On Android there is open source K9Mail app but it's pretty old fashion, no conversation view.
I envision a new lean Mozilla browser (like Firefox was to Mozilla Suite back then) based on Rust powered Servo-HTML-engine and a HTML based UI. Additionally an email app addon would fit in my vision.
In a story that began two years ago with Pocket's integration by Mozilla [1] in Firefox [2], large segments of the userbase spoke out with scathing criticism.
This, at first blush, appears unrelated: Mozilla previously announced its Context Graph initiative, which was a bold undertaking to be built partially upon a new and emerging set of W3C standards to take back some of the control over linkage, metadata, and the consumption and annotation of web content [3] from big incumbent providers who run content portals, content silos, or content aggregators (largely the usual suspects, including Google, Facebook [4], Apple, Microsoft, and Yahoo [5]).
To understand this play, temporarily forget about Mozilla the Foundation, and think about Mozilla as a strategic competitor to the above. In the case of Pocket, a hard-to-deny side effect is that Pocket's presence in Firefox, despite the exact nature of the integration, is likely here to stay. While this is bound to frustrate many, Mozilla's competitors routinely ship software or entire platforms with tight captive integrations, against which competition has proven difficult to mount solely on the merits of values and philosophical purity.
[1] https://hn.algolia.com/?query=firefox%20pocket [2] https://hn.algolia.com/?query=mozilla%20pocket [3] https://news.ycombinator.com/item?id=13729525#13740110 [4] https://news.ycombinator.com/item?id=13375451#13375917 [5] https://news.ycombinator.com/item?id=12863565#12867493
Pocket makes Mozilla competitive on mobile because Firefox's market share on mobile is very low.
https://www.reddit.com/r/firefox/comments/5wio45/mozilla_acq...
[edit] also nnethercote is a Mozilla employee :)
Not me. I don't want a bloated Firefox; even if the bloat is well intentioned and fully open sourced.
Firefox is open-source and (fairly) easy to build - if you really want the utmost control then I'd suggest this is the best way to do it. You can easily do a build that has no Pocket integration.
There's a cost to the level of configuration that I assume you're advocating here. Not saying we can't get better here, but there's definitely an impact on code complexity, QA test combinations, and stability.
Having the codebase be as small as possible is a laudable goal - with browsers it is difficult since Web standards are fairly complex on their own, and being cross-platform brings along a lot of weirdness.
An important aspect of security is compartmentalization - for instance, using separate sandboxed processes for web content vs. the main UI (which runs with full user privileges).
Sandboxing is a good example here since it improves perf/stability/security but also adds to the size and complexity of the code.
Only in an abstract "we might have been able to implement security/performance improvements faster if we wouldn't have had to worry about breaking addons" sense. Any other effects are restricted to those people actually using the addon and don't affect everyone else.
A powerful extension interface can also be used to improve performance/stability: while e.g. adblocking certainly doesn't come for free, its cost should be more than offset by not running all that crappy code pulled from ad networks.
That's what extensions are for. Those who want it, can have it, those who don't, they won't. Everybody wins, no need to raise emotions.
If you mean the server-side then fair enough, maybe this acquisition will help with that.
https://dxr.mozilla.org/mozilla-central/source/browser/exten...
It would be great to have access to article view to build other clients, such as a Linux client.
Actually .. no. It was a very vocal minority.
In the past, I've written about [1][2] my views of Mozilla's audiences, and soon after, Mozilla's own internal audiences [3] were brought to my attention. Several of their 'user types' are either noted as averse to change or loss of control.
[1] https://news.ycombinator.com/item?id=13425956 [2] https://news.ycombinator.com/item?id=12192509#12194161 [3] https://blog.mozilla.org/ux/2013/08/firefox-user-types-in-no...
Now that Mozilla is promising to open-source this, I eagerly await adding this feature to my own fork :)
> available in the United States, Australia, Mexico, New Zealand and South Korea.
[1]: reminder: technically, streaming isn't different from download, what your computer does when watching a video in streaming is downloading. Forcing users to delete the video they have downloaded (which is exactly what's happening with streaming) so they pay the premium service for off-line use, is not a legitimate way to do business. They can do it of course, if people are willing to pay for something they can have for free it's fine, but people who don't want to pay aren't doing anything wrong.
You're not the arbiter of this.
> but people who don't want to pay aren't doing anything wrong.
Not wanting to pay isn't wrong. Circumventing the Youtube's restrictions is though.
That's exactly my point: it's not.
It may be bad for Youtube's business, but it's not morally wrong. We owe nothing to Google.
Look at 5b. Downloading Youtube videos, except with Youtube Red, is a breach of contract.
Breaking contract is wrong.
Too bad, then every single user of Youtube is violating this rule: the browser needs to download the video to play it, streaming is just the act of automatically removing the video chunk after it's played. I don't seen written anywhere that the user is forbidden to prevent the deletion of the video chunk he downloaded.
Even if Youtube updated its rules to fill this loophole, I would still be allowed to do it. In France people are protected by «l'exception de copie privée» which allow them to have their own copy of video or music which their are legally allowed to see/listen.[1] That's why we are allowed to record TV broadcast. I guess there must be a similar law in the US but I'm not really aware of the regulation there.
[1] sharing the video with somebody outside of your family is forbidden though.
It's not their (the user's) content.
And anyway, despite the name, youtube-dl supports a whole lot more than just YouTube.
$ brew install youtube-dl $ pip install youtube-dl
I wish we had these options in Canada, because mobile bandwidth is stupidly expensive over here.
This is because Internet in India sucks
Ingredients:
1. Termux App.
2. Termux API App.
3. Termux CLI utilities. apt install termux-api
4. Python: apt install python
5. youtube-dl: pip install youtube-dl
6. VLC App. Install from app store.
7. A set of shell functions for clipboard and application access:
alias xc='termux-clipboard-set'
alias xp='termux-clipboard-get'
open ()
{
termux-share "$@"
}
lrwxrwxrwx 1 u0_a204 u0_a204 29 Apr 26 2016 Download -> /storage/emulated/0/Download/
(alias | egrep x[cp]; typeset -f open) | sed s/^/ / | xc
With all of that, you can download and play, in one swell foop, a video (assuming you know the output format you prefer -- something you can set as a youtube-dl preference):
open $( youtube-dl -f 18 "$(xp)" | awk -F':' '/Destination/ {print $2}' )
I'd still prefer to be able to use a commandline audio player with controls rather than the GUI client. There's a very simple "play-audio" command, but it has no controls -- <ctrl>-C to end is about it, even backgrounding doesn't actually stop playback.
I've messed with the sox "play" command, but it doesn't have an assigned audio device, and I've been unable to convince it that such a thing exists (see StackExchange posts regarding Android for similar issues/discussions).
Then install youtube-dl as follows:
$ brew install youtube-dl
$ youtube-dl "https://www.youtube.com/watch?v=dQw4w9WgXcQ"The browser is such an obviously poor place to stick A/V. Other than, of course, the fact that advertisers slobber over cramming every more crap down some "channel" or other.
Thank god there's a native iOS/Android client.
Meredith L. Patterson has addressed the point of Port 80 (or 443) adequately. For the time being, we're locked into that.
My point is that handing of A/V material to a dedicated AV app is, all else considered, probably optimal. It's the 4th browser replacement mentioned in my "Tabbed Browsing" rant, elsewhere in this thread.
BTW, I'm unable to access /storage/emulated/0, it seems Termux doesnt have permission (and the app doesnt list it in its permissions). Is your phone rooted?
I've just confirmed though that I can create and delete files on /storage/emulated/0/ YMMV, is all I can say.
Allegedly, you can read things offline, but that feature never works for me. It seems the feature for offline reading doesn't exist at all in Firefox (which I'd assumed was the point of its integration, but my assumption was wrong), and I've tried the Chrome desktop app and the Android mobile app ..nothing I save to pocket is ever readable without a data connection. It must work for some content for some people because I see people talking about it like it does. But, without that feature I see literally no utility in Pocket...it's just a clunky bolted-on bookmark manager, and so I end up going back to bookmarks with tags. I use Sync and I have Firefox on all of my devices. So, my bookmarks go with me.
So, I guess it's good that it's going open source. I wasn't comfortable with the way integration was presented back when they added it...it wasn't at all apparent, to me, that Pocket was a third party for-profit entity when the "setup your pocket" process launched in Firefox, since I'd never heard of it before that. But, it still seems like a solution looking for a problem. I'll give it another look. Maybe I was just unlucky with my choices of what to save...but it seems like if offline reading is not going to work on a page (for whatever reason) it should warn you. It'd suck to get on a train/plane or get lost in the woods, with plans to catch up on some reading, only to find there's nothing there.
But, maybe that's not even the primary purpose of Pocket? I dunno, it's still pretty fuzzy to me wtf it's for, if not that.
Loved the book / movie but haven't read that article. Do you have the link? Thanks.
The main thing with the work-around is that you need to start Pocket on your phone while you have a data connection so that the articles are on the phone. There may be an option to automatically download the articles, but I've never found it. After the one-time data connection, it comes up offline.
This is the case when I save from the computer and view them on my phone (or different device, I guess, but I've not checked a different computer). Your luck may vary.
Hmm, I always found this to be obvious, and not a work-around. How else would they entered the phone?
Also check your download settings. If set to "download only on wifi" then the app won't download if you're on mobile networks. You can also set the "refresh when opened" option to sync everything when the app is first loaded.
Strange, because that is the main use case I use in Pocket. I save article there, and it stores it for offline reading, striping all formatting. It isn't a bookmark manager, it stores stuff and doesn't need internet to read it.
This is much more common on larger PDFs, but I've had it happen on so many sites that there was a point when I literally resorted to PDF'ing the pages I wanted to save - which is a damn shame, because Pocket's reader view really does do a good job.
If I remember to open pocket on my phone before flying I don't have issues.
I consider this a great move for a better bookmarking experience in Firefox as well as a better pocket service.
To me, the whole Pocket thing always smelled of cronyism. Someone is friend with someone else, and lo, Pocket appears. People get all angry, Pocket's hockey-stick fails to materialise, and lo, Mozilla bail them out...
I don't think that there would have been that many other suitors for pocket, so depending on how close they were to just closing the price might be extremely low (or are any numbers making the rounds?). Maybe there is not much acqui in the hire, could have been more like a deal between founders and investors, "allow me to take the brand with me to my future employer".
Pocket used to have a feature aimed at surfacing high-quality content from the collection of things a user had already pocketed. They removed that feature. I was paying for their premium service before that change. After they removed it, I stopped the premium subscription because I wasn't sure what pocket's value to me was anymore.
Now they have a recommender that recommends things you haven't pocketed yet. But that just encourages the user to accumulate an ever larger collection of pocketed things, not surface the best things in that collection.
Ever since, I've reflexively kept saving things to pocket, hoping they would bring that feature back. But the only practical thing I have done with it is pull up something I just saved recently, because it will be near the top of the list.
Pocket's CEO also writes, “In fact, we have a few major updates up our sleeves that we are really excited to get into your hands in the coming months.” I hope they will bring that feature, or something with a similar aim, back.
I want distraction free reading which means no social recommendations, sharing and other stuff. Things I would really like is pdf support, x days of reading left, auto scrolling and detailed statistics about my reading. Also cool would be some garbage collection, e.g., news articles are useless to read in 2 weeks but a blog post may be still useful in a few years.
And, as I've described in a blog post I did about Pocket, the recommendation system they created fails in one huge aspect: it is recommending me things that I've seen elsewhere but just decided not to pocket...
My view is pretty much as yours: POCKET IS MY VETTED WEB. If I've saved stuff there, it's because that is shit I've already determined is worth a second look, and I want to be able to find it again.
Increasingly, when I hit my Pocket archive (3k-4k+ items, top 1% user), I find that I cannot find what I'm looking for. This negates approximately 80% of the purpose of having Pocket in the first place, and I've been giving strong thoughts to simply using it as a link dump until I can figure out how to:
1. Download the content myself.
2. Download the tags, which are the most important element.
3. Get the simplified-Web view. Web design isn't the solution, Web design is the problem.
4. Be able to search and filter specifically what I've already fetched. And filter by more options: date, website, author, tags (positive and negative filters), etc.
None of that currently exists. And it is increasingly frustrating.
I've just started speccing out some thoughts on how document references (files, URLs, URIs, ...?) might be improved. A sort of api / multiple-attribute interface strikes me as useful:
1. Meaningful titles / filenames.
2. A content hash. Not exactly human-friendly... I'd prefer something shorter to longer, though there's the collisions problem. Still thinking on this. Could tie into VCS (git, Hg, etc.)
3. Various standard metadata: author(s), editor(s), publisher(s), and their relation(s) to the doc. See various bibliographic or MARC 21 formats.
4. Dates: Initiated, published, modified, accessed, read date(s).
5. Classification schema. Here with time I find that working with extant rather than de novo or ad hoc schema is most likely preferable. Dewey Decimal is apparently more logical than LoCCS, but the Library of Congress classification is nonproprietary. That may well be what makes it win out.
6. Workflow indicators. Unread, read, deep-archive, to-process, etc.
7. Reputation and ratings. Associated with works, authors, other contributors (editors, fact-checkers, etc.), publishers. Some form of distributed assessment here would be useful.
The question is how to make these visible. My thought is to treat the parameters as, essentially, search. It doesn't matter what name you use, so long as the set characteristics is unique or determinable. E.g., returning 3 items would allow me to manually determine which I'm interested in, returning 300 would make that difficult, returning 3,000 would probably require some programmatic determination (or further specification).
A URL scheme, say, URI:/au=clarke&dat=lt:1980&ti:=imperial&ti=earth ... could, say, return Arthur C. Clarke's Imperial Earth.
A filesystem / virtual filesystem approach might work somewhat similarly locally, either from a CLI or graphical approach. I'm thinking of how that might work....
Very early stages.
Pocket for me was my archive of things for which I would love to have a great diversity of searching, clustering and organising tools. The addition of recommendation of things I may like is nice, but not a core feature for me - my content is.
I also tried Wallabag [0] which looks promising but hasn't the ecosystem around it yet. So I'm exited to see where this open sourcing of Pocket will lead us. ;-)
That actually sounds promising. Next logical content vertical would be video then (judging from FB's content importance)
Is there corroboration that Mozilla had/has revenue sharing with Pocket and Telefonica? I've always trusted Mozilla, this suggests that trust has been badly misplaced.
I can't help but feel that I'm being suckered somewhere here - who from Mozilla is benefiting personally out of this acquisition and why are they being allowed to steer the ship?
It's 14 months since that blog post, I realise it's not news to some, but it's really disappointing to me.
>Chad Weiner, Mozilla's director of project management told PC World in an email back then that "there [was] no monetary benefit to Mozilla from the integration" and that Pocket "didn't pay for placement in the browser". (ibid) //
vs.
>Although the company emphasizes that Pocket and Telefonica didn’t pay for placement in the Firefox browser, Mozilla Corp. chief legal and business officer Denelle Dixon-Thayer told WIRED that Mozilla has revenue sharing arrangements with both companies. (Wired, as quoted ibid) //
They seem directly conflicting statements to me barring a monumental coincidence. Even if it were considered not contradictory, per se, then it's highly misleading. If I say "I wasn't paid to write this car review" and it turns out I get a cut of sales of the cars ... pretty fraud-y.
Now it makes at least some sense.
In their defense, it won't be the first time they've gotten into operating a service -- there's Sync, for instance. So if they see expanding FF's bookmarking abilities as a key strategic differentiator, buying an existing read-it-later service they're already familiar with could be a simpler/cheaper way of getting there than building one from scratch.
https://blog.mozilla.org/blog/2012/11/28/mozilla-invests-in-...
I know there's wallabag, but i always felt it was too hefty for self-hosting on, say, a small digital ocean vps. I've been using Shaarli [https://github.com/shaarli/Shaarli] because its so lean, and easy/quick to set up...though admittedly it is also lean on features (which i'm cool with, but others might want more). My hope is that pocket - once made to be self-hostable - is easy and lean to self-host on a small vps.
...Though even if its not as lean and easy to set up, the fact that pocket will now/soon be added to the open source world is always a win!
Very early app, features are rolling out daily. My end goal is to build a recommendation engine out of user data, while keeping things anonymous.
Although social bookmarking has been done plenty times before, I think execution has been sub-par in previous solutions. My aim is to make things streamlined and fast for the user to go from 'what was that link?' to 'there it is' (sidenote: check out slushi.es opensearch, and how it behaves when there's one result (only works for signed-in users)).
A complaint I hear often from Pocket users (and other save-for-later users alike) is that they will save 100s of links without ever going back to reading them. I, too, shared the same sentiment until one day I experienced a 'what was that link again?' moment. It was rare and fleeting at the time, but since using slushi.es more and more, those moments have appeared with increasing frequency.
I believe the best save-for-later app will transform the regular web browsing individual's habits of reading an article and forgetting about it, to reading an article and remembering it later; either a day later, a month later, or perhaps years. The thing is remembering. I think a good save-for-later app works as a memory reinforcer; something that augments your ability to build and recall knowledge.
Tags are essential. Think about this: a user saves this link to a list of stories about Pocket. He also collects links about Mozilla's management, so he puts it on a list of stories about Mozilla. Then he remembers that he wants to talk about this link with a friend, so he adds it to a list of links he wants to share with his friend.
According to "lists," he has to choose between one of those three lists, while with tags he can use all three. Search does not replace tags, and neither does having to manually type keywords into the description field.
Leaving out tags is a fundamental oversight. I would never consider using any service that didn't have them.
the functionality as it stands is, pasting a link and hitting ENTER will add the link.
it needs to be pre-pended with http in order for it to add a link, otherwise it will perform a search.
this will be changed to add a link (http prefixed or not) in any case when there are no search results
Better optimisation for mobile viewing has given me less use for Pocket, but I still use it a lot, so I'm interested in your opinion here.
I do sync pocket right before a flight but find myself engaging with it rarely.
I find my use of bookmarks akin to liking something on facebook (or even saving it for later, which I never go back to).
For me it's a great time saver, I see some interesting article during work, but instead of wasting my time on it during work, I save it for later. Granted I get no signal during the subway where Pocket becomes a really useful app, but it results in me being a lot more efficient with reading.`
This way I can go back and read the articles that I really care about, while still saving low priority stuff that I only go through when I'm bored.
I started putting things in Google Inbox, and I found that I like the reminders to read things - but I don't look at those either. I just keep pushing them back, and eventually, during a less busy week, move them over to Pocket, where I can truly stop reading them.
One day, years from now, I'll read everything I've put into pocket over the years and finally understand the universe.
The mobile app also syncs the slimmed down versions so you can read them while offline. If you're using it for that, be sure to open the pocket app once in a while as it will stop syncing if you haven't opened the app for some [undetermined] amount of time.
I use Pinboard for organized reference bookmarks, and Pocket as a dumping ground for anything that seems interesting. Some of it gets moved to Pinboard or deleted, but otherwise I like keeping it there as a record in case my brain decides something from the past is important again.
I don't read all of the articles I have on there, of course, but that's OK. It still works for bathroom or on-the-road reading. Admittedly, games get played during toilet visits more often than articles getting read.
1. Total articles saved. Archived. Rread.
2. Counts by tag.
3. A "times read" count. There are hot articles I hit a lot.
4. Numbering of items on page.
The lack of ANY user-focused stats or reporting on virtually any Web-based tools is ... kind of creepy, actually, given the extent user data is sliced, diced, marinated, and skewered on the provider and advertiser ends.
Back to the matter of what's read: Pocket is effectively my "vetted web". Content I've found and found at least worth a second look. The biggest problem(s) I have presently are that I cannot effectively mine that archive. Pocket's tools for searching, ordering (or unordering -- there's a strong argument for randomly accessing a stratified sample) are a hugely increasing friction point.
What I've started using some time ago, though, is Reread.io – it sends you emails containing random articles from your saved list, on specified intervals. I have it set up to send me a couple each week, that way it doesn't feel "forced", and better than having them forever forgotten.
[1] http://blog.del.icio.us/?p=1193
[2] https://www.facebook.com/delicious/posts/10153614657337205
As a concerned user, I even wrote this a few months ago http://constantbetasoftware.com/2016/09/02/pocket.html
How can I apply?
Longer term, my understanding is that we want to use Pocket's expertise and data to help build a recommendation engine for the open Web (Context Graph: https://wiki.mozilla.org/Context_Graph). This speaks directly to the problem of sites like Instagram which restrict links to external sites: users can enter via URLs, but they can't navigate away. (More reading: https://www.theguardian.com/technology/2015/dec/29/irans-blo...). If anything could help users route themselves out of these silos, it'd be a huge win for the openness of the Web.
I'd love to help on the recommendation engine. I'm (for two years now) at the top 1% of users.
I also happen to live in Brazil, to be a native portuguese speaker and the recommendation system absolutely sucks. I get a lot of articles regarding startups and Trump, but absolutely nothing in portuguese and/or about Brazil.
I'm excited though, since the reason I hadn't used Pocket in the past was because I didn't want to be part of yet another walled garden (YAWG?).
A quick look at Crunchbase shows that they'd raised $14.5M from investors. Given Mozilla's ~$300M of annual revenue, I wonder whether this leans towards an acquihire or a technology/product acquisition (definitely not a business acquisition). Difficult for me to assess the significance of 10M users for a company like Mozilla.
Now that would be a strategic acquisition.
In this case: https://techcrunch.com/2010/04/30/opera-fastmail/
For those interested in an alternative, I am currently building a simpler bookmarking tool [1] that works pretty much exactly like Pocket or Instapaper. Email This will extract useful content from a page and send it to you via email instead of you having to download an additional app or login to another service to access your bookmarks.
I didn't really trust my saved article data to a random startup. Being under Mozilla means now I'll actually use it.
My only complaint is that a large portion of the Recommended content is junk from Business Insider. Hopefully this will wane as Mozilla's priorities are implemented.
I'm mostly limited to firewalling domains at my router. Doesn't stop them from turning up on, e.g., Web search.
Otherwise, you have to click on a FB link to get the unmangled URL, thus counting against your number of free views every month.
Or Archive.is
A question: what advantages privacy-wise does Firefox have over Safari on iPad and macOS? I frequently delete all cookies on Safari and set strong privacy options. I ask because I have transitioned in the last year or so to working on my iPad and MacBook, largely letting my Linux boxes collect dust. On Linux, using Firefox was an easy decision. On iPad and MacBook, Safari is more convenient.
I get that pocket offers the option to tag, but different people have different preferences and folders would be nice.
Also a bunch of large squares doesn't seem to be the best way to organize information consisting of web blogs and pictures.
Hopefully mozilla will make some UX changes to pocket.
I wonder if Pocket will be completely free now or if mozilla counts on this to fund more of its efforts. Beyond that. I also wonder if this means a read it later service will finally properly support RSS. Forgive me I don't know the features of pocket but as i understand it is does not correct?
I been using the built in firefox RSS feeder for years. with pocket integration it'd be a lot more useful.
https://johnrockefeller.net/use-pocket-without-being-tracked...
Hope they build in some Context Graph projects into Pocket, as there is some great ideas their.
I don't know the ins and out of Mozilla dual identity as a foundation/corporation. But it'd be unsettling to learn that part of your donations to an open-source project is financing a corporate acquisition.
For legal / tax reasons, MoCo can only push a tiny fraction of its revenue up into the Foundation. This means that donations are necessary to sustain the Foundation's initiatives.
(appreciate you clarifying this here)
The possibility of adding them myself without rebuilding the whole app is exciting!
There's also Callahad commenting in this thread, who, as far as I'm aware, is a Mozilla employee. And well, he sort of confirmed that this is a move to diversify Mozilla's income streams:
>bearcobra 12 hours ago [-]
>Does this mark a strategy shift away from search revenue as the primary funding source? A quick crunchbase search for other aquicisions by Mozilla yeilded nothing, so I'm curious if there are other examples of them buying up for-profits.
>>callahad 12 hours ago [-]
>>Mozilla is actively working to diversify its sources of funding; the greatest step in that was when we switched from a global default of Google search to smaller, regional deals with Yahoo, Google, Yandex, and Baidu toward the end of 2014.
I've been using Pocket for a couple of years, and am a top-1% user. It's been useful, though also highly frustrating, and is at best only about a 50% solution.
I've provided considerable feedback to Pocket over issues and features. Over the course of a couple of years, few if any of them appear to be addressed, which has been highly disheartening. (Any Pocket folk: I'm "dredmorbius" at gmail, though not in my account, which is otherwise attributed, because, you know, privacy, Kristalnacht, Snowden, etc., etc.)
I'd previously used Readability, which was nice in fixing a primary problem of online content: Web design isn't the solution, Web design is the problem. But that service shut down, on 30 days notice (though with loud signs for the previous couple of years) last September. I spent several days largely manually transferring information out of Readability (404 links meant that a straight export wasn't useful -- I had to track down alternative references where possible). I'm hoping I don't have to go through that again.
I've looked at other alternatives: Instapaper (no compelling use case), Pinboard.in, by our very own @idlewords (his comment below was ... not particularly useful). Upshot: without a very specific walkthrough of the product, I can't tell if it's worth my time, and my time would be a week or month of trying to reconstruct the structure I already have in Pocket, in Pinboard. I've visited the "Tour" link multiple times, and no, it isn't clear that this offers me anything useful.
I'm thinking that RMS's model of having an email-based web-requesting systsem might actually be more useful than anything else. A Mutt (or Emacs mail-mode) searchable, taggable archive, date-sorted, threadable/groupable, would be a huge win over a lot of other alternatives. I've been thinking through other ways in which I might create my own self-hosted archive repository.
Zotero is another option, though again, I can't quite penetrate the use model / workflow.
In both cases, the prospect of being stuck with as-published layouts rather than as-useful layouts (have I mentioned: Web design isn't the solution, Web design is the problem) is disheartening.
I'd really like to have an offline / commandline tool which could manage webpage decrufting. I'm aware that it's not a fully deterministic process -- the problem with the Web, for better or worse (I've been suspecting the latter for some time) is that there are no publishing standards, and content follows no consistent form. That said, much content can be divided into two general categories: 1) known states of fucked up and 2) unknown states of fucked up. Growing the size of category one, and taking the hopeless cases and simply stripping all markup from it and starting from scratch (something I do myself, manually, far more often than I care to think) is a semi-reasonable approach.
I've written a few times on what's plaguing the Web (as have others, Maciej's rants are particulalry recommended).
Tabbed browsing: a band-aid: https://www.reddit.com/r/dredmorbius/comments/256lxu/tabbed_...
The Reference Management Problem: https://www.reddit.com/r/dredmorbius/comments/50o1jv/the_ref...
And some general feedback (wrapped around some specific feedback) to Pocket: https://ello.co/dredmorbius/post/3eucmp_s0tumjuoxmfclbw
(Yes, it's heavy on the caps and asterisks -- it's difficult otherwise to indicate important points in email. SoKookMeHarder...)
Borrowing from that last:
Don't put solving your own problems ahead of solving those of your users.
The features I do use, heavily, and would like to see improved, are article view (many websites remain glitchy, I'm well aware this is a whackamole problem, but it does need to be continually addressed), import (I've been working through a backlog of 2,000+ Readability articles migrating to Pocket, slowly, one-at-a-time, there's no automated tool), bulk-action tools, sub-corpus tools (working on a specific set of articles at a time), and tags tags tags tags tags tags tags tags tags tags tags tags tags tags tags tags tags tags tags (did I say tags) tags tags tags. And more tags.
A principle, perhaps the principle problem with the Web as it stands is organisation particularly as concerns quality and vetted content.
There are various sources who can vet content. Some are good. There's one I especially trust, and whose judgement over what I like is strong: ME.
I've commented before, AND CONTINUE TO HUGELY APPRECIATE several features of Pocket, especially the ability to peform full-text searches of my current and archived articles. It's HUGE.
One of my (many) interests is COGNITIVE LOAD. Pocket is a tool for REDUCING COGNITIVE LOAD when reading online media. I see several mechanisms:
1. A standardised presentation of Web content. I can look at an article, and identify what is the primary content (virtually all of it), what's metadata (usually the top -- you do a good job but I'd love to see this improved as well), and where the controls are (standard Pocket bits).
2. Elimination of online distractions. Sidebars. Ads. Animations. Videos. Spurious links. Shitty page layout. Shitty font choices. Shitty colour choices. Shitty CSS choices.
3. Format optimised for my device and preferences. I love you to tears for not having to fuck with zoom, font choices, background/foreground colour, etc., etc., etc., on Every Fucking Webpage. ("Web design isn't the solution, Web design is the problem.") Huge. Or is that "Hyuuuuge!" now?
4. My own curation. Anything I've saved to Pocket I've seen at least once. There's a familiarity in returning to material which makes it more valuable.
5. Tags. Again, my assigned classifications for material. (And often picks selected from Pocket's tag suggestions, which are quite good.)
Things I love about Pocket are
- Curated (and from other people I followed) "recommendations",
- tags "Best Of", "Quick Reads".
- beautiful android app
Instapaper has less features than Pocket but I find that
- Instapaper article parser is better,
- UI is cleaner, highlights ( I love these!),
- ability to switch style (type faces, article background)
- speed read
- they also have "Browse" (something similar to Pocket's recommendation?) but in Android app, it's a bit hidden in the drawer menu so I don't use it often.
- Apart from saving the parsed, "readable" version of an article, it can also save the web as-it-is. This is very useful for those times when the formatting is important (as it is in articles that include code; you loose syntax-highlighting with the readable view. Pocket can be set to try and choose the best view for each article.
- It does a great job with videos.
- It uses tags instead of folders.
- Instapaper has been less reliable for me (specially the android app), although in fairness I've used it more, so I'd notice it's unreliability more often.
I'm not that interested in recommendations, but I gotta admit that the few times I've looked at them, Pocket's recommendations were fairly good.
I've been using Instapaper for around two years now, keeping Pocket as a bag of less-important links, not-really-reading-material, and very often video. I was thinking of going back to Pocket as my main read-it-later service, specially for the first feature I mentioned.
It being Mozilla-owned and some day also OSS will surely be a further advantage in my mind.
1. Zotero doesn't have a full-service (or any?) Android app. Which is my primary reading platform. So it's simply not an option.
2. More straightforward onramp. It's pretty easy to figure out what the fuck to do with Pocket, though after a bit, it gets utterly unusable with scale (I've got ~3-4k articles, possibly more, the fact that I can't even extract a !@#$%^&() count is a major PITA, and referencing them Simply Doesn't Work.
3. Simplified and uniform presentation. Web design isn't the solution. Web design is the problem. I prefer Pocket's styling to ANYTHING* any website can throw at me, with exceptions I can count on the fingers of one hand. Most of which I've made myself.
Frankly, I'm utterly frustrated with use of the Web as a research and archival tool, and none of the options I've seen yet are satisfactory.
That being said, I started using it extensively after being a big fan of Instapaper. The browser integration (especially the easy tagging) has been really helpful in keeping my tab count down.
The only drawback, for me, was the added bulk of the Bookmarks bar. I like to slim it down, so having the single button has been great. (Also, being able to add the tags, but maybe the bookmarklet is capable of that?)
When you click the bookmarklet a little dropdown banner shows and you can add tags from there.
https://addons.mozilla.org/en-US/firefox/addon/custom-button... ... ah, and now I see it's unmaintained and recent version isn't working for some, carry on, never mind (works for me though).
They don't want it there at all, in any way. They don't want it using any of their computing resources, no matter how minute this usage might be.
They tend to see it as something that should be available as an add-on that's installed on-demand by those who actually want the functionality.
You can remove it easily, but I'd advise you to try using it.
It personally helps me go through interesting news and "pocket" it if I don't have the time to read it now, or want to keep my time for more important articles but still think it's an important piece of news.
I have both the desktop Pocket application and the mobile Pocket application. They download the web view offline, like that I can read articles wherever I am, when I have some down time.
It's been a huge time saver when it comes to only reading what is important during the day. Having less tabs. And being able to see what I deemed important to read after a while.
Completely subjective. Also pointless as it could easily just be an addon. It's just bloat however and my own subjective POV is it's useless. I've never once used it, have no desire to use and don't even know anyone who uses it.
So yeah, there ya go
[0] https://bugzilla.mozilla.org/show_bug.cgi?id=open-pocket
Pocket is now Free Software, which might make those elements from RL you liked possible again.
Continuing the current revenue model and supporting Context Graph seem at odds with improving user privacy. Pocket isn't now Free Software, but hopefully it will be feasible to self-host whenever they do release the source.
I hear ya, being in a similar boat. My hope is that Netsurf ends up being a decent contender here by the time Mozilla kills XUL. Else, hopefully TST will indeed be made possible with Firefox-specific WebExtension APIs.
We may not land everything we need by the time Firefox 57 releases, but we'll get there. If we miss, you have options: you can decamp to Firefox ESR for a few months, where TST will keep working, or someone could theoretically convert TST to a WebExtension Experiment which would work on DevEdition and Nightly builds of Firefox.
I've noticed (on the rare instances I'm on desktop, mostly Mac these days) that Vimperator is also borked (only parts of it seem to be functioning). That's another lifesaver to me, and whatever it takes for it to come back to life and/or an alternative to provide effectively similar functionality ... would be peachy.
If I can lure you to another bit of developer / user advocacy, a bit from about 3 years ago on the content management problem:
https://www.reddit.com/r/dredmorbius/comments/256lxu/tabbed_...
Now there's a different, much better story.
I was following their experiments, and they shut all of them down while some of them were already working.
I used to use Thunderbird years ago, but they completely stopped working on it.
I just hope they don't kill Pocket, since I use it every day to save things to read later.
I think it's a failure of imagination to assume that this is going to be the extent of what Pocket will be able to contribute... they have a lot of users and popular mobile apps for instance which is useful on its own.
As the blog post points out, the hope is that Pocket will accelerate the context graph initiative.
So, I disagree that it's about "bloat" or customization. In any case, the Pocket add-on is like ~700k and it doesn't do anything if you take it off the toolbar...
Why do you think XUL and Thunderbird are good investments vs. things like Servo or the context graph initiative (which the Pocket team is going to accelerate according to the blog post)?
Do you think a non-standard framework for making fat native apps and a mail client built on this framework are going to make Mozilla more relevant?
Every time I read about something Mozilla does, I am reminded of this xkcd comic from 2013:
...by buying a crappy, proprietary app?
Pocket was originally a Firefox add-on.
citation needed
> proprietary app?
fixable