[Chicken-users] Askemos again; this time bad news. Needs some support/donation.
Hello $all,
we've been recently in touch regarding Askemos. Now I might need
some help, if you can.
Until Wed, 23 Jan 2013 15:55:00 +0100 the Askemos cloud ran on
a rather healthy mix of peers.
Pardon me? }:-| ??? …
On Jan 18 2013, Daniel Leslie wrote:
A little off-topic for this list, but it comes up now and then so I'll
dive into it. Every time Askemos comes up I get a deep curiousity that
has me exclaiming What is this thing?! Especially after perusing pages
like this one
http://askemos.org/Ad60e3fb123a79b2e5128915116b288f7/index.html/?_v=footnote_id=1223.
…
And, erm, what are the minimal steps for bootstrapping a server which can
collaborate on this *ethical cloud*?
…An almost healthy mix, that is. For historic reasons three of
those eight peers of the development network, which originally where
at different locations, ended up behind a single point of failure. Since
the system promises fail-stop, I can't even add a note into my blog.
Given the trouble I expect more. In case of trouble: all URL's
given here would/could/should be served from several locations.
*IF* the URL after the askemos.org part starts with an
A[0-9a-f]{32} path step, just replace the prefix with
any other replica and retry. Odds are 5:8.
For hosts still visible see appendix.
So find the reference cited above under
http://login.softeyes.net/Ad60e3fb123a79b2e5128915116b288f7/index.html/
or it's alternatives while I'm fixing the DNS etc.
@Ian Grigg and Allison Stellíng: the same applies to the not-so-private
message I just sent out minutes before the disaster happend. Find the
one-pager-message wrt. system theory under hash code:
A5ae3c14013b6fe38b4aa66a2697e097f that would be e.g.
http://login.softeyes.net/A5ae3c14013b6fe38b4aa66a2697e097f or
http://peanut.softeyes.net:7080/A5ae3c14013b6fe38b4aa66a2697e097f [the
latter being a plug computer at home only].
I just wanted to add a forgotten note beneath the TC DISCLAIMER
http://cl.softeyes.net:8080/A5ae3c14013b6fe38b4aa66a2697e097f/Systems%20in%20Genetic%20Autopoesis
This: The hypothesis wrt. cancer would be that the strict rule
*no communication along the diagonal* where shortcut.
Leading into a 'thermodynamic chaos'.
When those three peers disappeared.
## The Needs - Short Term
To fix the case I rather urgently need to find at least two
locations, where I dare to replicate my notes wrt. to my personal
privacy. One already secured; so one more whom I can trust
not to embarrass me by leaking info taking as a remembrance to
myself. Preferable outside Germany.
## Minimum requirements
BALL became a bit like the Swiss-army knife wrt. small scale
ISP needs not having a solutions widely deployed for a reason.
For operation it needs to bind to a port at the moment.
Run as some isolated user it needs to be able to maintain the
contents of one directory.
## Participate - Long Term
The more parties joining the network, the better it should help
with privacy, safety and autonomy.
### Regarding the Healthiness
So far we had
♣: AMD64, i386, ARM
♠: Chicken, Rscheme
♡: FreeBSD, Linux
♢: GPL, BSD
for symbols see A5ae3c14013b6fe38b4aa66a2697e097f , the
not so private draft message.
At the moment RScheme and FreeBSD are gone; leaving
both the pure GPL and the BSD stack incomplete.
Thanks for your time.
/JFW
## Hosts Still Visible
http://login.softeyes.net
http://isstvan.softeyes.net:7080/
http://cl.softeyes.net:8080/
http://peanut.softeyes.net:7080/
..
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Egg: redis bindings
Relatedly, has anyone updated the old memcached egg? Considering that MySQL 5.6 brought in a NoSQL memcached APIhttp://dev.mysql.com/tech-resources/articles/whats-new-in-mysql-5.6.html#nosqlthis may prove to be of some use. -Dan On Wed, Jan 23, 2013 at 7:27 PM, richo ri...@psych0tik.net wrote: On 23/01/13 20:59 -0500, Andrei Barbu wrote: Hi, I put up an egg that has high-performance redis bindings using hiredis. It's much faster (100x) than the current egg and it doesn't suffer from timeout issues. Provides a pretty bare-bones API. I've put up docs on the wiki: https://wiki.call-cc.org/**eggref/4/redishttps://wiki.call-cc.org/eggref/4/redis And the egg is available from: https://github.com/abarbu/**redis-chickenhttps://github.com/abarbu/redis-chicken Could someone make this accessible via chicken-install? Thanks! I'd also appreciate if someone had a look at the meta/release-info/setup files and let me know if I'm doing something inappropriate. Awesome, I wrote a small library that's current backed onto either flat files or redis at the deployers option, I'll have a play with this in the evening! Cheers Richo -- richo || Today's excuse: The monitor is plugged into the serial port http://blog.psych0tik.net ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Egg: redis bindings
Never mind, the qwiki search didn't show the /4/ egg when I searched for memcache, but it does appear to exist: https://wiki.call-cc.org/eggref/4/memcached -Dan On Thu, Jan 24, 2013 at 10:12 AM, Daniel Leslie d...@ironoxide.ca wrote: Relatedly, has anyone updated the old memcached egg? Considering that MySQL 5.6 brought in a NoSQL memcached APIhttp://dev.mysql.com/tech-resources/articles/whats-new-in-mysql-5.6.html#nosqlthis may prove to be of some use. -Dan On Wed, Jan 23, 2013 at 7:27 PM, richo ri...@psych0tik.net wrote: On 23/01/13 20:59 -0500, Andrei Barbu wrote: Hi, I put up an egg that has high-performance redis bindings using hiredis. It's much faster (100x) than the current egg and it doesn't suffer from timeout issues. Provides a pretty bare-bones API. I've put up docs on the wiki: https://wiki.call-cc.org/**eggref/4/redishttps://wiki.call-cc.org/eggref/4/redis And the egg is available from: https://github.com/abarbu/**redis-chickenhttps://github.com/abarbu/redis-chicken Could someone make this accessible via chicken-install? Thanks! I'd also appreciate if someone had a look at the meta/release-info/setup files and let me know if I'm doing something inappropriate. Awesome, I wrote a small library that's current backed onto either flat files or redis at the deployers option, I'll have a play with this in the evening! Cheers Richo -- richo || Today's excuse: The monitor is plugged into the serial port http://blog.psych0tik.net ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Egg: redis bindings
Hi, Andrei Barbu and...@0xab.com writes: I put up an egg that has high-performance redis bindings using hiredis. It's much faster (100x) than the current egg and it doesn't suffer from timeout issues. Provides a pretty bare-bones API. cool, I wasn't aware of hiredis! I've put up docs on the wiki: https://wiki.call-cc.org/eggref/4/redis You mention Note that you will need to fetch the git submodules in this package. -- I wonder if the .tar.gz includes the checked out submodules, too? Otherwise it won't work with the eggs infrastructure I'm afraid. We'll know in a bit though :-) Could someone make this accessible via chicken-install? Thanks! Done! I'd also appreciate if someone had a look at the meta/release-info/setup files and let me know if I'm doing something inappropriate. Looks fine AFAICS. You can remove the `egg', `files' and `doc-from-wiki' clauses from the meta file, though. They are not needed anymore. FYI, I also made a Redis egg once which I never released because I didn't need it eventually and then I couldn't be bothered to finish it up and write documentation for it :-) I took a slightly different approach in providing a high-level API which exposes each Redis command as a Scheme function. You can find the code here https://gitorious.org/chicken-eggs/redis Regards Moritz ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Askemos again; this time bad news. Needs some support/donation.
To fix the case I rather urgently need to find at least two locations,
where I dare to replicate my notes wrt. to my personal privacy. One
already secured; so one more whom I can trust not to embarrass me by
leaking info taking as a remembrance to myself. Preferable outside
Germany.
Are you saying that you require access to a physical server outside of
Germany, on which you may bootstrap instances of Askemos to act as
replication peers?
If so, I'm sorry to say that I'm stuck on a slow residential cable line and
haven't the cash to spare for the continuous operation of a server. Between
my wife's tuition and the mortgage, we're rather tight for cash.
-Dan
On Wed, Jan 23, 2013 at 1:32 PM, Jörg F. Wittenberger
joerg.wittenber...@softeyes.net wrote:
Hello $all,
we've been recently in touch regarding Askemos. Now I might need
some help, if you can.
Until Wed, 23 Jan 2013 15:55:00 +0100 the Askemos cloud ran on
a rather healthy mix of peers.
Pardon me? }:-| ??? …
On Jan 18 2013, Daniel Leslie wrote:
A little off-topic for this list, but it comes up now and then so I'll
dive into it. Every time Askemos comes up I get a deep curiousity that has
me exclaiming What is this thing?! Especially after perusing pages like
this one http://askemos.org/**Ad60e3fb123a79b2e5128915116b28**
8f7/index.html/?_v=footnote_**id=1223http://askemos.org/Ad60e3fb123a79b2e5128915116b288f7/index.html/?_v=footnote_id=1223
.
…
And, erm, what are the minimal steps for bootstrapping a server which can
collaborate on this *ethical cloud*?
…An almost healthy mix, that is. For historic reasons three of
those eight peers of the development network, which originally where
at different locations, ended up behind a single point of failure. Since
the system promises fail-stop, I can't even add a note into my blog.
Given the trouble I expect more. In case of trouble: all URL's
given here would/could/should be served from several locations.
*IF* the URL after the askemos.org part starts with an
A[0-9a-f]{32} path step, just replace the prefix with
any other replica and retry. Odds are 5:8.
For hosts still visible see appendix.
So find the reference cited above under
http://login.softeyes.net/**Ad60e3fb123a79b2e5128915116b28**
8f7/index.html/http://login.softeyes.net/Ad60e3fb123a79b2e5128915116b288f7/index.html/
or it's alternatives while I'm fixing the DNS etc.
@Ian Grigg and Allison Stellíng: the same applies to the not-so-private
message I just sent out minutes before the disaster happend. Find the
one-pager-message wrt. system theory under hash code:
A5ae3c14013b6fe38b4aa66a2697e0**97f that would be e.g.
http://login.softeyes.net/**A5ae3c14013b6fe38b4aa66a2697e0**97fhttp://login.softeyes.net/A5ae3c14013b6fe38b4aa66a2697e097for
http://peanut.softeyes.net:**7080/**A5ae3c14013b6fe38b4aa66a2697e0**97fhttp://peanut.softeyes.net:7080/A5ae3c14013b6fe38b4aa66a2697e097f[the
latter being a plug computer at home only].
I just wanted to add a forgotten note beneath the TC DISCLAIMER
http://cl.softeyes.net:8080/**A5ae3c14013b6fe38b4aa66a2697e0**
97f/Systems%20in%20Genetic%**20Autopoesishttp://cl.softeyes.net:8080/A5ae3c14013b6fe38b4aa66a2697e097f/Systems%20in%20Genetic%20Autopoesis
This: The hypothesis wrt. cancer would be that the strict rule
*no communication along the diagonal* where shortcut.
Leading into a 'thermodynamic chaos'.
When those three peers disappeared.
## The Needs - Short Term
To fix the case I rather urgently need to find at least two
locations, where I dare to replicate my notes wrt. to my personal
privacy. One already secured; so one more whom I can trust
not to embarrass me by leaking info taking as a remembrance to
myself. Preferable outside Germany.
## Minimum requirements
BALL became a bit like the Swiss-army knife wrt. small scale
ISP needs not having a solutions widely deployed for a reason.
For operation it needs to bind to a port at the moment.
Run as some isolated user it needs to be able to maintain the
contents of one directory.
## Participate - Long Term
The more parties joining the network, the better it should help
with privacy, safety and autonomy.
### Regarding the Healthiness
So far we had
♣: AMD64, i386, ARM
♠: Chicken, Rscheme
♡: FreeBSD, Linux
♢: GPL, BSD
for symbols see A5ae3c14013b6fe38b4aa66a2697e0**97f , the
not so private draft message.
Thanks for your time.
/JFW
## Hosts Still Visible
http://login.softeyes.net
http://isstvan.softeyes.net:**7080/ http://isstvan.softeyes.net:7080/
http://cl.softeyes.net:8080/
http://peanut.softeyes.net:**7080/ http://peanut.softeyes.net:7080/
.
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
