From: xor <xor@freenetproject.org>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
Date: Wed, 10 Jun 2015 10:25:12 +0200 [thread overview]
Message-ID: <1943127.DBnVxmfOIh@1337h4x0r> (raw)
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
http://www.howtogeek.com/218764/warning-don%E2%80%99t-download-software-from-sourceforge-if-you-can-help-it/
TL;DR:
> In 2013, GIMP’s developers pulled the GIMP Windows downloads from
> SourceForge. SourceForge was full of misleading advertisements
> masquerading as “Download” buttons — something that’s a problem all over
> the web.
[...]
> In 2015, SourceForge pushed back. Considering the old GIMP account on
> SourceForge “abandoned,” they took control over it, locking out the
> original maintainer. They then put GIMP downloads back up on SourceForge,
> wrapped in SourceForge’s own junkware-filled installer.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2015-06-10 9:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 8:25 xor [this message]
2015-06-10 9:35 ` [Bitcoin-development] Is SourceForge still trustworthy enough to host this list? Wladimir J. van der Laan
2015-06-10 16:46 ` Andy Schroder
2015-06-10 18:02 ` Troy Benjegerdes
2015-06-10 18:41 ` Andy Schroder
[not found] ` <DB12E925-11C6-4A82-BC81-FB3DA26BC5B3@newcastle.ac.uk>
[not found] ` <20150610185810.GQ27932@nl.grid.coop>
[not found] ` <DB5PR07MB091974E06974EA88136F60C2B5BD0@DB5PR07MB0919.eurprd07.prod.outlook.com>
2015-06-11 1:46 ` Troy Benjegerdes
2015-06-10 18:28 ` Ivan Brightly
2015-06-10 18:47 ` Troy Benjegerdes
2015-06-10 19:13 ` Ivan Brightly
2015-06-10 18:36 ` s7r
2015-06-10 18:59 ` Andy Schroder
2015-06-10 19:03 ` Peter Todd
2015-06-10 19:12 ` Andy Schroder
2015-06-10 19:20 ` Peter Todd
2015-06-10 19:36 ` Andy Schroder
2015-06-10 19:43 ` Peter Todd
2015-06-10 20:03 ` Andy Schroder
2015-06-10 19:54 ` Jeff Garzik
2015-06-11 9:27 ` Wladimir J. van der Laan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1943127.DBnVxmfOIh@1337h4x0r \
--to=xor@freenetproject.org \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox