Live data from Hacker News

Marginalia Goes Open Source

memex.marginalia.nu

31–40 of 75 posts

Re: Marginalia Goes Open Source

#31

> I feel GitHub has taken an incredibly toxic turn with its emphasis on social features This the first time I've seen this view of GitHub, and I'm struggling to figure out what specifically he's referring to.

I would guess that the chan board members and other asshats raided their projects in the past, because they regularly attack / harass these kind of projects when they're not fully open source. And let's put it this way: the moderation tools at GitHub are a bad joke. Can't even disallow abusive language, so they're 100% ineffective.

"disallow abusive language"? Do you think chan board users are too stupid to know how to bypass an "abusive language" filter?

Re: Marginalia Goes Open Source

#32

> I feel GitHub has taken an incredibly toxic turn with its emphasis on social features This the first time I've seen this view of GitHub, and I'm struggling to figure out what specifically he's referring to.

Sneedacity debacle.

Funny you'd mention this. I installed Audacity a few hours ago and much to my dismay the application informed me upon starting it for the first time that update checks were enabled by default - in other words, Audacity had already called home and I couldn't have done anything to stop it from doing so.

So yes, they deserved the abuse.

Re: Marginalia Goes Open Source

#36
Well done and thank you. Not just for the work, but for the attitude and courage of your convictions that come across clearly in your comments here on HN.

Search is presently a neighbourhood of technology that's fallen into a downtrodden ghetto. Maybe you've sowed some seeds that can grow between the cracks. But I think there are gangs and pushers roaming the streets that would be happy for it remain derelict.

Thinking about the dynamics of open source, with respect to the many different interpretations of search that create tension within such a project: It occurs to me that whenever a somewhat mature project enters the ecosystem a robust strategy is to immediately clone-fork multiple identical copies of a project. This is like a "backup strategy". From there, form several loosely coordinated project groups that can spread risk, share threat intelligence, but each work with different models of crawling, filtering, funding, presentation and so on. Keep the original as an upstream parent. One of the children may survive.

Re: Marginalia Goes Open Source

#37

Thanks for making this open source. What about the index? Are you open sourcing that also?

If I can solve the logistics of publishing that data, then sure. In its most compressed form it's still of order 100 Gb.

The intermediate goal is to have some standardized testing dataset of a couple of hundred megabytes to a gigabyte or so.

Re: Marginalia Goes Open Source

#38

Alright, this seems great. Going to test it in daily use. I am ready to start paying money for search engine. So fed up with google SEO spam.

Probably not going to replace Google, it's at best aiming to pick up the slack where it's struggling. But dunno, maybe down the line it will have grown into a real open source alternative.

Re: Marginalia Goes Open Source

#39
post #32

Earlier quoted context omitted.

Sneedacity debacle.

Funny you'd mention this. I installed Audacity a few hours ago and much to my dismay the application informed me upon starting it for the first time that update checks were enabled by default - in other words, Audacity had already called home and I couldn't have done anything to stop it from doing so. So yes, they deserved the abuse.

First off, nobody deserves any sort of abuse.

Secondly, the Sneedacity incident was abuse targeted at a fork of the Audacity project, not at the original 'hostile takeover' project itself. The fork was intended to remove said abuse you feel is deserving of more abuse.

Re: Marginalia Goes Open Source

#40

Earlier quoted context omitted.

I would guess that the chan board members and other asshats raided their projects in the past, because they regularly attack / harass these kind of projects when they're not fully open source. And let's put it this way: the moderation tools at GitHub are a bad joke. Can't even disallow abusive language, so they're 100% ineffective.

The author of the article was saying that Github was toxic and I personally do not see an issue tracker as a social feature.

Comment threads everywhere (including on commits and lines of code), these comment threads then having emoji reactions, and the inability to disable any of that (same for the pull request feature, which also leads to more comment threads) can get somewhat annoying when a group has decided to target you for arbitrary reasons, and such potential 'needing to see harassment' being deeply embedded in one's code workflow (i.e. in your own repository) can get tedious.

Not everything needs to be turned into an embedded discussion forum.

Post reply on HN