teams-api
reload
| teams-api | reload | |
|---|---|---|
| 9 | 1 | |
| 124 | 42 | |
| 2.4% | - | |
| 0.0 | 0.0 | |
| over 1 year ago | 12 months ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
teams-api
-
Microsoft rebuilt Teams from the ground up, promises 2x faster performance
https://github.com/fossteams/teams-cli uses https://github.com/fossteams/teams-api
-
Microsoft Teams Premium: Cut costs and add AI-powered productivity
That's why we're building FossTeams [1] (:
The idea is to have a backend [2], powered by a library [3] that does the heavy lifting and a / multiple frontends to be used with that (e.g: CLI[4], Web frontend[5], Flutter app[6]).
We're looking for contributors! If you hate Teams and want to improve an Open Source version, PRs are welcome (:
[1]: https://github.com/fossteams
[2]: https://github.com/fossteams/fossteams-backend
[3]: https://github.com/fossteams/teams-api
[4]: https://github.com/fossteams/teams-cli
[5]: https://github.com/fossteams/fossteams-frontend
[6]: https://github.com/fossteams/fossteams_gui
-
teams-cli, a CLI for Microsoft Teams
These tokens are collected by replicating the Oauth flow with an Electron app that basically intercepts the redirection and gets the tokens. These tokens are then saved in a directory and are picked up by teams-cli (actually teams-api) when you use it.
- Run MS Teams on a Coffee Machine?? (Or: Embedded Linux Framebuffer VNC Client)
- Unofficial Microsoft Teams Library
- Show HN: Microsoft Teams (unofficial) Go library (WIP)
-
Microsoft Teams desktop reply to message feature missing
This is indeed frustrating, but there might be a technical explanation behind it: AFAIK message ids on Microsoft Teams are generated by the clients, and one cannot easily jump to a message ID.
Their Teams mobile app does something more stupid, but that kinda works: when you reply to a message, the message is copy-pasted as a quote and you are basically sending back the original message to the user.
I really don't get why Microsoft Teams is _that_ overengineered and (IMHO) badly develooed. Their clients are super heavy on CPU and memory and I can barely use the web version.
On a side note, I'm trying to fix part of this mess myself by writing a Microsoft Teams library (and later a / multiple clients) so that I can finally use without complaining about it: https://github.com/fossteams/teams-api
reload
What are some alternatives?
msbotbuilder-go - Microsoft Bot Framework SDK for Go
go-dotenv - A minimalist library for reading and atomically writing .env configuration files in Go
teams-cli - A CLI / TUI for Microsoft Teams
xdg-go - Go implementation of the XDG Base Directory Specification and XDG user directories
dusupay-sdk-go - Golang SDK for Dusupay payment gateway API (Unofficial)
pterm - ✨ #PTerm is a modern Go module to easily beautify console output. Featuring charts, progressbars, tables, trees, text input, select menus and much more 🚀 It's completely configurable and 100% cross-platform compatible.
fasapay-sdk-go - Fasapay payment gateway XML API Client for Go (Unofficial)
log - Simple leveled logging wrapper around standard log package
go-reddit - Go library for accessing the Reddit API.
mockit - Library that make mocking of Go functions/methods easy
teams-token - A super simple Electron app that will save your Microsoft Teams tokens
options-gen - Codegen for functional options in go projects