Sunday, February 24, 2008
Tuesday, February 12, 2008
iSwaggle
In keeping with the mobile times, we here at Swaggle are quite enamored of the iPhone, so we tailored a Swaggle interface just for that device. Just visit swaggle.mobi from your iPhone to try it out. You can create and manage your groups, send messages, change your name, whatever your heart desires.
Don't have an iPhone? As long as you have a Safari browser, you can still give it a whirl: http://i.swaggle.mobi/. (Well, you can try it on any browser, but no guarantee it will look right).
Don't have an iPhone? As long as you have a Safari browser, you can still give it a whirl: http://i.swaggle.mobi/. (Well, you can try it on any browser, but no guarantee it will look right).
Sunday, February 3, 2008
Group Management
We introduced several new features tonight:
- Group management: Group owners can now control their groups through the web interface (www.swaggle.mobi). When viewing a group, you'll now notice a "manage group" option that will let you change whether the group is public or private, broadcast or chat and even whether new members get announced.
- Member management: Group owners can now boot members from a group either through the web interface (see previous bullet) or by sending ".BOOT groupname XXXX" where XXXX is the name of the person you'd like to remove. Once removed, a user must ask permission to rejoin a group even if it is otherwise public.
Thankfully, nobody has asked for that second feature, and hopefully you'll never need it.
Friday, February 1, 2008
Who you talking to?
We've been noticing a common problem people have been having: someone is in two groups, they receive a message from one of the groups, reply to it and (I know, this is crazy), they expect that response to go to the group they just received the message from.
Well, that's not quite the way Swaggle worked. Because there is a single Swaggle phone number at the moment, the way we support multiple groups is to ask you to specify the group you're sending to (e.g., "skipals: Heading to the lodge" would go to the "skipals" group). To make life easier for the new user, we support the notion of a "default" group. That is, if you don't specify "skipals", we send to your "default" group, which is typically the first group you join.
So, if you receive a message from another (non-default) group and reply, we were sending that reply to your default group.
It wasn't working.
Now, Swaggle will send any message without a group specified to the group you last received a message from (within 2 hours). That way, if you receive a message and hit reply, it goes to the right group.
Hopefully, this will clear up the errors we're seeing, although we know it might also introduce a new type of error (you expect the message to go to your default group and it doesn't). Well, Swaggle is an experimental service, and we're experimenting.
Well, that's not quite the way Swaggle worked. Because there is a single Swaggle phone number at the moment, the way we support multiple groups is to ask you to specify the group you're sending to (e.g., "skipals: Heading to the lodge" would go to the "skipals" group). To make life easier for the new user, we support the notion of a "default" group. That is, if you don't specify "skipals", we send to your "default" group, which is typically the first group you join.
So, if you receive a message from another (non-default) group and reply, we were sending that reply to your default group.
It wasn't working.
Now, Swaggle will send any message without a group specified to the group you last received a message from (within 2 hours). That way, if you receive a message and hit reply, it goes to the right group.
Hopefully, this will clear up the errors we're seeing, although we know it might also introduce a new type of error (you expect the message to go to your default group and it doesn't). Well, Swaggle is an experimental service, and we're experimenting.