Otherwise painfully high number of failure points are true in the place I'm working, so a good article to show the management on the next scrum meeting (some point in the next two months) :)
I have a bookmarklet, which I've shared here: http://codepen.io/anon/pen/wKpewj (there are lots if you search bookmarklet + {something}). It makes the text 1em, not bold/thin, black on tan.
Something a bit better could preserve headings, bold words etc.
Firefox's Reader Mode sometimes works, although not on this site.
Yes, you can use plug-ins like Stylish. It works well for tweaking sites you read regularly, HN say, though personally I find it too much messing around for a site I'm just visiting quickly. I'm more likely to just open the developer tools in whichever browser I'm using and look for rules that set a tiny font-size, a font-weight of 300, a faded color, etc. Often just disabling a couple of those will make a page dramatically easier to read, so I do recommend spending five or ten minutes figuring out how it works in your preferred browser. Even then, I sometimes have to admit defeat. I hate the idea of criticising style rather than substance, but with a site as awful as this one you can spend several minutes trying to make it comfortable to read and still fail.
I see a bunch of lame commits like changing logos and names and no actual work on mitro -- not sure how encouraging that is, since you've already jumped at changing the name and making a company around it.
Perhaps the original app was feature complete and not a lot of work needed to be done on it? It's based on a third party password management service that open sourced its code before shuttering, so this would naturally be step one in relaunching something based on that code.
I'm one of the people running passopolis. We think that Mitro was already pretty good but we've fixed several bugs, packaged it for the Chrome store, made sure the server runs reliably etc. As the FAQ explains we changed the name to avoid confusion when Googling.
We're also not building a company around it, we've absorbed the work of keeping it running as our agency (wearewizards.io).
If we start charging it's going to be for some actually new feature, not for the current product.
To be clear this libertarianism has nothing to do with libertarianism as it's called in the USA, which essentially is an extreme protector of individual property rights.
I'm mainly developing PHP applications (Magento, Symfony) And I found Linux much easier. Back in 2000 (ish), when I switched to Linux the biggest confusion was the different format of configuration files and scripts. In Windows, I get used to .ini files and .bat batch scripts. When I switched to Linux (well, it was more like a slow process) I was confused about this. Fetchmail config format, the apt sources tree format (which seemed to be an .ini) and all the config files in /etc was all different. I finally managed to get my emails fetched and sorted to different folders based on topic and sender, using Fetchmail, then I was happy to read them in Mutt. The UI looked terrible (well, it was text after all) so I tried Balsa and used it for years, then Sylpheed, Claws Mail, still backed with Fetchmail. I can imagine that the different GUI libraries would confusing others, but I always managed to sort my installation to use only one. If I had KDE, I installed only KDE or at least Qt programs. If I had GNOME, then so that it. Nowadays, I use AwesomeWM mainly with 3 or 4 software only, on 3 screens: the first screen is the terminal with tmux, the second (middle) is the browser, Thunderbird, the third is Sublime, so I don't get nervous about installing different libraries.
With all of these, Linux felt better than Windows and it's openness and community support encouraged me to discover more and more. Back in those days I really tried every programming language I could: Java, Ruby, C, C++ and I had no confusion learning and using these on Linux. I was only confused when sometimes I had to switch back to Windows. The lack of documentation, missing libraries, unpredictable crashes on software upgrades (which came from different sources, absolutely without automation, manually running setup.exe's) and different UX, unsought taskbar icons really annoyed me. Now if I sit in front of a Windows PC, I feel it's just an useless gadget.
Linux was the cause I became a software developer.
I have only experience with one IDE, which was Netbeans. I used it mostly for developing Rails applications and I found this was the only IDE which does not get in my way. I just can't get used to PHPStorm today and I found Eclipse too slow, so I'm using Sublime as my primary editor now. Before it was Geany, gEdit or just Vim. I was never able to learn Emacs, but probably it's my fault :)
There's a comment there indicating that FF has done the same in the past with an H.264 blob.
The conspiracist in me wonders why both these major browsers have downloaded and maybe executed binary blobs. Is it purely a convenience feature in the browser? Is it a secret order? That last question would have been silly a decade ago but we all know it's entirely possible now.
the open h.264 blob thing is annoying, but it's supposed to be a reproducible build of open source software.
The reason why there's a blob is because for that binary, Cisco pays the patent licenses.
So you can verify the source for any issues, verify whether it matches the binary, and work around MPEG-LA licensing at the same time (there are caps, and Cisco seems to have calculated that even when running into them, they're still better off with having webrtc support h.264 everywhere).
Wasn't Firefox recently called out for including proprietary integration from Pocket and Hello on their new versions by default which cannot be removed but only disabled? [1]
I wonder if I should just switch back to IE6 that has no microphone and webcam support, but then there is ActiveX! :(
Can you please cite where you read that proprietary blobs are used? IIRC the Pocket client is open-source, and so is the Hello client (it's basically a webapp that uses WebRTC)
You maybe right, that was bad wording on my side, thanks and corrected. I meant to write "Proprietary Integration", since it is only and only compatible with its respective companies/applications.
The client side code for Pocket integration is open source, so you can look at it if you'd like. You can disable it just by removing the Pocket icon from the toolbar. Plus, as Firefox uses lazy loading, once the Pocket icon is removed, the integration code will never be run.
Hello is just a thin wrapper around WebRTC (an open protocol)
Pocket is just a button that does a couple of AJAX calls to the Pocket site.
Both do have closed source code online, but when you click them it's pretty obvious that they are talking to some online service which may or may not snoop. You even have this "danger" when using Sync in any browser. In all these cases it's very clear what's going on.
When you use Pocket you know that the URL of the page you were visiting was sent to some service. When you use Hello you know that some routing service might be able to snoop on your call (I believe there's some encryption here though, but I'm not sure). When you use Sync you know that you're sending data to the server.
When you enable "Ok Google" detection in an open source software one would expect that the "Ok Google" detection is done locally in open source, verifiable code, and only after this detection is triggered, will sound be sent to the server. If this blob was instead some open source code, one would be able to verify that sound is only sent to the server when it is expected. But now that it's a blob, you don't have this guarantee. It could theoretically send periodic sound snippets to the server without you noticing, since it's listening on the microphone all the time.
That's the difference. Firefox's proprietary integration has verifiable triggers. It won't talk to a proprietary service unless you ask it to, and when it does you can verify what data it is sending.
On the other hand, this blob has no verifiable triggers. Yes, it is disabled by default (verifiably, apparently), but when enabled the data it collects and sends is not verifiable.
(Firefox also does have some blobs -- one for H.264, but the code behind it is open source, the blob is distributed for licensing reasons, and one for EME, but the EME blob is downloaded only with a confirmation which informs the user what is going on)
Black women are unapproachable. Not sure why is that. Are white males not attractive in black women eyes?
The effect is the reverse with white women as they tend to flirt with black man, hence the interracial children are mostly from black males and white females. I don't have a study to support this, but I do have personal experience.
Counterpoint: OK Cupid ratings appear to show that black men suffer rather less in the attractiveness stakes vs black women. http://blog.okcupid.com/index.php/race-attraction-2009-2014/ . If you see more black men + white women combos, those statistics would seem to suggest that it's because (for whatever reason) white men aren't as interested in black women as white women are in black men.
There are a lot of reasons for this, perhaps even more important reasons, but yes, black women are unapprochable as a white man. While other people interpret my normal social awkwardness/aloofness as just what it is, black women tend to take offense and think it's racist. There's nothing I can do to change that aspect of myself. I don't know why this doesn't happen with black men, it just doesn't really seem to, though.
However, I am concerned that my sample size may be too small to draw any valid conclusions.
Where are you approaching them? Have you even bothered trying, say, bars in black neighborhoods (I have) instead of palace where they're in the minority and in the defensive? Think about that for a second and ask yourself why not.
http://www.reddit.com/r/blackladies might provide a perspective on that. The general "feel" of this subreddit is that they're concerned about racism in an interracial date. The whole subreddit comes across as very anti-white.
Otherwise painfully high number of failure points are true in the place I'm working, so a good article to show the management on the next scrum meeting (some point in the next two months) :)