Paul Evans
Paul Evans
* Use constructor-method `meta::package->get` rather than purely functional `meta::get_package` * Added `meta::glob->get` * Actually specify the "meta::package" and "meta::glob" package names * All packages exist; `->get` will lazily create one....
The original design had functions such as ```perl my $metapkg = meta::get_package("some::name::here"); ``` A suggestion from the mailing list was that these could instead be written as constructor-style methods on...
The original text did not explicitly mention that regular `$foo` interpolation does not work here, but it seemed implied so I've added some words. I've also added a guess at...
Users have expressed an interest in being able to give the bridge their gitter-side user credentials so that it can puppet for their actual user account instead of relaying messages...
This issue split out from #31 If we hypothetically had the ability to perform an OAuth2 dance with synapse and give `matrix-appservice-gitter` a token to puppet for matrix-side accounts, this...
Currently, every matrix-side ghost user maintains presence state for all of time. If you don't restart the bridge for a while, this constant accumulation of users starts creating even more...
It seems that gitter clients have to prepend their own username (or displayname) when sending "/me"-style status messages, because the server doesn't prefix that for you.
If gitter users post messages that contain links to github (projects, repoes, issues, etc...) then the message text gets truncated nicely for a neat short name to display in gitter....
Attempting to join by name a Gitter room that doesn't exist, has the side-effect of persisting the "name to ID" association in the HS before it fails to join. This...
Gitter message markup allows inline images in the flow of text. Matrix does not. We should work out how to transport these. This /might/ require adding matrix spec support for...