benjaminbenben

https://flights.benjaminbenben.com/

I’ve been playing around with aligning drone footage to flight paths. I'm really interested in the idea of representing a video as a volume, planning to do something similar with non-drone video too.

We use this for summarising our hack day write ups: https://remotehack.space/previous-hacks/

It's a tiny script that looks up the rss feed and uses the content to generate summaries; quite a nice fit with our static site. Sometime I'd like to extend it to ask different questions about the content.

Yep. When the credentials were used earlier on in the session they'd been scrubbed from the logs - so there's some checking, but not on the code that's committed.

I was manually reviewing when I saw it. Was looking through the PR more out of interest than worried that there'd be a problem tbh.

If you pair this with a eink display you could send messages back and forth with another device https://remotehack.space/QR-TX/

I've been working on https://stacks.camera - it's an idea about overlaying the previous picture when you're taking a photo so you can create a timelapse or animation.

For example, you can scroll through 60 pictures from my window https://stacks.camera/u/ben/89n1HJNT

Most of the challenges are around handling images & rendering, but I've also been playing with Passkey-only authentication which I'm finding really interesting.

We've been running this since March last year.

It started as a "traditional hack day" with themes, teams etc, but we've morphed it into a more casual get together with random people working on fun stuff. We'd love to get more people involved!

I've been working on this over the last couple of weeks. The idea is that you can can start a session (click the number at the bottom and choose "independent"). Then other devices can subscribe to it (by entering the id as 'other').

I've built it for: * demos during talks * workshop/hack sessions

…seems to work okay so far, but I'd love to know what people think.

I saw Mariko give a talk about this last week - http://2016.render-conf.com/talks#drawing-on-canvas-a-few-th...

It was absolutely fantastic; really great information about image data & how to process it.

Yeah, there is a bit of an overhead with that. Module server - https://github.com/google/module-server seems like quite a good solution. Though I'd agree, for a large number of sites it's far better to bundle them up.

Ah, I've not had to deal with sharing between multiple elements yet - I'm kind of hoping that when I do require.js would give quite a solid base for it. YepNope seems like a good choice for this kind of thing, especially that it can bring in css assets too. Would be awesome to bring in all related assets for a element

I wrote this post - feels like quite a simple approach. Would love to hear if anyone has done anything similar.

I didn't. That's fantastic - exactly what I needed; added it and gone back down to 2 dynos.

I went to 5 and was still seeing a lot of errors, so upped it to 10.

That's the minus sign on the bottom right - it's for zooming the css list so that it's all in view (it was originally built to see if appended styles were more specific on a page).

yup, it's just overloaded at the moment. It's serverside using phantomjs - I'm running it through cloudfront so the common urls are cached there.

thanks. Yeah - it's not as useful as something like css profiler, I built it to work out if there were ways that I could architect my css in a more efficient way.. Though it looked cool, so I threw it online!

yeah - there were issues in FF dealing with large data-url embedded images in a json file. I'm looking into it though.

document.stylesheets - https://developer.mozilla.org/en-US/docs/Web/API/document.st...

The main part of the injected code is https://gist.github.com/benfoxall/5647039 - there's a bit of hacking round cors issues there too.

Yup - It's been falling over quite a lot in the last couple of hours! It is all served through cloudfront so that the popular urls get cached (which is why I added the example links - so they would hit the cache). I've just thrown a whole load more heroku dynos at it, so it seems to be working okay again now!

(I built this!)

Good point, another approach could be to use a templating system where the ui is bound to a js object like knockout.js or angular.js.

Ah, cheers - yeah, it serialises the image as a data-uri in the json which seems to be erroring in FF. Need to find a better way of doing that.