World: r3wp

I wouldn't be "all fresh and happy" - I'd be a little bit grumpy 
about it.
But I'm interested in how the old messages were lost.
Did the power outage occur when AltME was writing files?

Perhaps we could place all the world files in a Git repo and run 
a cron job to update the repo regularly.

Has anyone done something like that?

I missed that horror.

With a slow connection, when datasets are large and take too much 
time to reload, Altme performs an automatic deco/reco and all the 
current loading is lost.
Probably because it fails to ping the server during the load.

Entering in endless attemps to reload and reload the same dataset 
(not sure though).

It's an OLD issue, I already notified that in the past. several times.

but I always had trouble making myself trust by people who do have 
not that problem.

I missed that horror.

With a slow connection, when datasets are large and take too much 
time to reload, Altme performs an automatic deco/reco and all the 
current loading is lost.
Probably because it fails to ping the server during the load.

Entering in endless attemps to reload and reload the same dataset.

It's an OLD issue, I already notified that in the past. several times.

but I always had trouble making myself trust by people who do have 
not that problem.

What would be useful isd for RT (or whoever currently holds the development 
rights for AltME) to publish the API that syncs the local copy with 
the server.

Then the better programmers among us could write a resync/repair 
tool. Run that routinely before starting AltME, and a number of issues 
(like the . problem) may be solved.

I don't know that it was a power outage. It was something about files 
being truncated on the server, then synced to clients, IIRC.

It was during a move, so probably simply not moved or unpacked

AltME already attempts to repair message databases since a year or 
two; it just doesn't work well enough

who cares about old messages ? noone read them anyway ...

flush out the altme is great altme has the right too forget things 
and start blank :)

It's easy enough to archive/delete dead groups......Would you like 
to propose a candidate list?

I would make the case that anyone wanting to write a book about the 
emergence of R3 from an engineering standpoint might want  access 
to an altme archive ... or has that ship also sailed ?  Also quite 
open/transparent:  IO language IRC exchanges and the evolution of 
the Falcon language at falconpl.org with their maillist.  But Carl 
is talking about getting rid of the maillist for Rebol - when archived 
maillists are often so useful in hindsight. ...

footnote: the Griswold papers on SNOBOL and ICON ended up in the 
library at UMN - his collaborators may never have thought of posterity 
taking an interest.

Only when they're used. Many of the people in the community don't 
really use email anymore (including Carl and me).

I'm not opposed to having the mailing list continue, but really dread 
having to use it, which I will have to if it starts being used.

I must be subscribed to over 10 mailing lists

Why are special chars like: ä ö ü ß totally screwed up when posted 
from OSX and read from a Windows version an vice versa? Is there 
a solution to this?

I think they're each interpreting text according to their own native 
character set. Windows in UTF-16, OS X and Linux probably in UTF-8. 
AltME doesn't compensate

Yes, AltME simply ignores character encoding.It simply regurgitates 
the text it receives from the client. I believe that REBOL/View uses 
the default codepage under Windows(not utf-16) and MacRoman under 
OS/X. I suspect it uses ISO-8859-1 under Linux but am not sure.

Any solutionw would require changes to AltME.

From a previous discussion: Whenever I post something from the clipboard 
into AltME I make sure I run the following first:

cb: func [][
    write clipboard:// read clipboard://
]

Ashley that overcomes the 'newline" issue with pasting OS X text 
(\n newlines) into AltME which uses MacRoman (\r newlines) but I 
don't think that it overcomes the charcter encoding issues.

You're right ... just tried it with some quoted text from a Pages 
document:

	ÒQuotes are the main culpritÓ

Most of accented characters are affected - it makes the messages 
in FRANCE unreadable.

I don't have trouble with accents in  Altme... its more the germanic/scandinavian 
chars which skrew up.

That's probably because you're using Windows and the people who wrote 
the messages are also using Windows.

Try these 
a acute ˆ
e grave Ž
c circumflex 

ah yes.. its not just region its also the os that's the problem.

It's not really a problem if you remember that AttME is designed 
to support 7-bit ASCII across operating systems.


It's just these users that wan't to write some fancy characters ;-)

yeah damn frenchies  ;-)

In fact AltME works pretty well for WIndows users as long as they 
stick to Windows Codepage 1252.

I've finally broken the secret of how to get reliable message copying 
to clipboard from altme !!!!

just make sure to click in the message posting text area before right 
clicking on the post you want to copy !

interesting ..!

in the last year, I've been noticing that the message copying worked 
somehow and there was a pattern... I just coudn't figure it out.

then, today I did 11 copy/pastes in a row and was typing at the same 
time (and they all worked!)...

that's when I realized that going from typing to copying was the 
secret!

Is that on Windows? I've been reporting the procedure for Linux here 
for years

yep on windows.  strange, maybe I just forgot or didn't notice your 
post(s) about it.

I didn't know it was that problematic on Windows as well - or maybe 
I also forgot :-)

Public group request (probably not web-public yet): WebOS
Description: Development for WebOS with REBOL

Similar to the Android group.

Reposting Robert's request: How about creating an RMA group?

Done!

Thanks, Sunanda.

Hi everyone. For the record, logging into REBOL-gate as guest/guest 
doesn't work.

Ends up giving an incorrect password error.

Welcome, Rob

Thanks Rob.
I've fixed that.....Next step is to find out what broke it :)

The SQLite group is broken ... I suspect a corrupt file on the server.