AmigaOS Team Lead Steven Solie to take part in Sunday Q&A IRC chat

This was announced over on AmigaWorld.net and is a sure thing for tomorrow...

http://amigaworld.net/modules/newbb/v ... wmode=flat&order=0#711445

AmigaOS Team Lead Steven Solie will participate in a moderated question-and-answer session during a portion of the weekly Asha Develder Memorial Internet Relay Chat this Sunday, July 7, 2013.

Here's the text from the announcement...

Chat will be starting at 3pm EDT (2000 UTC). We changed the start time in
order to include more people from Europe, as the original start time was in
the middle of the night for them. But we're still keeping it going through
until 11pm EDT (0400 UTC), with stragglers until whenever.

SPECIAL GUEST: Joining us at 6pm EDT will be Steven Solie who is the acting AmigaOS Development Team Lead.
Steven will try his best to answer all of your questions about the one and only Amiga Operating Sytem. Suggestions for improvements to AmigaOS are also welcome.

During the Solie visit, the channel will be moderated. Please feed your
questions to the designated channel @operator or +moderator. Before and
after that, it'll be an unmoderated channel.

Standard Ashachat rules apply: No religion or politics until after things
wind down at 11pm EDT. And other IRC etiquette rules apply, as well, such
as no flooding.


And some instructions courtesy of number6...

server = irc.superhosts.net - port 6667
channel = #team*amiga
have patience with connect time

The irc template for sending questions to a moderator/op:

"/msg [operator nick] [question]" no quotes

If I worked that out right, that means it starts at 9pm UK time, and Steven Solie comes on at midnight...

"No religion or politics til things wind down..."

I thought to some Amiga is a religion this might prove difficult.

Someone just remember to post a link to a log after the fight is over so we can all savour and enjoy ssolie's suffering in its minutest detail over and over again.

Edit: typos

@Severin

no worries on that score. it'll be up at intuitionbase.com shortly after the Q&A ends. heh. ssolie is rather brave to offer himself up like this. gonna be fun!

-- eliyahu

Ssolie isn't brave, he just has a thick skin

Not much luck connecting so far:
Quote:

EDIT: OK it worked third time around.

I am told that Ssolie is actually due to answer questions at 11pm (UK time), not 12pm as I had deduced. Although he is already online now, so maybe he starts earlier than that?...

Now in progress.

Bloody good read, enjoyed that immensely

Well done Steven

Two new developers? Any names, please Or we have to wait for Hyp blog update?

@ChrisH

For future reference, identd is a pain. If you can set up application ports on your router so an outbound connection on port 6667 activates the identd port (the number of which I forget) it should stop things like you saw, and long pauses when logging into IRC etc.

Quote:
Keep an eye on the blog...

Quote:
Glad you liked it. I really just answered off the top of my head as honestly as I could.

Please feel free to contact me directly for any clarifications. I don't want anybody walking away saying "I think he meant this..." If in doubt, ask me. http://solie.ca/contact/contact.php

@Chris(Y)
Quote:
Port 113 ?
( http://www.speedguide.net/port.php?port=113 )

Although I can't see how to configure my Netgear firewall to do what you suggest :-/

BTW, any idea why Windows-based IRC client(s) don't seem to have this problem? (Although I didn't specifically check this time.)

Quote:

Looks plausible.

Quote:

Sometimes it's called Port Triggering. Here are some instructions for NetGears (whether it applies to yours is another matter): http://kb.netgear.com/app/answers/det ... -setup-port-triggering%3F

Quote:

I suspect they do have the same problem. I haven't used IRC under Windows for at least five years, and that time I was using a server which I've never had identd problems on anyway.

Thanks for the irc chat log. Had a good and funny reading :)

@Chris(Y)
Sadly no such option on my Netgear :(

I tested with a Windows IRC client, and it also seemed to have the same problem...

...BUT WookieChat still takes 2-3 times as long to connect. However, I noticed that is the case for all networks. I think WookieChat is either slightly broken or missing a speed trick. (IIRC, AmIRC also connects faster than WookieChat.)