XMPP Service Operators - 2019-08-27

I was going over the spec for http_upload

Would it make sense to add a TTL to the standard so you can optionally set an expirey policy?

for exmaple PUT https://upload.someserver.com/file&v=someauthcode&ttl=6300

tom, yes, I think it would make sense (though it would probably be part of the slot request, not the URL - the server generates the URL)

But the server operator may want to put an upper limit on retention time

and then it starts to get complicated, as we also have quotas (limits in size, rather than time)

Most servers are already expiring old user uploads, but they all have different policies about when and how

may I point out that pea has been connecting and disconnecting at least two times per minutes for quite a while?

mathieui, the way I currently do it is I delete all files that are more than 30 days old with a bash oneliner in a cronjob

0 5 * * 1 find /var/www/upload.mydomain.com/htdocs/* -mtime +30 -delete

wait

is it the XMPP server itself that keeps track of user quota or the upload server's job?

I would think it's the XMPP server because that's the thing generating the unique upload auth codes

that would also make sense why the newer version also verifies mime and size upload-server side in case the xmpp server had upload filtering policies and with the current version implemented in perl, you could bypass upload policies with a modifed client because the auth code is still code even if you send different data that what you told the XMPP server you would send