Skip to content
/ Mintopi Public

Messenger Api for various platforms (see credits) - unified in a single structure in terms of interoperability

Notifications You must be signed in to change notification settings

piLovr/Mintopi

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Mintopi

This Project is a work in Progress (and not ready for use!). Feel free to contribute.

Naming Convention

I put a lot of thought into how to name Objects like Groups, Channels, Guilds, Communities, since they represent similar structures, but are called different among different messengers/platforms. If you have different thoughts about how to name things, feel free to tell me by opening an issue.

Progress (and maybe what's to come)

Clients with working connection:

  • Whatsapp
  • Discord
  • Telegram
  • (optional) Matrix
  • (optional) Signal

Message decoding:

  • Whatsapp
  • Discord
  • Telegram
  • (optional) Matrix
  • (optional) Signal

Listener Events:

  • Message
  • Room (Group-) Events (promote, demote, image updates)
  • System updates

Other stuff:

  • Client Error handling
  • General Error handling
  • Logger
  • Message Objects
  • Specific Message Objects (Poll, Location,...)
  • Media attachments in Messages
  • Room Objects
  • Optional Cache for GroupMetadata and Members
  • Roles in Rooms (Admin, Custom Discord roles)
  • Optional specific roles (could be useful for stuff like CommandBots)
  • Optional CommandHandler Structure (ready-to use for Commandbots)
  • Maven tests for various events
  • Maven tests for various messageTypes
  • Optional transfer to SpringBoot with RESTful Api for sending Messages

Credits:

Client API's

About

Messenger Api for various platforms (see credits) - unified in a single structure in terms of interoperability

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages