nic-ferrier

There's a long term plan to switch the wiki to being hosted on Emacs/Elnode. People could help out, especially with corner cases of the rendering. The repo is: https://github.com/aidalgol/elwiki

Note that we don't expect to do this quickly. Maybe we could get it up as a readonly mirror quite quickly.

Right now the issue is getting enough of the wiki cached that we're not under siege.

you forgot the link:

https://www.youtube.com/user/jekor?feature=watch

There are lots of videos showing you how to use Emacs. Emacs Bites is about teaching you Lisp.

wait. there are more than 3!

http://www.emacsbites.com/series/done-so-far

you're in luck! that's absolutely what I'm trying to do.

I do have secondary audience, people who want to learn Lisp, not necessarily elisp. Emacs is the best way to do that imo.

I expect those people to have at least looked a bit at Emacs before they start though.

I have been using Emacs for a long time and I can't remember the last time it got the wrong key.

If you're using a graphical Emacs (for OSX or X or Windows) I think it hardly ever happens? Doesn't happen to me and I use all 3 of those.

And again thanks. Fixed. The reason for this breakage is that I had to change the name after it was launched (in a hurry).

thanks! I've fixed that. Good catch.

I'm clearly doing a bad UX job with this somehow. There are a collection of little videos wrapped by web pages documenting what is in the video. Eventually they will add up to something substantial (hopefully) and comprehensive (hopefully).

I toyed with the idea of using something that would show you the keys... but those things are never totally reliable and always a bit of added complexity. So I decided instead to offer the web page approach.

I admit, I'm probably not doing a great job for complete Emacs newbies right now. I am unclear if I have to, there are a lot of starting Emacs screencasts around. This one is about starting with EmacsLisp, not really Emacs.

Having said that... if that's what people want I may go back and alter the structure of the thing so that total newbies could join in.

It would probably only mean having fewer expectations in the crash course.

Yes. The github is here: http://github.com/nicferrier/emacsbites

so come back.

yeah. there are loads of alternative video chat apps. that's not the point of teamchat.

Thanks jlf!

You guys at #emacs have helped this happen. An awesome community.

Yes. We're veterans of previous video startups. This is video meeting done right. It's not a big part of the product but it is important coz it means you don't need skype or hangout or whatever in addition to this.

If you ping me on twitter I'll make sure you're prioritized. We are obviously wanted teams to try this to tell us what is good and what isn't. So if you're a team we want you basically.

I'm not going to advertize it that much (because I don't want to support people that way yet) but all the code behind teamchat.net is freely available on github.

That should be fixed.

I'm kinda surprised that people haven't picked up on that bit and asked questions. You'd have thought hackers would be interested in that bit :-)

That's basically it. We've worked on this for quite a while and I reckon we could just keep going... This way we can gauge interest and prioritize teams who sign up.

And yes. I will publish results later in the week.

they are now.

Bigger ones now provided.

it's simple to build a simple one... but the more polished takes more time. Why not just offload that work to someone else? That's our view anyway. We've chatted to some potential clients and other companies running their operations this way.

will do. I'll also try and make sure you get prioritized for go live.

I'll try and prioritize your teams access. Send us an email or hit me up directly on twitter: http://twitter.com/nicferrier

I know... I know. I prefer that too.

The trouble is this is for teams, you kinda have to have a team. We wanted to gauge interest so we've done it this way.

If we can we'll go live for collections of people (if there are 2 or 3 people from the same company email domain) this week or next.

awww man. templating. thanks for catching.

It's all emacslisp. Including the webserver (it's elnode). So there is an irc bouncer written in elisp tightly integrated with the elnode webapp. The bouncer uses a modified rcirc (built into emacs) to connect to the irc servers.

The robot framework is also written in emacslisp.

The irc servers are ngircd and the webserver is nginx.

I'd recommend watching both. John's talk was really enjoyable, his point about charm was a really really good one.

Someone asked a question at the end about how to get charming. It's the same answer for everything: practice.

The OP is absolutely spot on, however, innovation in those fields he mentions is very hard because they tend to be closed shops. I think the best thing those places could do would be to talent buy some startup teams and see what happens because it's sure as hell true that their existing IT is failing to move with the times.

Witness the ridiculous mess the British banking industry has gotten into (with RBS, a massive British consumer bank having a failure that caused them weeks of further problems).

It can often seem to those of us outside that management in those companies has focussed on pure profit, not dealt with technical debt and not even tried to make an effort to adapt their IT strategy to the rest of the world.

This is interesting, I was only talking about doing this the other day, just for EmacsLisp on github and in the package repositories. Because of the constraint mine would be worse. So maybe better. Hmmmm.