Short version: the new license effectively gives a BSD-like, transferable license to all projects hosted on Github and raises issues with attribution requirements of other licenses.
Update: after reviewing a few other comments, I’m not sure it’s the case. But that’s the point made in the article of course. :)
This is really a shame. Mozilla invests tons of money in a company producing closed source software while there’s this free software alternative that has been well established against that quasi monopoly. They should support Wallabag instead of Pocket… sometimes I just don’t understand the Foundation’s decisions… (and i know they need money, but this seems like a decision contrary to their principles)…
Pocket has a business model and larger audience. If they adopted Wallabag then they would be competing with Pocket, through acquisition they also get rid of their largest competitor. C'est la vie.
I too wish they supported OSS like Wallabag, but I likewise wish more OSS products had robust business models.
Presumably Pocket will become licensed as Open Source?
I do agree with you here, though.
(I have nothing to do with any of this, even though I work at Mozilla)
Super cool! :)
Yes, that’s why I created an account yesterday and transitioned many of my open tabs into it.
The Mozilla foundation is about OSS. Pocket will become OSS. Mark my words.
“Mozilla invests tons of money” – I haven’t seen any reports of how much Mozilla spent on the acquisition. The numbers may have worked out to be something reasonable for Mozilla, on a per-user basis. It really depends on the company’s trajectory and the investors' view of the company.
Acquiring a service that has lots of users and some penetration on mobile devices might not be a bad investment. I guess we’ll know in a few years.
A good way of describing Mozilla is “principled but pragmatic”. Basically, be principled, but not to such a degree that you shoot yourself in the foot in the process. A textbook example of this was the decision to adopt EME.
I’m not very familiar with either Pocket or Wallabag, but I’d guess Pocket has better market penetration and recommendation algorithms which would support existing Mozilla initiatives like context graph.
can someone clarify what exactly this implies? previously, one could compile Signal without GCM support but phone calls wouldn’t work, and there would be battery issues as well.. are those issues fixed?
Previously nothing would work in standard Signal without GCM, it required patches to get messaging working and even with the patches voice wouldn’t work. Standard Signal should now work without GCM and voice works too (via the new WebRTC code). Battery life will be worse as it can’t use a shared GCM connection for the push notifications, but how much worse depends.
I use Copperhead OS. There is a port of signal called Noise. It works without play services and is available on F-Droid. Its packaged and maintained by Copperhead.
Can’t promise it will work for you, but here is the link:
Noise (Signal-compatible encrypted messaging app) - https://f-droid.org/app/co.copperhead.noise
how does this compare to the TeX family or SILE mentioned here recently?
As bad as TeX is, highly imperative/script-y OCaml code is not an improvement on TeX.
You’re criticism of this code is that it’s imperative? That’s literally all code in your browser, operating system (unless I guess you’re using xmonad), lobste.rs, and most things in general.
Functional code can be great! But there’s also lots of great code that’s not functional.
TeX, though, is known to be particularly bad—I think SILE did a good job of expressing the problems. While idk how patoline compares to SILE, I’d be very surprised if they didn’t manage to improve TeX, at least as far as code quality goes.
That’s not my only criticism, it’s just the most salient one. I’ve written a 1,300 page book with LaTeX, among other things. I know where the rough spots are. Patoline solves none of them.
What are the rough spots that you want to see solved with LaTeX?;
this is awesome.
This is a repost: https://lobste.rs/s/qtipck/typosquatting_programming_language
i thought lobste.rs was deduplicating things already…?
That’s a manual process. :) It’s really meant for when the two conversations are in close temporal proximity, but I’ve merged these ones anyway; we might as well keep discussion together.