<gwillen>
dwrensha: counterpoint: I agree with you and loathe the thing where backspace goes back
<gwillen>
because 100% of the time that it happens, it's because I thought I was in a form field but wasn't, so I just destroyed my form contents by accident
<funwhilelost>
Totally agree on backspace. 100% of the time it's a facepalm in the middle of a form.
<XgF>
=/
<XgF>
for me 99.99% of the time its' I want to go back
<funwhilelost>
Interesting. I'm usually resting on the command/shift keys (go to 1st tab, go to next tab, forward in history, back in history, etc. are all within reach)
funwhilelost has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
eternaleye_ has joined #sandstorm
eternaleye_ has quit [Quit: Konversation terminated!]
jadewang has quit [Remote host closed the connection]
jadewang has joined #sandstorm
paroneayea has quit [Ping timeout: 240 seconds]
jadewang has quit [Read error: Connection reset by peer]
jadewang has joined #sandstorm
isd has quit [Quit: Leaving.]
jadewang has quit [Remote host closed the connection]
isd has joined #sandstorm
jacksingleton has quit [Ping timeout: 264 seconds]
<gwillen>
after installing an app, the ?highlight= parameter in the URL causes the app to dance again if I click 'uninstall' and then again when I click 'done uninstalling'
<gwillen>
not an important issue but looks a bit silly
<gwillen>
Bigger issue: When I installed Davros, I'm pretty sure I got an interstitial that just said "Install this app?" and had zero indication of what it was insstalling. But I can't reproduce it now because the interstitial doesn't happen again even after removing it and reinstalling it
rhapsodhy has quit [Remote host closed the connection]
rhapsodhy has joined #sandstorm
ArcTanSusan has quit [Quit: ArcTanSusan]
ArcTanSusan has joined #sandstorm
jacksingleton has quit [Ping timeout: 240 seconds]
<gwillen>
Davros bug report-ish (not sure whose fault this is, but) -- the OS X ownclid client has an 'Open in browser' option, but it directs me to https://alpha-api.sandstorm.io/, which is of course not useful.
<gwillen>
[btw let me know if it's irritating that I'm reporting bugs over IRC instead of through some bugtracker somewhere]
<gwillen>
[but if I had to be honest it's probably this or nothing]
jadewang has quit [Read error: Connection reset by peer]
jadewang has joined #sandstorm
isd has quit [Read error: Connection reset by peer]
<zarvox>
Hmmm, yeah, I guess "Open in browser" is never going to work.
<gwillen>
zarvox: well, it seems like it ought to be possible to make it work in principle...
<gwillen>
you could make an API call to the grain to ask it where to point the link
<gwillen>
not clear whether it's worth the effort, but being able to get to the online management interface from the menubar seems like a pretty good feature
<zarvox>
gwillen: grains don't have a way to link back to themselves, though!
ArcTanSusan has quit [Quit: ArcTanSusan]
<zarvox>
It does seem like a good feature, though it'd probably require changes in the owncloud client that upstream seems unlikely to merge, given their discussion on https://github.com/owncloud/client/pull/3712
jadewang has quit [Remote host closed the connection]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 260 seconds]
isd has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 252 seconds]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 250 seconds]
isd has quit [Quit: Leaving.]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 240 seconds]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 252 seconds]
ocdtrekkie has quit [Remote host closed the connection]
aldeka has quit [Remote host closed the connection]
aldeka has joined #sandstorm
ocdtrekkie has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 265 seconds]
achernya_ has quit [Read error: Connection reset by peer]
gilli123 has joined #sandstorm
achernya has joined #sandstorm
gilli123_ has joined #sandstorm
achernya has quit [Ping timeout: 244 seconds]
gilli123 has quit [Ping timeout: 246 seconds]
jadewang has joined #sandstorm
achernya has joined #sandstorm
jadewang has quit [Ping timeout: 250 seconds]
xet7 has quit [Read error: Connection reset by peer]
achernya has quit [Ping timeout: 244 seconds]
achernya has joined #sandstorm
gilli123_ has quit [Read error: Connection reset by peer]
jadewang has joined #sandstorm
gilli123 has joined #sandstorm
jadewang has quit [Ping timeout: 250 seconds]
bb010g has quit [Ping timeout: 264 seconds]
bb010g has joined #sandstorm
ArcTanSusan has joined #sandstorm
ArcTanSusan has quit [Quit: ArcTanSusan]
decipherstatic has quit [Remote host closed the connection]
TC01_ is now known as TC01
notevil has joined #sandstorm
jadewang has joined #sandstorm
bb010g has quit [Quit: Connection closed for inactivity]
ocdtrekkie has quit [Remote host closed the connection]
aldeka has quit [Remote host closed the connection]
ocdtrekkie has joined #sandstorm
aldeka has joined #sandstorm
jadewang has quit [Ping timeout: 252 seconds]
gilli123 has quit [Read error: Connection reset by peer]
<zarvox>
mnutt: I'd be curious to know what changes to the mobile clients would be necessary to make them work with Davros atop Sandstorm (or even OwnCloud itself atop Sandstorm if someone were to package it; it'll have the same issues)
<mnutt>
zarvox: the issue with the owncloud ios client is that owncloud actually has two requests it makes when it sets up a connection, one to /status.php which is supposed to be unauthenticated and one to /remote.php/webdav after you have entered the credentials. We get around this on desktop by using https://username:password@example.com for the server URL, and qt is smart enough to pass along the credentials to /status.php, and then you
<mnutt>
set up username and password on the next screen and the initial creds get overwritten. This works, but is hacky and requires two tokens, one of which is only ever used once.
<mnutt>
the problem with the ios client is that if you use https://username:password@example.com it expects to get a 401 challenge from /remote.php/webdav and errors out, disabling the “submit” button. If only we could hit the “submit” button it would all work.
<asheesh>
Seems like something that could also be fixed in a patch to the iOS client.
<asheesh>
FWIW.
<mnutt>
it’s fixable, but we have to rely on owncloud team merging a PR and getting it into the app store.
<asheesh>
Also hi, I'm a little tired and sick, so I might not be operating at 100% today, so if I say things that are obvious or nonsense, let me apologize in advance for that.
<mnutt>
I think there’s a solution that would also make the desktop client smoother while not targeting Sandstorm specifically; I suggested it and will see if I get any buy in before I work on it
<zarvox>
We'd have to whitelist the iOS app's user-agent to trigger that codepath
<asheesh>
"Obviously" this behavior switch about 401 etc. should be configurable by the app
<zarvox>
Do you know offhand if that's owncloud-specific, or if that's justing using the iOS platform one which could possibly render HTML and such elsewhere, and thus would be unsafe to whitelist?
<asheesh>
I guess the problem is we have a whitelist not a blacklist, so we can't trust the app to do secure things.
aldeka has quit [Remote host closed the connection]
ocdtrekkie has quit [Remote host closed the connection]
jadewang has quit [Read error: No route to host]
jadewang has joined #sandstorm
notevil has quit [Quit: Leaving]
ocdtrekkie has joined #sandstorm
aldeka has joined #sandstorm
neynah has joined #sandstorm
<mnutt>
jadewang: speaking of skitch, another idea I had for a sandstorm app was to replace an app I use called CloudApp that lets you ctrl-opt-v to replace an image in your clipboard with a link to that image, uploaded to their servers. It makes for a handy shift-ctrl-cmd-4, ctrl-opt-v, cmd-v to send someone a screenshot.
<neynah>
+1 to that mnutt, that would be super useful
<neynah>
I'm having trouble finding a good way to share mock-ups & get feedback using Sandstorm apps.
<neynah>
Lychee is the better image gallery app but doesn't support comments. Wekan squeezes images into a limited height but has comments. (Although images are pretty tedious to upload)
funwhilelost has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<neynah>
Davros is really awesome for uploading graphics quickly but doesn't have a gallery view. (If it did then I would probably use Davros)
<asheesh>
I totally want Dillinger today
<neynah>
It's difficult to view non-square mock-ups on Davros without having to download them.
<mnutt>
I’d love to get someone from core’s feedback on if it would make more sense to build a gallery inside davros, or use powerbox to let davros expose its files to a gallery app.
<asheesh>
Theoretically I want to say "powerbox" but we don't have a way to share files between apps yet. But paging dr. kentonv
<kentonv>
mnutt: great question. I am not really sure! Powerbox will ensure that someone else can offer a better gallery without forking Davros, but there's an argument to be made that bundling a gallery view into Davros may be useful to users.
<kentonv>
but of course there's also an argument that it's bloat and keeping things simple has advantages
<kentonv>
so I don't know
<mnutt>
yeah, can probably come up with some way to modularize a directory view for different overlays, but was just curious if powerbox would somehow let me call out and say “I need a gallery, here are some images”
<mnutt>
if it’s more like intents it may be harder, depending on what the data passing looks like
<eternaleye>
That reminds me, I need to poke at CapnProto-izing 9p
<eternaleye>
All sorts of uses for that
<eternaleye>
(Though, some incompatible changes would need made to preserve proper capability behavior, like removing the ".." traversal)
<kentonv>
that sounds neat
<eternaleye>
kentonv: Yeah, I figure that 9p is already a good proxy for any number of APIs, especially ones that benefit from reads and writes to bytestreams
<eternaleye>
kentonv: In addition, promise pipelining and caps basically eliminate the need for FIDs and TIDs
neynah has joined #sandstorm
<kentonv>
eternaleye: Yeah, I find a lot of protocols which have complicated designs for the sake of latency reduction suddenly become much simpler as Cap'n Proto, since the latency reduction schemes tend to map nicely to promise pipelining.
<kentonv>
eternaleye: note that I have some plans to extend Cap'n Proto to make the ByteStream interface more usable. The basic idea is that the write() method would be declared as a "streaming" method, which means that the application does not receive notification of completion but rather notification of when it is a good idea to make another call, with Cap'n Proto then managing flow control through this
<eternaleye>
kentonv: I consider 9p2000.L (and fuse) overcomplicated abominations :P
<kentonv>
you discover if previous write()s completed by calling some other method, e.g. done()
<eternaleye>
kentonv: Plain 9p2000 (and _maybe_ 9p2000.u) to be vastly better
<eternaleye>
kentonv: As opposed to shoehorning the mess that is the Linux VFS into what was a clean protocol
<eternaleye>
kentonv: Also, I'm wary of that in terms of 9p-like stuff - errors need to be reported precisely in terms of the causing operation.
<eternaleye>
kentonv: To see why I hate 9p2000.L, compare the 9p2000.L "getattr" operation to _anything_ in the base protocol