Currently the framework does not support puppeting the matrix user, that is being bridged.

That means that using the framework also involves keeping track of an additonal matrix client/api in order to puppet this user as well. It also requires own code to decide in which way an event is supposed to be handled - either relaying the message via the framework (relay_service_message) or relaying it as the real user (again, having to write own code for submitting messages and room events via the matrix api since the framework cannot masquerade a user not in the user-namespace).

Do you have any plans or ideas regarding this already ?

i.e. when sending a matrix message there should be a "create_room_and_send_message" type method, which handles all the steps needed to send a service message into matrix.

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/matrix_discord_bridge-0.0.1.dev0-py3.6.egg/appservice/app.py", line 179, in on_message
    return await self.handle_discord_message(message)
  File "/usr/local/lib/python3.6/site-packages/matrix_discord_bridge-0.0.1.dev0-py3.6.egg/appservice/app.py", line 109, in handle_discord_message
    room = await self.create_new_room(auth_user, service_roomid)
  File "/usr/local/lib/python3.6/site-packages/matrix_discord_bridge-0.0.1.dev0-py3.6.egg/appservice/app.py", line 154, in create_new_room
    room = await self.apps.create_linked_room(auth_user, service_roomid, matrix_roomname=channel_name)
  File "/usr/local/lib/python3.6/site-packages/appservice_framework-0.1.0-py3.6.egg/appservice_framework/appservice.py", line 879, in create_linked_room
    query_params={'auth_token': self.api.token})
  File "/usr/local/lib/python3.6/site-packages/appservice_framework-0.1.0-py3.6.egg/appservice_framework/matrix_api.py", line 74, in _send
    async with request as response:
  File "/usr/local/lib/python3.6/site-packages/aiohttp-3.3.2-py3.6.egg/aiohttp/client.py", line 843, in __aenter__
    self._resp = await self._coro
  File "/usr/local/lib/python3.6/site-packages/aiohttp-3.3.2-py3.6.egg/aiohttp/client.py", line 317, in _request
    with timer:
  File "/usr/local/lib/python3.6/site-packages/aiohttp-3.3.2-py3.6.egg/aiohttp/helpers.py", line 662, in __enter__
    raise RuntimeError('Timeout context manager should be used '
RuntimeError: Timeout context manager should be used inside a task

The AppService get initialised in a similar fashion to the way it is done in the hangoutsas:

    def run(self):
        self.apps = AppService(
            matrix_server=self.args[CPNs.MX_HS],
            server_domain=self.args[CPNs.MX_HS_DOMAIN],
            access_token=self.args[CPNs.MX_AS_TOKEN],
            user_namespace=self.args[CPNs.AS_USER_NS],
            sender_localpart=self.args[CPNs.AS_SENDER_LOCAL],
            room_namespace=self.args[CPNs.AS_ROOM_NS],
            database_url=self.args[CPNs.DB_URI],
            loop=self.loop, # in class __init__: self.loop = loop or asyncio.get_event_loop()
            invite_only_rooms=self.args[CPNs.AS_INVITE_ONLY_ROOMS]
        )

        # service_connect handler and user creation snipped 

        with self.apps.run() as run_forever:
            run_forever()

Any idea why this is happening ? Any idea on how to troubleshoot it or information you would need to fix/give help ?

Currently the framework supports relaying images (w/ m.image message type). What about m.file ?

When implementing relay_service_file, should it be and additonal method (similar code structure to relay_service_image) or should the relay_service_image method be renamed to relay_service_file with added support for custom message type (file, image) and maybe custom content_pack/info parameters ?

We should support the ability to have one service user and have the AS invited into rooms, i.e. telegram / gitter bridges

For post new messages to AS-managed rooms, AS user must be a member (maybe with admin permissions?) of all rooms.

But sometimes it can not be a member of room:

• If this room was already exists before AS is added to server (eq if user use other AS with same sender_localpart and replace it to new AS).
• If user kick manually this user from room.

In this situations now AS shows the error:

matrix_client.errors.MatrixRequestError: 403: {"errcode":"M_FORBIDDEN","error":"User @hangouts:homeserver.org not in room !uJsAiCcPjyKuXTJHTo:homeserver.org (None)"}

And when user try to manually invite @hangouts user to room - we got another error:

appservice_framework ERROR    Membership event received, handling is not yet implemented.

For solve this problems, we must implement managing membership events (for accept manual invites of AS user to rooms), and force joining AS user to managed rooms, if it missed in room member list.

Along the lines of telematrix we should store a mapping of events on the service and matrix side, this would allow for relates_to linking and also things like read marker / timestamp syncing.

On startup of we should iterate over all the rooms in the database and query their state, things like names, members, if the rooms still exists etc.

This will probably need some extra service side hooks.

Should support a way to define all the __init__ parameters of the Appservice class as well as providing easy ways for users to specify custom config for the service they are using.

Hello:

I'm willing to write a appservice for a game server lobby (SpringRTS)
I would like to help develop this project as I ee it has a lot of potential
but I'm pretty lost :D is there a room where we can talk?

Thanks

edit: what I need is a transparent bridging from matrix to springrts ( not behind a bot (I already have this))

Most service libraries have the timestamp of the message on the service side, we should support passing this to matrix.