Slashdot turned 20 this month, which is ancient in internet years. How far have we come?
Also, we've set up a page to coordinate user meet-ups around the world to celebrate. Read on for the full 20-year history of Slashdot.
Slashvertisement: Here is SourceForge's message to CodePlex devs.
To his credit, Reichl notes that he'd like to move to encryption as soon as he believes it's possible. You can also verify that you're getting a signed download, if you're worried. However, it's still contradictory to develop a security-centric app and decide that security should take a back seat.
An update on the site says the software's version information file is now digitally signed, adding that KeePass "neither downloads nor installs any new version automatically. Users have to do this manually... users should check whether the file is digitally signed... HTTPS cannot prevent a compromise of the download server; checking the digital signature does."
I wanted to use this opportunity to get a discussion going on how we can improve Slashdot moving forward. I am not talking about a full re-design that will detract from the original spirit of Slashdot, but rather: user experience, bug fixes, and feature improvements that are requested from actual /. users. We appreciated many of your suggestions in the story announcing the sale, and I have taken note of those suggestions. This story will serve as a more master list for feature requests and improvement suggestions.
We welcome any and all suggestions. Some ideas mentioned in the sale story were, in no particular order: Unicode support, direct messaging, increased cap on comment scores, put more weight on firehose voting to determine which stories make the front page, reduced time required between comments, and many more. We'd love a chance to discuss these suggestions and feature improvements and pros and cons here before we bring them back to our team for implementation.
I have every intention of continuing to work on it. I enjoyed the learning opportunity, and I've already identified a number of things I want to improve upon, but I recognize that even as crude as my code is, if it solved my issue it might help others too.
Do I just put it on Github or SourceForge and hope that someone else will have that magic formula of my use case and skill level (because someone more talented would probably make their own code easily enough, while someone less talented may not realize how doable the solution can be)? Do I try to find an existing project and see if I can shoe-horn my efforts in somewhere? Do I keep it to myself until some unspecified point in time that I realize it's right for sharing? Read on for further background information on this question.
At $1.49/month or $10/year, this might be enough to drive some people who otherwise would not to check out some of the free, open-source games out there; PySolitaire is one of many in this incomplete list.