121
edits
Difference between revisions of "GSoC/2020/Project Ideas"
Jump to navigation
Jump to search
→High Level Messaging API
(Add initial Prosody ideas) |
Vanitasvitae (talk | contribs) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 76: | Line 76: | ||
Currently Smack can establish connections via TCP/IP and HTTP via BOSH. WebSockets are yet another way to connect to a server. | Currently Smack can establish connections via TCP/IP and HTTP via BOSH. WebSockets are yet another way to connect to a server. | ||
=== Smack Bot Framework === | |||
''Brief explanation:'' Create a bot framework with Smack that enables the easy definition and creation of bots.<br/> | |||
Smack is currently mainly targeted towards client developers. It would be nice to make it more appealing to bot developers. | |||
''Involved Technologies:'' Android compatible Java 8<br/> | |||
''Mentor(s):'' Paul Schaub (vanitasvitae) [mailto:vanitasvitae@fsfe.org email: <vanitasvitae@fsfe.org>]<br/> | |||
''Deliverables / Expected Results:''<br/> | |||
* Being able to create a chat bot that does a simple task with only a few lines of code. | |||
* Implement a spam fighting bot for use in multi user chats. That bot should be invitable to a chat by admins and then monitor messages. It must ban spammers and remove their messages with the help of XEP-0425: Message Moderation. Configuration is per multi user chat and should be done via Data Forms or - if supported by the admins client - via XEP-0439: Quick Responses. | |||
=== High Level Messaging API === | |||
''Brief explanation:'' Smack provides APIs for sending and receiving messages (duh).<br/> | |||
What this project is about is to create a high level API that unifies the process of sending plaintext and e2ee encrypted messages. | |||
''Involved Technologies:'' Android compatible Java 8<br/> | |||
''Mentor(s):'' Paul Schaub (vanitasvitae) [mailto:vanitasvitae@fsfe.org email: <vanitasvitae@fsfe.org>]<br/> | |||
''Deliverables / Expected Results:''<br/> | |||
* An intuitive, easy to use API for sending and receiving plain and encrypted messages using OMEMO and OX. | |||
* A framework that makes it easy to listen for incoming messages, message corrections, retractions and other updates and that is easy to plug into as a client. | |||
== Dino == | == Dino == | ||
| Line 86: | Line 112: | ||
''Project Contact Person:'' [[User:Larma| Marvin W. (larma)]]<br/> | ''Project Contact Person:'' [[User:Larma| Marvin W. (larma)]]<br/> | ||
''List of Teaser Tasks:'' [https://github.com/dino/dino/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 Dino good first issues]<br/> | |||
''Contact chat:'' [xmpp:chat@dino.im?join chat@dino.im] | ''Contact chat:'' [xmpp:chat@dino.im?join chat@dino.im] | ||