SourceForge BlockThis Initiative Update

Last week, we launched an initiative aimed at removing misleading ads that display a download button without disclosing the name of the product and we want to update you on how this program is progressing.

A task force of people working in the AdOps, Community and Product departments reviews daily the notices sent in from the community, in addition to the work we do on our own.  We process requests by following these steps:

1. Reviewing the advertisement to confirm they are misleading;
2. Identifying the advertising network partner/s displaying those ads;
3. Removing those ads; and
4. Proactively reviewing all additional partner networks to find similar ads.

In a week, we received a handful of community notifications and we found 90% of them legitimate. Thank you!  We took action accordingly, eventually communicating back our findings and actions.  This has resulted in SourceForge blocking +20% of misleading ads, with more work ongoing.

This is just the beginning and we are fully commitment to improving our site and removing misleading ads.  We continue to ask for your patience and assistance, as this is a continuous process.  If you see what you think is a confusing ad, please send a screenshot of the ad itself and the URL of the site where the ad leads. Send to: blockthis@sourceforge.net.

November 2013 Project of the Month, PasswordSafe

I’ve been a long-time fan of PasswordSafe because it has a single function; password security. We’ve been hearing a lot about security of late, so it’s also a topical matter. Here is my interview with Rony Shapiro who is the admin for this very useful project:

d: Tell me about the PasswordSafe project please; what made you start this, and has your original vision been achieved?

PasswordSafe started off as a free closed-source utility from Bruce Schneier’s consulting firm.  Around 2001, Bruce decided to make the code open source, and chose a volunteer to set it up on SourceForge. Unfortunately, that person got caught up in the dotcom bust, and more or less abandoned the project.

I really wanted to work on this program to scratch my own itch. Specifically, (1) to support grouping entries into topics (such as banks, e-commerce, etc.) and to add a search function (e.g., to look for the entry that contains the word “robot”). Once I put out a version with these features, people started contributing ideas and code. The rest, as they say, is history.

Re “vision”: I dunno about that. It’s a large word. I hope to think that fewer people have had their accounts hacked because of PasswordSafe, but of course there’s no way to test this.

d: Who can benefit the most from PasswordSafe? Have you seen the current climate around personal privacy impact your project?

Any person who has more than one password to protect can benefit from PasswordSafe. Certainly the recent push of privacy-related issues to the headlines has made people more aware of this.

d: – What’s the best way to get the most out of using PasswordSafe?

The best way to get the most out of PasswordSafe is through liberal use of the Generate Password button: Create a separate entry for each site you use, and generate a random password for each. This ensures that (1) even if a single site is compromised, the attacker cannot use the password he’s recovered to access any of your other accounts, and (2) that any dictionary-based attack will fail, or knowing the names of your family members, pets, etc. will not help the attacker.

Another good idea is to use the Notes field to remember the fictitious answers you created for all those silly “security questions” (that should really be called insecurity questions, because they allow an attacker who found out a bit about you to reset your password…)

d: Why did you choose the Artistic 2.0 license? 

That was the license chosen by Bruce Schneier when he released the project.

d: Did you ever regret choosing this specific license?

I’ve had no problems at all with it.

d: – If you had the chance, what other license would you select and why?

Don’t think I’d choose differently if I had to start over.

d: What was the first big thing that happened for your project? What helped make that happen? What was the net result for that event?

Getting contributions from other people made the project much much better than anything I could have made from it by myself. I guess the first one that made me appreciate this was the autotype feature, added back in 2004. Unfortunately, I don’t have notes on who added it.

d: What is the next big thing for PasswordSafe?

I’ve started working an a new database format that should have some nice features.

d: – How long do you think that will take?

Probably a few months to a year’s worth of evenings and weekends  until something usable will come out of this.

d: If you had it to do over again, what would you do differently for PasswordSafe?

I’d probably take a go at working on it full-time and making a living off it (while keeping it open source, of course), instead of working on it strictly as a hobby.

d: – Any reason you can’t do that now?

I’ve decided to leave that as something to look forward to for my retirement :-)

d: Is there anything else I should know?

Of course: My deep gratitude to everyone who’s contributed to the project over the years, be it via code, translations, bug reports, suggestions, or plain old fashion donations. Special thanks to DK, who’s become a personal friend and companion as well as a coder, critic, and sounding board for my crazier ideas. And of course thanks to SourceForge, for years of hosting.

d: Excellent Rony. Thank you for your contributions to the Open Source community for all that you do.

Advertising, Bundling, Community and Criticism

Over the last days, we heard a number of concerns around how our business practices affect the community sentiment. A few concerns were expressed by several developers, included the GIMP community, about confusing ads on SourceForge pages. Along with that, we also heard complaints about the DevShare program. We want you to be assured that we are always listening to you, learning from you, and taking action on your feedback.

1. About the Confusing Ads

