Mozilla in 2018 brings in 10 times as much revenue as it did in 2008, but is 1/10th as effective and doing 1/10th as much good work.
0307ea7a0f89f4c893e89e6a4992b82b1a812c22e9510410f9e4279a52368d04
2,674 karma · joined September 22, 2009
Mozilla in 2018 brings in 10 times as much revenue as it did in 2008, but is 1/10th as effective and doing 1/10th as much good work.
0307ea7a0f89f4c893e89e6a4992b82b1a812c22e9510410f9e4279a52368d04
Not doable, because despite declaring (at the time that Mozilla merged with them) that Pocket would become open source, that never happened. To put it another way, we're a month away from the one year anniversary of the date that Mozilla decided to begin operating a closed source, for-profit service.
PS: This is your periodic reminder that the thing you're probably thinking of when you hear the name "Mozilla" actually went away years ago and doesn't exist anymore.[1] It's got the same name and looks kind of the same, like an alien in a human suit, but it's silly to give this any more weight than it deserves. If it helps, think of Mozilla as having undergone a reverse takeover. (It's more complicated than that, and most of it actually predates the Pocket stuff, but if it helps, it helps.)
For anyone who's similarly curious or confused, LWN published a pretty great overview last month—their "Federation in social networks" article:
The way its written, I first took the mention of finding this "during the analysis of a prominent antivirus product" to mean that you were reverse engineering some AV thing and found that it was scanning for this vulnerability (i.e., to protect against bad archives). After a second read, it seems like maybe not, and that the AV itself re-used parts of 7-zip for its own implementation and was therefore vulnerable itself. Still not sure, though.
The way the stylesheet makes the "rendered" form (especially section headings) resemble markdown source is pretty neat.
So to get a general idea of what sort of setup is expected in order to run a gitbucket instance, if you're running one, what are the relevant details?
This doesn't mean there aren't other defects in the apparatus where C exploits thrive. It's just that (if you adhere to the langsec school of thought) you are required to confront the conclusion that it's been pinned on the wrong thing.
EDIT: There's also this[1] alignment issue in the settings wrt to "City of residence" where the text field is off by ~1 pixel.
EDIT2: On the page where I uploaded my SSH key[2], it says updates occur after a small delay. The linked page in the docs says that this delay is ~30 minutes. In any case, I was able to begin using SSH immediately. If that info is no longer fresh, I suggest removing it, especially since it's probably a turnoff for a lot of users.
EDIT3: When I run sf-help --web at the shell, it prints an error:
[colbyrussell@shell-22009 ~]$ sf-help --web
Use of uninitialized value $user in concatenation (.) or string at /usr/bin/sf-help line 96
1. https://imgur.com/a/2d0lr> Is that like, showing the commits you make on your profile?
Yes.
> Having a page that shows what you've worked on at all?
Yes.
> This seems like good ways to be difficult to work with in open source projects
First, open source doesn't start and end with GitHub.
Second, I prefer not to publish anything to Facebook or Twitter feeds, either. That's a position that folks seem to find palatable. (In fact, it's one that programmers appear to be disproportionately sympathetic to.) I don't see why it shouldn't remain so if the subject of the conversation is GitHub.
> for zero benefit
Opting out of the same kinds of personal broadcasting on GitHub isn't "zero benefit" to me. And if it is zero-benefit, it means the service linked here is zero-value. I feel differently. We don't have to agree.
Side note: the Git project is enforcing the Git trademark now.[2] If you want to use "Git" for your branding, you'll need to get approval.
1. https://www.colbyrussell.com/2016/02/13/keeping-a-low-profil...
2. https://public-inbox.org/git/20170202022655.2jwvudhvo4hmueaw...
Beaker is interesting because it's enabling things that aren't possible on the HTTP web, and (again) focusing on making it stupid easy for non-tech people do things. Meanwhile, the major browser vendors' idea of forward motion amounts to working on things that web developers can use to impress other web developers and maintaining existing barriers to entry.
http://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_...
https://arstechnica.com/information-technology/2013/08/confu...
Also: unless you've okayed the name with the Git folks, you're going to need to change the name. Git is trademarked, and they are no longer allowing just anyone to use the mark without first seeking permission. (GitHub, GitLab, and others have been grandfathered in.)
See https://public-inbox.org/git/20170202022655.2jwvudhvo4hmueaw...
Last year, when SVP of Engineering at Google left for Uber, I suggested[1] here on HN that Uber getting into mapping (for exactly the reasons in the article) with OSM would be mutually beneficial (in the same way as outlined in another comment from today[2]). It didn't get a warm response. (IIRC, at first it was even downvoted into the gray.)
That's completely at odds with what Kay actually advocates for. His position is strongly aligned with the "mechanism, not policy" philosophy. That is, what he advocates for is less of what you want, not more. This is apparent from that Dr Dobbs interview, his work with VPRI, back to his OOPSLA speech in 1997. To wit:
> HTML on the Internet has gone back to the dark ages, because it presupposes that there should be a browser that should understand its formats. [...] You don't need a browser if you followed what this staff sergeant in the Air Force knew how to do in 1961. Just read it in, it should travel with all the things that it needs, and you don't need anything more complex than something like X Windows.
Kay has always sat on the diametrically opposite site of the table as those favoring the Principle of Least Power—one of the most underappreciated tenets of computing. Tim Berners-Lee called it out in Axioms of Web Architecture:
> At the other end of the scale is the weather information portrayed by the cunning Java applet. While this might allow a very cool user interface, it cannot be analyzed at all. The search engine finding the page will have no idea of what the data is or what it is about. The only way to find out what a Java applet means is to set it running in front of a person.
You can get a better view of what a world that more closely adhered to Kay's vision would look like in Stanislav's (an adherent's) post, "No Formats, No Wars": http://www.loper-os.org/?p=309
There's a lot of power in branding, apparently. People keep saying things like, "Mozilla is a good company at heart", and I'm at a loss. Mozilla 2017 is nothing like the Mozilla that existed when the Foundation was established, or when the Mozilla Manifesto was adopted. Tons of key people left in a few different waves: first when Google pulled them off the project to go build Chrome, and then lots more who trickled out over the years during and after the Kovacs/FirefoxOS era. What remains is (a derivative of) the codebase + the name "Mozilla" + and, like, Mitchell. But that's it. Keep calling it the same thing, though, and somehow folks act like we're talking about the same thing.
Mozilla imploded—or rather, got Netscapified—years ago. To believe that Mozilla or Firefox is your old friend who's still helping you fight the good fight is incredibly naive and can only come from someone who hasn't actually been paying attention and is easily fooled by (trivially contradicted) surface-level details (like a name). I mean, it's not even like some philosophically tricky ship-of-Theseus problem. Mozilla is dead, people, and this isn't news.
I had hope that GitLab would take the opportunity to fix most of the problems GitHub introduced (or at least a few), but they seem to be interested in just copying the mistakes and chasing the market segment made up of people who's only criteria begins and ends with like GitHub, but on-prem.
It doesn't even have to go away. (And on that note, I'm bummed that the conclusion in the article is to do that, especially because everytime this comes up, there's an uproar.) But, jeez. Just tuck it away so futzing with it is an opt-in decision for the 5% of the time that you need to make sure you aren't committing all of your changes. (And on note #2, if a person is doing partially staged changes more often than that, my question is why? What kind of chaotic, stream-of-consciousness style of development leads to that, and is it even producing good results? It doesn't take especially careful planning to not end up in the scenarios where partially committed changes is the answer.)
No, that is what I'm suggesting. Your comment reads as a quote. After reading it, I went to the linked page and looked around for the context. Turns out, there was no context for that quote, because it's not a quote, because those words aren't actually in the original text.