sethish

They did that first: http://jacobappelbaum.net/ <-- 10 collected accounts from people that Jake has sexually assaulted.

Did you consider reading the helpful FAQ on their website http://jacobappelbaum.net/? They explain in detail why they aren't seeking prosecution.

Instead of discussing the issues that prevent women from joining the tech community, you want blogposts about how to get women into tech. Is that accurate?

Did you miss the link to http://jacobappelbaum.net/ where the rest of the testimonies are collected? Or read any of the other blogposts on the subject like this one? https://blog.patternsinthevoid.net/the-forest-for-the-trees....

It isn't a single 'open blog'. Alison is a widely respected member of the infosec, internet freedom and librarian communities.

The outright denials in this thread are one of the many reasons why people don't come forward immediately.

Tell me, how would you prefer victims to speak?

I hope you don't program on a back monitor. The display turns down the brightness when you're looking at dark things, and up when you're looking at bright things. The only way to disable it is to install windows...

Aptitude is installed by default on Debian Jessie.

> in fact I think the very idea of Django and similar frameworks should go away. I find templates cumbersome, hard to read and non-pythonic.

This is incredibly dismissive and hardly a well functioning argument. I don't like to edit html templates, therefor web frameworks shouldn't exist.

The anti-proprietary-js movement seems to be coming from RMS himself (given his complaints to con organizers). And he hasn't used a browser other than emacs in... ever?

This is the most compelling reason I've seen to finally drop python2.

Heh. The list I could make for you my friend. For one, there is a dynamic contrast 'feature' that can't be disabled from linux. When you look at dark screens, it will decrease the brightness of the backlight. The goal here was when looking at light screens it increases the brightness to make it look like it has great contrast. Suspend and powersaving is an issue (see MJG59's blogpost about the chipset), almost unworkable if you don't get powersaving sata working first. Thunderbolt support is non-existent. 1/3 of the time I hot unplug a displayport monitor my machine freezes. You can't disable the keyboard backlight, it turns back on whenever you press a key. Oh, and no one on the sputnik team has tested the displaylink video out adapter they sell with the device. Oh, and my alt key popped off 31 days after getting the machine.

> security track record as good as Google Play or iTunes

Do they have great security track records? I know a lot of the integrations like games into their systems are terribly insecure.

That depends on your git.push settings. I have it set to current, which means `git push` pushes the current branch to only an origin branch of the same name.

I'm disappointed that a respected technology journalist can misapply the term open source so completely. If he actually meant that java can be decompiled and therefor is 'open source' then why the hell did he capitalize the phrase?

If you add a trendline for the term 'Software' you will see that it has been steadily decreasing at the same rate as 'open source'.

Can someone explain to me why this only happens on linux?

I would love to work on this. It would require getting a dump of all of their data, or scraping it from them however.

Wait, we all realize these are grabbing the favicons for the bookmarks right? This list of .iso's reads to me like a list of default bookmarks.

Unfortunately, Tmux still doesn't support true-color, which nvim added recently. I was hoping for it in the 2.0 release.

hacker.tattoo and hacker.ink mistakeswerema.de

If you're interested, I'd love to combine forces. Eric (the author of the newsletter) joined up with GITenberg. Github gives a LOT of surface area for additional contributors. And with our library initiative, we have the opportunity to distribute our ebooks directly to libraries. Meaning your standard ebooks can be the standard ebooks for libraries.

Absolutely. We need guides about how to use Github to asciidoc-ify books.

It looks like asciidoc has a stable future ahead too. Multiple implementations, adoption by O'Reilly and others, auto-github rendering, pandoc support (to and from formatting).

GITenberg status report. --------------------------------

Seth started GITenberg back in September of 2012. It was pretty much a one person effort. Through this mailing list, a few other people started thinking about what it could be. I discovered the project and joined up in March of 2014 when I was exploring similar ideas. The project got some good exposure on Hacker News last August.

### Knight Foundation Grant When I heard about the Knight News Challenge for Libraries, I suggested to Seth that GITenberg might be a good fit. Together with Raymond Yee, Seth and I put together a proposal. We got help from Jenny Lee, Phoebe Espiritu, and Emily Nimsakont.

https://www.newschallenge.org/challenge/libraries/feedback/g...

There were 676 entrants in the News Challenge, and believe it or not, GITenberg was one of 22 entries to receive funding. We've been awarded a $35,000 "Prototype Grant", which will allow us to spend some real development time to start turning the idea into something that really works. More to the point, we have a deadline (in late June!) for demonstrating the GITenberg concept.

Now the work begins.

### Next Steps

Aside from 45,000+ repos on GitHub (a significant achievement by itself) GITenberg has so far been more concept than reality. If you tried to adopt a repo and submitted a pull request, you'll surely be aware that the GITenberg of today is more of a sketch than a working system. To make it a working system, we'll have to assemble a lot of cooperating components. Thankfully most of the components we need exist, and people are working on them. This became very clear at the Hack day sponsored by New York Public Library in January.

So I think it's important to make that sketch more explicit.

### Core Vision

