There was a minor issue with the Security Certificate now in version 1.0.3 you can download from signed.labs.coop-v1.0.3.tar.gz ~ 5Mb's (Includes API Discovery as well through contextual headers)

Over the last few weeks I have spent around 86 – 97 hours working on a Digital Signature system mainly for Chronolabs but I have decided to open up the code and release the Release Candidate to the public. It allows for a client or business to make a signature for placing signature assignment on legal documents like sales contracts etc online.

I have seen many websites that get you too put your name, initials and a date, but this isn’t correct signing online, it needs to involve a validation system from a third party/peer so with the JSON REST API it allows other websites to accept signatures on your signature repository. It also allows to be paired with other signature repositories for ethical token trust relationships in peer-to-peer relationships on the service. You can also specify a callback so if someone signature becomes ‘unsigned’ then the signature repository will notify you that their signature is current invalid and what documents it is in relationship to.

The best thing about it is that it uses flat files for it configuration and as a storage mechanism uses XML, so there is no over bearing database or co-related physics in the signature it is unilaterally bonded as raw data. If you would like to look at it point your browser to signed.labs.coop.

It covers all the necessary basis of legal binding arrangement and has an IT Security Style Certificate, Signature code or a Serial Number in the XML were you need two of these three things to sign anything online and receive a confirmation validation code from the api. Well i don’t suggest you remove anything thing, but there is no harm if your looking for a binding method of doing online signatures you can expand, if you think of anything interesting I would love to hear about it.

This is the final model ofhttps://signed.labs.coop ~ this is used too generate an online signature for a client to sign online a contract, waiver or legal accreditation.

It will generate an XML file, a signature code as well as a Digital Signature Certificate which two of the three can be used with the JSON REST API to sign a document. It does not use an database as this has intrinsic physical weight into the argument or clause of the signee.

Thanks Michael your mambies are always appreciated it take more than one to tango as you know, well latin salsa anyway!

I think that is a wrap unless you can find anything else, could you publish some news on it based on this article from my sourceforge.net page ::http://forge.labs.coop/mynamesnot/2014/05/fishsms-1-04-final/

The download link is ::http://sourceforge.net/projects/chronolabs/files/XOOPS%202.5/Modules/FishSMS/xoops2.5_fishsms_1.04.zip/download

This should not be updated but will be when 2.6 is close to a formal structure be migrated to XOOPS 2.6 as well

To mamba,

Yeah I decided to take 12 months off to cool my head so I was less abrupt with my responses, you know preparative screens can do that to you my friends. Anyway thanks for always playing tag team for me on the bugs.. This has all those bugs removed.

Download: xoops2.5_fishsms_1.03.zip - 57.9 kB

Thanks

Simon (wishcraft)
http://simonaroberts.com
https://twitter.com/NegativityGear

ZIP Has been patched 08/05/2014 07:10 AEST. This was to fix a couple of minor initial release misnomers like 'receive' spelt wrong, to allow constant to be embedded as String Preferences and a couple of other little issues here and there that I found just reviewing the code a little more.

Any further changes will be a minor version change. So the magic 6 that have already downloaded you will need to do this again.

Thanks

Simon

FishSMS 1.02 RC
Release from the Chronolabs Cooperative

In any paid work I do I try to find at least one module which is genetic and not system specific or contains business rules owned by the website to release as Open Source as per the licensing and ethics of open source and XOOPS. In this example this is a module that works with Cardboard Fish APIs from the UK to allow you to use their APIs and Callbacks as well as Polling systems if you wish to send, receive and operate your site and modules in conjunctions with this affordable SMS Aggregation Service.

This module's Intellectual Property is retained by Chronolabs and myself, and it is through Ringwould Ethical Trust Network that I am developing as a self metering ethical management tools for industries and their providers for John Saunders that made this module possible. It was developed today over around 14 hours. It is also all tested!

Release notes:

FishSMS 1.02 RC is a tool that works with Cardboard Fish's SMS aggregation service in conjunction with your website. It has a plugins system which an example is provided that will allow you to easily make it interact with your custom and standard modules as well as receive SMS's on the site that can be processed by your modules and anything you wish.

This is more or less a complete framework for Cardboard Fish's APIs and will involve some level of intermediate programming to implement in your site, standalone without this it will not do much, but all the hard work has been done for your pleasure.

