Metacrane
Metacrane client for Sailfish. (https://metacrane.com/)
Also available at Harbour, but new versions arrive first here because of Harbour's approval lag.
NOTE: Version 1.0.8 is not in Harbour because it uses features that are not currently approved in Harbour. What it precisely needs is libnemotransferengine-qt5.so to appear here: https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/harbour-qa...
Features
- Browse uploaded items
- Upload and download files and text
- Copy URLs easily to clipboard
- Upload directly from Gallery (You can leave the app in the background so that it doesn't pop up annoyingly)
Changelog
1.0.8 (2015-07-07)
- Allows easy copying of file URLs and texts using the item context menu
- Uses the nemo transfer engine to allow uploading files directly from Gallery. (this is not yet allowed in Harbour, so this release is not available in the Jolla store.)
- Every page now goes to landscape mode
1.0.7 (2014-03-09)
- Image thumbnails in file picker
1.0.6 (2014-03-09)
- Possibility to select multiple files for upload
- User-settable deletion time
1.0.5 (2014-03-08)
- Show items with varying height to fit content
1.0.4
- Don't reset file picker path every time it's opened
- Edit About page
1.0.3
- URLs are parsed to tappable links
1.0.2
- Modify some stuff in order to possibly reach harbour compatibility
1.0.1
- Sailfish-styled icon (curved corner)
1.0.0 (2014-03-06)
- Restore connection if it fails
- File upload with upload progress indication
- More useful cover page
0.4
- Support text upload
- New items appear at correct end of list
0.3
- Use new protocol
- Sync item deletions to screen
- Make things look reasonably good
- Save visited cranes on start page
- Allow copying texts and links
0.2
- Umm... I guess something maybe works
Source releases
Screenshots:
Category:
Application versions:
| Attachment | Size | Date |
|---|---|---|
 harbour-metacrane-0.4-1.armv7hl.rpm | 60.23 KB | 04/03/2014 - 19:51 |
| harbour-metacrane-1.0.0-1.armv7hl.rpm | 70.77 KB | 06/03/2014 - 02:11 |
| harbour-metacrane-1.0.1-1.armv7hl.rpm | 71.27 KB | 06/03/2014 - 02:38 |
| harbour-metacrane-1.0.2-1.armv7hl.rpm | 70.72 KB | 06/03/2014 - 18:30 |
| harbour-metacrane-1.0.4-1.armv7hl.rpm | 71.24 KB | 07/03/2014 - 13:14 |
| harbour-metacrane-1.0.5-1.armv7hl.rpm | 71.22 KB | 08/03/2014 - 20:02 |
| harbour-metacrane-1.0.6-1.armv7hl.rpm | 72.14 KB | 09/03/2014 - 06:55 |
| harbour-metacrane-1.0.7-1.armv7hl.rpm | 72.29 KB | 09/03/2014 - 13:07 |
| harbour-metacrane-1.0.8-2.armv7hl.rpm | 849.54 KB | 07/07/2015 - 20:06 |
Changelog:
(none)
Comments
Kabouik
Mon, 2018/07/16 - 17:42
Permalink
I think Metacrane breaks the new sharing system that comes with Sailfish 2.2.0.29. Any plans to update it?
celeron55
Sat, 2017/04/08 - 21:54
Permalink
Ok this is just stupidly lazy but I FINALLY set up https://kristaps.bsd.lv/acme-client/ to get us some certificates.
Everything seems to be working, so, eh, enjoy, I guess!
objectifnul
Wed, 2016/03/09 - 16:33
Permalink
Time to update certificate:
This Connection is Untrusted
We can't confirm that your connection is secure.
metacrane.com uses an invalid security certificate.
The certificate expired on 28/02/2016 21:14. The current time is 9/03/2016 13:31.
(Error code: sec_error_expired_certificate)
objectifnul
Fri, 2016/01/08 - 18:22
Permalink
Currently (January 7, 2016), https://metacrane.com/ => 504 Gateway Time-out (nginx/1.7.12)
Edit: metacrane is back (January 8, 2016)
objectifnul
Thu, 2015/10/15 - 10:17
Permalink
Service discontinued?
celeron55
Thu, 2015/10/15 - 13:31
Permalink
Uh oh - the server software seemed to have gotten stuck somehow. Restarted it and everything works fine again.
celeron55
Tue, 2015/07/07 - 20:30
Permalink
Looks like the source packages got lost in a switch to another VPS provider; I'll have to take care of that at some point. EDIT: Okay, done!
EDIT: New openrepos-exclusive release! (while waiting for Harbour to allow using the Nemo Transfer Engine.)
objectifnul
Sat, 2015/02/28 - 20:21
Permalink
metacrane.com uses an invalid security certificate. The certificate expired on 26/02/2015 15:36. The current time is 28/02/2015 17:20. (Error code: sec_error_expired_certificate)
Jordi
Thu, 2014/09/11 - 09:57
Permalink
I use this app almost every day. Donation is ongoing!
rolfa
Thu, 2014/05/01 - 01:45
Permalink
I have my own vserver and would be interested to run your software on the server for private use. Any chance you would let me do that?
celeron55
Thu, 2014/05/01 - 03:48
Permalink
The server is built on a library/framework that hasn't been intended for public release, so I'm not too eager to do that.
I'd at least need to strip all unused parts of it off and... bleh.
celeron55
Fri, 2014/04/11 - 22:25
Permalink
vasvras: Done.
This has a very small effect on overall security though. There are simply too many things that can go wrong.
It is one of the reasons why I wanted to set this up as an anonymous service. It only stores your file, your IP and the upload date, so there isn't much to worry about. You should encrypt your files with a tool that you trust if they contain something that the public shouldn't see.
Metacrane was affected by the heartbleed bug via its reverse-proxying Nginx server. I haven't yet gotten a new certificate because I'm lazy. I will report here once done (maybe in a few weeks). I'm currently looking at options on how to minimize the future risk of these kinds of problems.
celeron55
Sat, 2014/05/31 - 16:40
Permalink
I have decided to not revoke and renew the certificate, because it will cost me $25 and frankly that's not worth it. I will use a new key when I renew it in February 2015.
vasvras
Sat, 2014/04/12 - 12:37
Permalink
Thanks.
You should probably revoke current certificates and generate them with new keys, since its been proven now that private keys were leakable.
vasvras
Fri, 2014/04/11 - 16:58
Permalink
Looks great.
One request: Could you add HSTS support to metacrane.com?
https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
celeron55
Fri, 2014/03/28 - 14:55
Permalink
rolfa: It uses only port 443, and unless using the website (which uses HTTPS), it only uses the secure websocket protocol (websocket over TLS) over that.
I will not make any workarounds for proxies that disallow such connections because it's a pain in the ass and it's becoming an increasingly common way of doing stuff in any case.
Useful and accurate information about websockets: http://www.infoq.com/articles/Web-Sockets-Proxy-Servers
rolfa
Fri, 2014/03/28 - 13:56
Permalink
very useful!
However it does not seem to work behind a corporate proxy. Message "Disconnected". Only ports 80 and 443 are allowed with this proxy. Does Metacrane use different ports and could you please fix it?
Jordi
Mon, 2014/03/10 - 01:57
Permalink
In one word: Superb!
Jordi
Sat, 2014/03/01 - 14:11
Permalink
Like the idea, will give it a try.