Chat APIs
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- javascript
- Área
- api
Línea de trabajo
The issue proposes chat namespaces, provider APIs, permissions, and manifest.json declarations, but names no source files, tests, or entry points. Start by reviewing the existing extension architecture and manifest.json, then determine which part of the proposal is in scope. The issue has no concrete completion criteria, so an agreed design and bounded implementation target are needed before work can be considered done.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
There should be a namespace to interact with chat. The following is an old draft of mine of what that could look like:
APIs (ordered by namespaces)
- chat
- conversations
- Conversation
- id
- accountId
- muc
- name
- room
- buddyId
- unreadCount
- mentionCount
- lastReadMessage
- topic
- Participants: Array of Participant
- Participant
- id
- name
- conversationId
- avatar
- status
- statusText
- metaDetails
- mode (OP etc.)
- create
- accountId
- room?
- buddyId?
- update
- conversationId
- index?
- unread progress/state?
- selected?
- query
- selected?
- index?
- providerId?
- accountId?
- muc?
- conversationId?
- close
- conversationId
- getParticipants
- conversationId
- updateParticipant
- participantId
- updatedParticipant
- onCreated
- onUpdated
- onClosed
- onTooltip -> allows adding data to the tooltip
- Conversation
- buddies
- Buddy
- id
- accountId
- status
- statusText
- create
- accountId
- buddy login or whatever
- nickname
- update
- nickname
- query
- buddyId?
- nickname?
- accountId?
- providerId?
- remove
- buddyId
- onCreated
- onUpdated
- onRemoved
- Buddy
- providers
- Provider
- id
- name
- canMuc
- canBuddy
- canTopic etc.
- IRC
- onCAP
- onCommand
- onTag
- onISUPPORTs or whatever
- etc.
- XMPP
- I don't know XMPP, just that it has something similar to the CAP system.
- onStanza
- get
- onRegistered
- onUnregistered
- Provider
- accounts
- Account
- id
- providerId
- server
- nickname
- password
- autoJoinedRooms
- create
- update
- query
- remove
- onCreated
- onUpdated
- onRemoved
- Account
- presence
- Presence
- avatar
- status
- statusText
- get
- update
- onUpdated (with reasons like auto idle)
- Presence
- messages
- Message
- id (not sure)
- text
- rawText
- userName
- buddyId?
- participantId?
- incoming
- system
- timestamp
- conversationId
- create
- conversationId
- text?
- raw? (so you can send custom XMPP and IRC etc. payloads)
- query
- conversationId
- buddyId?
- onReceive
- allows filtering/changing a message
- onSend
- ditto
- onCommand
- or should commands be declarative in the manifest.json?
- Message
- menus
- add extra targets for messages, conversations, buddies and participants
- conversations
That's about it for APIs. But as you will notice, nothing about themes, emote sets or new providers in there. That's because that should be statically declared in the manifest.json:
- provider
- name
- icon
- entry_point -> html file that gets special APIs described later on
- capabilities
- topic
- buddy
- muc
- presences
- ?
- setup
- type (oauth vs. pw/login)
- fields
- username
- server
- password
- port
- TLS
- defaults
- defaults for fields -> set OAuth URL here?
- emote_set
- not sure how this'd look. Probably a key value map?
- theme
even less sure how that'd work. In Firefox themes have been abstracted far away from the "bare metal" to essentially CSS var tweaks, which is definitely way less than what chat themes have been able to do. Given the APIs above I think a theme should just be able to do everything themselves, they just provide the HTML file to load in the conversations frame and then there's some API for them to know what conversation they're in and that's about it. Requires it to be the last one to get the events, so probably needs a specific implementation for themes. - permissions
- accounts
- conversations
- messages
- buddies
- providers
- presence
- irc
- xmpp
The provider API
Provider pages would essentially get some additional APIs to either build on top of an existing provider or build their own (and since TCP sockets are not exposed to extensions atm some socket would have to be exposed...)
Not sure if some APIs should be restricted from here, so the socket part can run in its own thread and all the front-end stuff that doesn't actually need the socket would be forced to the classic extension background script and they could communicate by messaging.
The exposed socket things would be classes that could be extended? Not sure. All the events from the other APIs should only be sent for changes coming from outside the provider, so the provicer can use the create, update and remove methods for UI changes.
- providers
- IRC
- XMPP
- Socket
- conversations
- addParticipant
- removeParticipant
- messages
- create
- from
- create
- providerInstance
- setConnectionStatus
- onConnected (user/autoconnect)
- onDisconnected (user disconnect)
- ???? -> probably mostly event handlers -> many type specific handlers are already present in the API above, maybe add shortcuts that don't require filtering for providers
- Lenguaje dominante
- JavaScript
- Estrellas
- 33
- Forks
- 18
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de thunderbird/webext-experiments
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
-
Proposal: narrowly scoped account order APIPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
thunderbird/webext-experiments#72 · 3 comentarios ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
thunderbird/webext-experiments#61 · 2 comentarios ·
Todos los issues de thunderbird/webext-experiments
Issues similares
-
Edit: Hello TasteAbiertochannels:edit check:passed
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Los mantenedores suelen responder en 2 días
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
hiero-ledger/hiero-sdk-js#4793 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
addyosmani/agent-skills#802 ·
Los mantenedores suelen responder en 4 días
-
26.04 bug dark-mode Easy Hack impress symptom: visual
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
CollaboraOnline/online#16421 · 1 comentario ·