The Okopipi Project is chartered to create an anti-spam opt-out tool which will operate in a completely P2P and open-sourced manner. We are looking for interested individuals to get involved in the project in whatever capacity possible.

Get Involved

There are several ways to get involved in the Okopipi project. The recommended methods are:

Revamp

We are currently working on revamping the project bear with us. Like I said before I am in talks with a member of the apache group and he has agreed to join our team and will become our lead developer. We have discussed the latest paper and will be making improvements to it soon. We are still in need of developers to help us create a Proof of Concept program.

We are looking at renaming the project during this revamp due to the fact we need control to moderate the group and manage the website and most of the people who had control are long gone. Please let us know what you think and any ideas. developers please email me at c130commnav (at) gmail.com

spam with PHP

I recently got this information from a security friend of mine. Spammers php to send spam, this means they can send spam from any php enabled webhost they have access. Keep and eye on those webservers.
posted below is the code

!DO NOT RUN ON YOUR WEBSERVER!
http://digitalparanoid.com/~matt/voxx.phps

Digg Me

Update

Here is a bit of an update on what is going on with the okopipi project.

[RANT]
First off I want to say, you people complain way to much. You act like it is your God given right to have this project developed for you. Stop posting things that are not productive, stop posting things you don't have a clue about. READ ALL the forums instead of posting about somthing that is already covered. If you don't want to help develope then stop complaing that code isn't being written, if you don't wanna volunteer to be a leader in the project, stop whining about the leadership. The fact that this project is completely distributed makes it insainly complicated, WE ARE WORKING ON IT. STOP COMPLAINING!

Blood still flows

Recently I got a couple emails concerning Okopipi, I am rather surpised, after I posted about not being able to work on the project anymore I monitored the forums and such, and nothing...I thought the project would die and that was that. Now I see it has started to become active in the last couple months which is good to hear. I have a bit more time these days, but with a baby and deployment on the way that time will soon be cut short. If anyone can get nathan off his ass I have a server we can use for free so he can stop paying this hosting company. Maybe there is hope after all.

Here is the deal

Alright here is a bit of an update, not much has been done. I have been busy with stuff and havnt really had time for this project. I have talked to several developers whom are very intrested in the project. I think right now we just need to start coding. If you need any information please contact me. All coders feel free to start working on a proof of concept program. If you need any tools let me know and Ill hook you up. It would be nice if you either wrote a theory of operation paper or edited mine and posted it so others know what you are doing. Basicly this project is up for grabs to who ever wants to do it.

Okopipi Project Meeting

We are holding an official project meeting, anyone interested may
attend it will be focusing on the development of okopipi, so developers/programmers are encouraged to attend. The meeting will be Aug 19th at 1900 (7:00 PM) GMT on our IRC channel #okopipi on undernet. for questions please contact Journeyman

New Okopipi design paper: First draft

Many of the steering-committee has been inactive for some time, so after discussing with the remaining committee I was given permission to take charge and start working on production of the Okopipi project. After some research and working with Kwinter we have come up with what we feel will be the best structure for the Okopipi network. This paper explains how everything will work. However we are just 2 people, so please if you find any holes in the paper, or have any suggestions/comments please let us know.

http://svn.okopipi.org/docs/okopipi.pdf

Work will soon begin on the Okopipi project

Some of you may be contacted in the next few weeks to inquire about your skills as posted on the wiki, no one will request you give out any personal info, just a rough experience history and availability. This list will be used to build teams for the project and as a way of determining skill levels.

Please do not exaggerate your skills, if you only have a C+ 101 class say so. If you can only devote one hour on the third Friday of every month say so. This is not the project to "figure something out" for the first time. At first the tasks will be low priority/security items so that we can build an understanding of everyone's skill and participation level.

If anyone doupts the authenticity of the request you are free to contact me with the Name/E-mail of the person who contacted you.

Also this is a reminder to update and detail your skills as listed on the Okopipi Wiki and insure there is the correct contact E-mail address listed for you.

Official Meeting Announcement

On Saturday June 10th at 10pm GMT the Okopipi Steering Committee will be holding a public meeting to answer your questions. The topic will be Project Management and Structure.

The meeting will be held on the Undernet IRC Network in the #Okopipi room. If you do not have an IRC client you can follow the link to the Java Client here. This will be a moderated meeting and you will have to submit your questions by Private Message to one of the moderators to ask it. Please be patient as a lot of people are expected to attend and it may take some time before your question is asked.

Syndicate content