World: r3wp

Just operational messages - four of them in total. It's happenned 
a couple of times before but is very infrequent.

I've made the Red group [web-public] a few weeks ago, but I still 
don't see it been exported: http://www.rebol.org/aga-index.r, does 
it require some admin validation?

Sunanda has to ok it

to make sure it's not an error

but I guess there might be some issue with hosting on rebol.org a 
group which is competition with Rebol??

Thanks Doc -- I had not noticed that Red is flagged [web-public].

Theoretically, [web-public] gets you:

....automatically published on REBOL.net (though that appears to 
no longer be updated):
       http://www.rebol.net/altweb/rebol3/index.html

....and published on REBOL.org at the discretion of the Library Team. 
       http://www.rebol.org/aga-groups-index.r?world=r3wp


As Graham suggests there may be some issues, especially as REBOL.org 
is funded by RT. I'll ask the Library team to discuss.

The Red group is now published on REBOL.org -- my thanks to Library 
Team for the discussion:
    http://www.rebol.org/aga-display-posts.r?post=r3wp840x0

Thanks to the Library Team.

In another AltME world I'm participating in, AltME file sharing is 
used to share 103 files, all of which I have downloaded. Every time 
I (re)connect, AltME offers me to re-download 63 of them. Irrespective 
of whether I re-download or not, I'm again offered this each and 
every time I connect.

I faintly recall having heard of this problem before, anyone has 
a clue what's going on (and more importantly: how to fix it?). I'm 
using AltME 1.2.25 on Linux.

It may be the daylight savings time bug, where that changeover makes 
all the file times apparently an hour off. This is because the AltME 
file time handling isn't converted to UTC.

Any known fixes/workarounds?

Once a year, go through and redownload every file in the world. And 
be careful to not repost those files, which is hard to do because 
of UI problems.

I deleted and re-downloaded all files several times already, so I 
guess it's a different problem.

No, this is the yearly daylight savings time problem. It's just not 
fixable. Redownloading doesn't help

Thanks. Sucks.

As usual, the non-Windows versions such more. In the winter, you 
can use AltME Linux version. In the summertime, you can switch to 
running the Windows version on WINE...

suck more

That only fixes the redownloading, though. (For every changed file 
you want to fetch, you have to download all of them.) In the winter, 
files that you created in the summer will have the wrong status. 
In the summer, files that you created in any winter will have the 
wrong status

Gotta love it

Can't you just set the PCs all to GMT?

You can, if you want to make your problems worse

It will corrupt all other programs that use time. It won't fix AltME's 
problems. We've tried

Is there a way to change the port that an altme world uses?

I think so, you can specify it as a command-line parameter. But port 
numbers are limited, IIRC.

there is a config.txt file in same folder with altme.exe but I'm 
not sure if there is an option like that.
there is a line "host-port: 5400" but this is for client.

http://altme.com/guide/advanced.html#sect0.9.

I have following in my altme.cmd command line script:

start altme -s "my-world" -p 5400

The world becomes unreachable when I start it on a different port. 
Altm.com still thinks its on port 5400

is there a way to reset it on altme.com?

well, that might be tricky, as IIRC altme.com keeps the world info 
from xy days. You would have to let it time-out at altme.com, turning 
off the world for xy days imo.

and also - there might be one bug I noticed and reported. When you 
start first world on 5400, and the other one on 5401, altme.com registers 
the second one on 5400 too. I overcame it by disallowing port 5400 
on my firewall for the time of registration of the 5401 world, or 
it would connect users to my first world.

Alan, does your firewall allow the other port to be reached? I've 
never had much problems switching ports. Altme.com should detect 
the port change when the world is restarted, but it needs to be able 
to contact altme.com and the world shouldn't be run double on the 
old port

Kaj, I'm pretty sure I opened the whole range for altme 5400-5409 
and I tried a port that I know is open which I had another world 
running on.

Ah, altme.com may be temporarily confused by the previous world on 
that port. If it doesn't work after restarting the world a few times, 
something may have changed in altme.com

I tried maikng another world from altme.com hoping it would not assign 
the port until I started teh world for the first time with my desired 
port but no good...it was assigned 5400 so same issue.

amacleod - when starting second world, e.g. on port 5401, during 
the time of setting-up the world, please prohibit altme.com from 
accessing another port on already opened 5400 port. That is imo a 
bug I found, and it did not get fixed yet. So disable 5400 port temporarily 
on port 5400. Maybe it will be enough if you turn-off the world running 
on 5400 port, because I got into situation, when Altme.com pointed 
two different worlds to the same 5400 port ...

Thats what I got going on. two worlds on same port. I will try again 
but close off the other ports first...let you know how it goes...thanks 
all

Did you move one of those worlds to a different port? Are you aware 
that the port number is entered into a configuration file when the 
world is created? If you move it later, you have to edit the configuration 
file. AltME doesn't check for port conflicts on worlds you start

altme.com is flexible about port numbers, but AltME running as server 
is not

no, it's altme.com, which si buggy, as I described.

011-07-09 01:57:47.836 altme[3539:903] Warning - conversion from 
64 bit to 32 bit integral value requested within NSPortCoder, but 
the 64 bit value 9223372036854775807 cannot be represented by a 32 
bit value

anyone knows whats this? i had altme open on my intel mac for a few 
weeks and this is what it was spitting onto the terminal. there was 
interesting glicth happening at the same time: my clicks were interpreted 
with some offset.

Probably some counter overflow, but it's weird, because R2 is not 
supposed to have 64 bits values

I think its a message from the OS being logged by Altme.

Ah yes, Syllable has a similar log format, and the program name mentioned 
in front is often not the place the message is originating from

@  Reichart : We were discussing in the OPEN GL group about the default 
way AltMe permits to enter text - and we were 3 that think the default 
way to enter text would be the EDIT mode (the one that accepts Line 
feeds without submitting the post automatically. 


Would you be considering this option in a future release - even if 
I now realize that this is a global switch since when I submits new 
posts this mode is kept alive.


I didn't ask for others to vote for this change but you can do it 
if you want - I find it  really annopying - more than the obligation 
to commit messages by having to use the mouse each time. I know it's 
a productivity consideration but as I can't reedit my sent posts, 
sometimes they didn't look good - until I asked someone how to enter 
LFs.

Thanks a lot for considering this request. 
Regards, Gerard

Is Reichart still involved in AltME development?

I think not. IIRC Altme is RT's responsibility ....

Gerard, I'm not invovled in AltME anymore.... 

I like your idea, and I wish AltME was open source (which I have 
pushed hard for).