Lotus Nut

Over the past couple of weeks, I have had some people email/tweet me about connectivity to im.bleedyellow.com. In these cases, port 1533 was being blocked either at a client location or a public place (even in a hospital!). So the first thing I always mention is to try port 80 and voilà we're in business!

So while we are all thinking about it - change those connections on your laptops!

Looks like these two products are now in the wild! Documentation for both products is forthcoming, so check here for Sametime Advanced (as a new topic in the menu) and here for Quickr 8.1.

I've already upgraded a Quickr server. Daniele Vistalli has some quick, but good, notes on upgrading from Quickr 8.0.0.x.

And I'm currently setting up a VMWare machine to use for Sametime Advanced...

We want to have everyone participating in the im.bleedyellow.com Sametime community. So after many internal discussions about how to prove this, we've released this Official Statement that we have not, do not, and will not be logging chats that occur on this Sametime community.

For those of you who have had trouble accessing the im.bleedyellow.com Sametime community from behind your company's firewall, we have just opened access to the community from port 80 - port. Chat away!! You can still use 1533 if you haven't had problems with that.

By the way, if for some reason you need to access the web server, you'll need to go to http://im.bleedyellow.com:8088

Thanks to Mikkel Heisterberg there is now a "Custom Sametime blackbox for bleedyellow.com" - check out his post for more details. If you're logged into the im.bleedyellow.com Sametime community and you've updated your Profile picture then it will surface in the Sametime business card. Good work Mikkel!

OK, don't laugh too much, but I have been using the following icon for my BleedYellow community in Sametime:



Mostly cheezy, but it's easier to differentiate that community compared to, say, a sideways blue triangle!

Earlier today, Mr. Tripcony pinged me saying that only a handful of people were showing up online at the BleedYellow Sametime Community. After having dinner with him (good choice, btw), I came back to the hotel and started to look at the issue. The YellowBleeders group contains a subgroup as its only member. This subgroup, in turn, contains multiple subgroups with long lists of accounts. The registration process adds people to a group and then creates another group after the previous one reaches a certain size (y'know, the whole 32K list thing...). We're up to 800 registrations! so there are 3 groups. But I digress...

Initially, I thought that the problem was the nesting of groups. However, I noticed that the first group had about 30 names sorted and then the remainder wasn't sorted. This was because I had previously modified this group to add the Org to the names, and on saving it the group was automatically sorted. It turns out that the only people I could see online just happened to be in that first group, and just happened to be in that section of sorted names. So after sorting all of the groups, some more names began to appear in the list of online users!

Let me know if you still see some issues with this. I need to modify the code to sort the groups automatically, but I don't want to mess with that code while I'm away from the office for a few days...

If you want to chat with others who are on the BleedYellow site, you can do this. You can add a new Sametime community to im.bleedyellow.com (port 1533). Then add the group YellowBleeders...

bada boom bada bing!