We work with several different Ad Network partners like Google to show ads on our site, and from time to time, a few confusing ads show up. Just like all of you, we do not like these ads, and last month, we asked our Ad Network partners to remove over 200 deceptive ads; however, it’s an ongoing process and we need your help.

In order to eliminate these sometimes misleading ads from SourceForge pages, we’re asking you to drop us an email at blockthis@sourceforge.net providing the screenshot and, more importantly, the full link to the confusing ads [to copy it right click on the link, and choose "Copy Link Location" in FireFox; "Copy Shortcut" in Internet Explorer; "Copy Link" in Safari and "Copy Link Address" in Chrome]. We will make sure to review all such requests, and if we agree with you, take immediate action. Please help us to make SourceForge a better place. Your input is material to help mitigate this issue.

2. About Bundling Open Source with Additional Offers

In July 2013, we launched a pilot version of an opt-in revenue-sharing program called DevShare. DevShare is a partnership program offered to SourceForge developers to turn downloads into a source of revenue for them, by bundling their applications with third parties’ offers. This revenue will help these projects grow, help the developers keep contributing to the Open Source community, and help us keep offering free hosting, distribution, and other services.

Let’s start by providing some context around this issue first.

We started the DevShare program for two reasons:

  1. Some projects were already using the SourceForge infrastructure to deliver bundled offers to monetize their downloads, and most of them were complaining about the lack of control on the quality of the offers and user experience. In addition, many other open source projects expressed interest in monetizing their downloads by bundling relevant offers, but the lack of control with Installer Partners was a key concern for them.
  2. SourceForge also makes a small amount of revenue from this program to continue offer free hosting, distribution, support and ultimately to keep enhancing Allura, it’s fully open source platform now in incubation at Apache.

Therefore, we evaluated a few Installer Partners to help us address end-users’ complaints related to one or more of the following reasons:

a) opaque installation flows providing little or no choice about secondary offering installations;

b) undocumented and difficult to uninstall procedures for those secondary offerings;

c) secondary offerings that are not always safe, trusted and secure applications.

We addressed points a) to c), and our approach was highly appreciated by eminent members of different open source communities.

What DevShare Means to You

End-users are provided with a clear and transparent installer behavior, all programs are malware-free and clearly described. All uninstall procedures are extensively tested, so that if end-users install it by mistake they can easily remove it.

Developers aren’t just compensated in money, but they are in full control of both the installer behavior and what sort of secondary offerings will be presented to their users.

Where are We and Where are We Going

Currently in the Pilot phase, we only have 3 projects participating in the DevShare program all of which explicitly opted-in. This represents 3 out of 300,000+ projects in our entire catalog. This is a 100% opt-in program for the developer, and we want to reassure you that we will NEVER bundle offers with any project without the developers consent.

The DevShare program has been designed to be fully transparent. The installation flow has no deceptive steps, all offers are fully disclosed, and the clear option to completely decline the offer is always available. All uninstallation procedures are exhaustively documented, and all third party offers go through a comprehensive compliance process to make sure they are virus and malware free.

Having said that, we believe we should do more to make sure all our stakeholders are pleased with the program and how it works.

In the near future, we’ll share a blueprint of how we believe this program can be improved, and we’ll ask the community for feedback. We will not be accepting any new projects into this pilot until the community has vetted possible changes and improvements to the program.

In Closing

You are welcome to join the conversation at the DevShare forum on SourceForge, your opinion rules.

SourceForge site maintenance window on 2013-11-07

A maintenance window has been scheduled for 13:00-14:00 UTC 2013-11-07. A short period of SourceForge site downtime is expected during that time.

Regards,
Chris Tsai, SourceForge.net Support

API Improvements: Bearer Tokens & Project Admin

Today we have launched some improvements to the API to allow you to more easily have programmatic access to your project data.  Bearer tokens are an extension to the existing OAuth negotiation that makes it vastly easier for your program to access the API.  Additionally, the API can now be used with the project data export launched in September to easily make regular backups of your project’s data, as well as now being able to install new tools for a project programmatically.

Bearer Tokens

token

On the OAuth tab under your Account settings, you can now generate a bearer token for any registered OAuth application.  These tokens are pre-negotiated, so your application doesn’t need to deal with the multi-step OAuth verification process and can just include the token in the access_token parameter to any HTTPS GET or POST request to the API.  Note: because these tokens grant all of the access rights of your account, you should protect them carefully and revoke any that you are no longer using.  More information on using bearer tokens, including example code, is available on the wiki.

Project Admin API

The project data export feature can now be accessed via the API, so you can schedule a project export, check the export’s status, and download the exported data, all programmatically.  There is even a drop-in script ready to do all of these steps for you.

Additionally, you can now install new tools, such as new repositories or ticket trackers, into your project via the API.  More information is available on the wiki.