"Ask the user. Reply back with a few choices and ask the user to pick one."
This makes the process difficult for devices using the api. If I post an @ via twhirl, is it going to offer me those choices? Maybe in the future, but keeping it simple is better. I agree with an aliasing system and IDs like the users use while subscribing remotely. We can make a table of these, like we have for the SMS carriers. Well, more like Evan's proposed table, where the first N aliases are reserved by the Dev team, the next N are local aliases to the host, and maybe another N could be user defined aliases. Then, the user puts in @id/evan to go to Evan, and @hap/happily to go to me, and @ta/john or @twit/john or maybe @army/john to go to [email protected]. I also propose that the user-defined aliases (if you have them) trump other aliases, so the user's aliases don't get changed on them too often. It would be better to not have user-defined aliases than to have aliases that get dropped. The question is: What happens when messages cross the Twitter bridge? Do they get stripped of this formatting so "@id/evan" becomes "@evan"? And will the default be local user or twitter user? Meaning, if I type @john on identi.ca, will it go to john on identi.ca or john on twitter? Will there be an alias for twitter that could be stripped out by the bridge code? _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
