| A | B | |
|---|---|---|
1 | Client Implementations: | |
2 | o Desktop app | |
3 | o Cross-platform, using Qt GUI | |
4 | o Fully free and open source | |
5 | o Will support (MP)OTR | |
6 | o Makes a GUI for virtually every feature | |
7 | o Scripting support through Perl | |
8 | o May have inline Markdown rendering and composition | |
9 | o Could define "IRCdown", Markdown derivative that transates bold into control characters, supports mirc colors, etc | |
10 | o Android app | |
11 | o Fully free and open source (made for f-droid and google play) | |
12 | o Will support (MP)OTR | |
13 | o Notifications and inline pictures | |
14 | o iOS app | |
15 | o Chromium app/extension | |
16 | o Open-source and free as Chrom(e|ium) allows | |
17 | o Chat in popped-out window, in browser, or from extension button popup | |
18 | o Detects if a currently open URL matches the set URL of a channel, and will prompt to join the channel | |
19 | o Web app | |
20 | o Uses socket.io for support of very many browsers | |
21 | o Provides embeddable widgets and chat frames for websites | |
22 | o Dynamic and responsive for size | |
23 | o Customize colors and tab position | |
24 | ||
25 | ||
26 | Notes: | |
27 | ||
28 | Registration of a channel also registers all subchannels (#channel.*) | |
29 | Subchannels and their parent channel all share access levels | |
30 | A user will not get op when joining a subchannel without access in the parent channel | |
31 | Joining a subchannel when the parent channel doesn't exist will forward the user to the would-be parent | |
32 | ||
33 | C mode chanconfigs may be set multiple times (e.g. multiple trivia packs, multiple mail receivers) unless boolean or otherwise | |
34 | ||
35 | The IRCd itself sets modes anonymously, using the nickname "IRC" | |
36 | ||
37 | Logging bot works like the GNU `more` command, when reading logs, asks every 15 lines "Continue? y/n" | |
38 | ||
39 | Adding access is mask-based, you can give access to someone that isn't even registered to services. | |
40 | Referring to a nick, if the nick is identified, automatically makes reference to "$R:their_account" | |
41 | If they are BTC verified, and not identified, it references "$B:1TheirBitcoinAddress" | |
42 | Referring to *nick (asterisk, then nickname) translates to "$R:their_account", if the nick is owned by their_account. | |
43 | ||
44 | Channel name is errounous if it contains: $ ! > < = , | |
45 | ||
46 | If/when we have an SMS service, we may be able to become an SMS reseller, since IRC is an easy protocol to develop for. | |
47 | SMS users show up as |sms|xxxxxxxxxxx, and |sms|* is qlined only for use by the SMS service. | |
48 | For consumers, eventually services may not cost anything. | |
49 | For consumers, having a conversation over SMS will require the receiver to accept the messages (one-time prompt, yes or no) | |
50 | ||
51 | Output for services commands support pipes, " | grep "pattern"", only grep is supported for now | |
52 | ||
53 | Bots should set SWHOIS to pastebins/hawkees/sites for help |