Open jacobian opened 10 years ago
Yup, I agree. For formatting, do you think this makes sense?
[19:50:05] jacobian: this is a message I sent.
The most attainable of these is a .txt
download for your buffer. However, that is only your buffer – not logs while you were connected to that network/device. An API is possible but buffers can get big (20,000+ messages) so I'd have to understand how that may work with pagination, etc.
Separately, the idea of supplying some storage service credentials for us to log all messages to requires a bit more thought. I'm personally eager to do it (I have multiple local clients too), just need to understand how it fits in for us.
@pearkes sure, that format works; there's about a million ways you could do it, that's easy and simple and fine.
The buffer thing could make it tricky to get logs with the interest of archiving them, but I don't think it'd be impossible. Tricky to script, but I'm totally willing to put some effort into that if it means I get a feature I want :)
Service credentials, at least for S3, are fairly easy: you can set up a AWS account and have people grant that account access to a bucket they create. You never have to see any AWS creds (other than your own), and people can scope that restriction to a single bucket (and remove it at will). It's a pretty nifty feature!
I'd love to have a way to be able to archive my logs (yes, I know I can configure my local client to do that, but I have multiple local clients.)
Some options I can think of:
All of these would be great.