The core vision is that for any text in Project Gutenberg, anyone will be able to fork a repo, commit a change, and GITenberg machinery triggered by the commit will derive ebook files and metadata products. The commit can be submitted as a pull request, and accepted PRs will get fed back into Project Gutenberg. We hope.

At this point, I should comment about Project Gutenberg. To fulfill its mission, Project Gutenberg has to be very conservative in its processes and operations. It doesn't have the resources to engage in speculative projects. So while the Project Gutenberg is enabling the experimentation we're doing, (and happy that we're doing it) we expect that GITenberg will need to prove itself before the PG feedback is a real thing.

One thing that Project Gutenberg has been thinking about for years is the source format for its texts. For a good while, that format was 7 bit ascii text files, and there was a lot of resistance to migrating to anything more "modern". Now, the plain text you get from Project Gutenberg is utf-8. Sort of. The html files are maintained separately, and are not uniform; there's a lot of hand-coding. Changing the source format to RST, XML or TEI has been discussed. The PG ebook files (MOBI and EPUB) are built using a script called ebookmaker which digests the html files. The HTML files are thus the "source" files as far as the ebooks are concerned. It should be possible for us to duplicate this workflow in the GITenberg machinery.

On the metadata side the situation is more obscure, and we're still working to understand it. There's a set of RDF files, there are metadata records associated with each ebook folder.

### Book Formats

We've surveyed the components now available, and we feel that we can also improve on the existing workflow by migrating away from HTML as a source format. At this point, asciidoc appears to be the best fit for a format that can be a source format for the required product files, while at the same time fitting with the established PG text corpus and the Git-based version control. It looks like the best choice for ebook and web formats is the HTMLBook flavor of HTML5. http://oreillymedia.github.io/HTMLBook/ There’s a converter for asciidoc that makes htmlbook files. https://github.com/oreillymedia/asciidoctor-htmlbook and css themes that support htmlbook. We expect that alternate paths into HTMLBook can be developed (or already exist) for LaTeX and TEI source formats. Pandoc has done quite a lot.

Internet Archive seems like the best destination for GITenberg produced ebook files.

NYPL Labs has done some really nice work on generating covers for PG texts, we expect to integrate that work as well.

On the metadata side, we've started looking at YAML as an appropriate serialization for PG-associated metadata. conversion to MARC and other formats should be straightforward in the backend.

### Issues

Github itself has presented us with a set of challenges to address. The large number of repos in the GITenberg organization breaks some Github tools. For example, GitHub for Mac became unstable for me, and some 3rd party integrations would time out when we tried enabling them. We broke our Github pages. So we need to understand this better; Github support has been very responsive. There's a separate organization "gitenberg-dev" https://github.com/gitenberg-dev that we're using to let us easily work on code untill we fully understand how to work with 50,000 repos; at this point, you probably don’t want to be a member of the Gitenberg organization but you might want to join gitenberg-dev, even if you’re not a developer.

The non-programmer usability of Github is another problem. We're going to set up a "github for poets" sandbox to see if this challenge can be addressed.

Despite the Knight grant, and the efforts of some committed volunteers, this is still a very small effort. GITenberg can't succeed without a lot of help, cooperation, and collaboration. I hope everyone on this list will be help us nurture that success.

Here’s something each of us can do to get the ball rolling: Decide on a Gitenberg repo to contribute to. Star it in Github. Then add it to the list of active repos at https://github.com/gitenberg-dev/wiki/blob/master/activerepo... (send a PR or create an issue https://github.com/gitenberg-dev/wiki/issues )

If you’re new to Github, instructions are at https://github.com/gitenberg-dev/wiki/blob/add_how_to/how_to...

There's a huge amount that we don't know, and so much prior work we've yet to absorb but we're really encouraged by all the expressions of support we've received. Thank you all!

Yes. This was discussed at length with the Twitpic founder. He said something to the effect of: "don't worry, I'm working on a deal, trust me. But stop downloading the pics"

I think that Marx had more of an impact. Or the Hite Report, or even the Kinsey Report.

> "here's my code, if you change it send me the changes"

More like: use my code, if you change it and give someone the changed version, you have to give them the source+changes.

This feels like a bait and switch. Saw a free app, installed it, registered, gave it permissions and my location, and only THEN did I find out the the actual feature of the game 'SuperTrip' is a paid feature and requires an account upgrade.

I forked Project Gutenberg to github[0]. I've been doing some some work on newsdiffs[1]. I'm working on a python library for dealing with Library of Congress Subject Headings[2]. And I'm trying to get access to and release hundreds of syllabi collected via universities via FOIA request[3].

[0]: gitenberg.github.io [1]: newsdiffs.org [2]: https://github.com/sethwoodworth/LCC [3]: http://chronicle.com/blogs/ticker/u-of-wisconsin-will-turn-o...

Oh yes. GITenberg is not a replacement for DP in the slightest. New books aren't likely to come out of GITenberg as it currently exists. That is what distributed proofreaders is for.

At some point, I would like to investigate DP tools and see if there is something I could contribute.