There is a function sendSMS() that is accessible throughout the code base of your modules and all areas of XOOPS pretty much after you install it, here is the code comment on how to call it:



Changelog.txt:
[size=xx-small]---------------------------------------------------------------
FishSMS - SMS Module - Version 1.02 RC
---------------------------------------------------------------
* tested all components seems to be working 100%[/size]

Links & Downloads:

• Bug Tickets: Sourceforge.net tickets
• Feature Requests: Sourceforge.net discussions
• Download: xoops2.5_fishsms_1.02.zip - 57.8 kB

Hey all how are you? Just so you know I hadn't abandoned the XOOPS project, I was just on extended leave, after developing around 40 modules for XOOPS 2.5 and myself and mamba at the repetitiveness of the system notices and emails we sent around, I decided to silently go on holidays.

You may notice through the threads that sometimes me and mamba have a spat at each other, that is more or less we have become more personally involved in each other (he is my boy friend, joking!) no just over the decade or so I have been involved in XOOPS some of the team are like family and like family you have disagreements every now and again.

I was suffering and still from lower back pain from the several decades of programming, but I don't think i want the option my cousin is trialling standing at the computer as I have seen with defence people and so on that stand a lot the arches of their feet collapse and it causes them pain to even walk.. Anyway we will see how Professor Matthew Roberts fairs with this, might need to find some periodically standing and sitting as well as hammock mode as well I think matt.

I did ask griff if he needed help in the core like I have with phppp a couple of times, but he seems to have it under control. I will be stripping back the number of modules I convert to XOOPS 2.6 which you will find journalese on the blog on my sourceforge project for my Cooperative Chronolabs. This is basically as the library in XOOPS 2.5 became too much to maintain and support and I have to make a living from my business as well as offering quality not rushed open source!

If you would like to Join Chronolabs we are looking for developers for a few long term projects and looks like all the legal documents for collecting ICANN/IANA Debt are all falling into place like last time in Dynasty 2 we're we are here again in prince Greorge william son and it is in Long play of history now so hopefully we will be making a suburb called XOOPS and one called Chronolabs and providing VC money to the XOOPS project so the project team is paid! We will all wait and see!

Viva XOOPS

xTransam 2.01
Chronolabs Cooperative release

Release Notes:

I have decided to remake xTransam to a new major version of 2.0, this now uses the gatewayhttps://translator.labs.coop to do the translation which stores a 24 month long cache on translations so they only need to be asked for once from the symbiotic translation api's, otherwise it will tell you the translation from the Gateways cache which will include a faster response being a file store not a database store.

New Features Include:

• Theme Language Support
• Providers to use
• Order of Providers to use

Testing Notice & Bug Report:

Please post your bugs on Chronolabs Soureforge Tickets - This is currently for XOOPS 2.5 only (Still waiting for language types to be solidified for XOOPS 2.6 before conversion).

Download: xoops2.5_xtransam_2.01.zip - 105Kb

[size=xx-small]Mamba: Publish new on this if you like I will email you the xcode for it - bit disheartened to go near the module seeming none of my news has been published for over a year while on holidays[/size]

Notabily something I have found is the length of time it takes to poll translation api's, my solution to this was to build :https://translator.labs.coop/ - The Chronolabs Translation API.

This stores translations and can be passed a storage token which for a module would be something like for xtransam as a module as md5('xoops-module-xtransam') - so that if someone else has ran for the translation your after; it will retrieve it from the cache for upto 24 months from the initial translations rather than having to wait to poll google, bing or mymemory.

This uses a file storage method not a database with similar classes to the cache class that comes with XOOPS - this is cause flat files are always much quicker than using a Database store and more manageable on mass.

In the next few weeks I will update xTransam, to this API for it provider methods this is so we eventually have fast and quick translations stored in the cache on this API. I will then after making a new Major Version of xTransam, looks too see if the language files have been finalised for XOOPS 2.6 and make a version for this as well.

I will post a thread here when both are complete!

Thanks

Simon - wishcraft/mynamesnot

Hey all you can download if you like XOOPS Logo - ASCII Art.txt - it is around 30k and contains the following art.. Good for Readme etc.