cetra3

We do use facial recognition to detect the faces in the photo, and then integrate with the school's student management system to work out what permissions or media consent has been granted for each student.

From there you can identify whether the photo overall is publishable, and if not, what students aren't. You can then crop/edit the photo to remove students from then on.

All of this happens in an on-premise VM, rather than calling out to a cloud service. Obviously you can run up an instance in AWS, etc.. if you want to cloud host, but that is the school's volition.

Schools are finding that this is a problem, but haven't had the ability to manage it. So we have built a product to address this very issue (https://www.schoolbench.com.au).

SchoolBench allows you to match profiles with media consent, so you can work out what photos are able to be published or not.

I'm talking about a shared private/public key for everyone which gets changed when members leave or enter.

Would just deriving a new pub/private key each time someone entered/left the chat be simpler? I'm assuming there is a reason why this wouldn't work.

I tried to find a good comparison to PDFBox but came up short!

I use it all the time to whip up quick scripts. The other day I made a cli tool that allows you to use Jmespath syntax for yaml files.

Memory management aside: compilation-time guarantees of your code is probably the best thing about the language.

The dealbreaker for me is no strongly typed templates. I have built big-ish apps (10-20k loc) in both React/Redux & Angular 6+ and I feel that there is still a lot of unsoundness in Angular 6 that I don't need to worry about with React & TypeScript.

I would be interested in knowing whether anyone else has confirmed these accusations or created a writeup as to why the protocol is insecure.

Sure, if Apple have fixed their issues with Keep-Alive for Safari:

https://stackoverflow.com/questions/25372318/error-domain-ns...

I'm assuming there is no source for this?

Our product is basically written in Rust (~40k LoC) [1]. When I say basically: there are a few backend components that are written in Java (i.e, ActiveMQ) and the frontend is TypeScript/React, but it is mostly Rust.

[1]: https://www.schoolbench.com.au/

We implemented WebDAV (rust/actix-web) for our product and it's great that you can mount it as a mostly native file system on all major OSes, but there are a lot of issues with Implementation:

* Windows sometimes appends a `/` at the end and sometimes doesn't when looking for folders, so you better make sure you return the same results for either.

* Windows WebClient service is buggy as hell. You have no event logs (that I could find) to find out what's wrong and end up restarting the service continuously. this includes if you get your username/password wrong, if there is an interrupt to the server (i.e, wifi drops), etc.. Wireshark is your friend, but it won't tell you why it's not working.

* Forget about Basic Auth on windows, credentials are not persisted across reboots/logouts, and you need to adjust registry to support non-ssl sites at all. Using Kerberos is really your only option, but if you want to use it on non .local domains, then you need to add in a registry key to allow this, as windows assumes that only .local domains would use SSO.

* Last time I checked, Adobe Lightroom won't even save to a WebDAV drive on OSX as it thinks there is no space.

* Lots and lots of noisy connections on both windows and OSX that aren't really needed, but happen anyway. Don't get me started on the amount of temp files that are saved/used, and don't filter them out either as things start breaking like Photoshop and folder uploads.

* Weird error messages that don't give you an idea of what's going on. Error code 100000041? Oh yeah I know what that one is!

* URL size limitations in Windows, make sure your entire path isn't too long!

All in all I am glad we have WebDAV for native-like access, but it is a massive pain to deal with some of the niggly bits between implementations.

I think Azul is definitely promising, but it's still alpha level, when I first tried to run it on OSX Mojave I got a nice black screen: https://github.com/maps4print/azul/issues/35

The next time I ran it, it worked on release mode, but panicked on debug mode.

I've just tried again from master and it works, which is an improvement!

For a security library to have no updates in a couple of years, I would consider it to be unmaintained and a huge risk.

I don't doubt that 2016 had some great libraries in rust, of which a lot are still used today. But most of them are updated to use new language features like `?` instead of `try!`, new macros system, async libraries, etc..

Take a look at a library like `serde`, which has been around since 2015 (https://crates.io/crates/serde/versions) and is awesome.

Are you talking about the crate `crypto` or `rust-crypto`? Both have not been updated in a couple of years.

The `ring` library is a bit more modern, but still requires a bit of a run around. Here's an example of encrypting a cookie: https://github.com/alexcrichton/cookie-rs/blob/master/src/se...

I have looked at the repo and the website and I have no idea what this is or what it's targeted at.

It's a cross platform something?

If you use systemd, you can use standard packages from your distro to run up services inside a container. That's basically the only reason I considered it.

I second using runit. We use runit to be able to use the same service definitions inside docker, on a VM or bare metal.

If you've ever tried to use systemd inside docker to bring up a couple of services, you would know the hoops you have to jump through to get it working.

(I understand that docker wasn't invented to run multiple services in the one container, but sometimes it can't be avoided and simplifies app deployment vastly I.e, using CI to test your service actually starts up as per its definition: just run up a quick docker image with runit and a service definition file)

Also worth mentioning is Toshi: https://github.com/toshi-search/Toshi

Toshi is to ElasticSearch as Tantivy is to Lucene if that makes sense.

Obviously as they are new they are not at feature parity, but Tantivy does win at some benchmarks: https://tantivy-search.github.io/bench/

We store our logs in PostgreSQL and use Metabase for visualisations & analysis: https://metabase.com/

It's still focused on SQL but the "Question" flow is quite simple, and doesn't require you to write SQL. You can, of course, write raw SQL if you want to and have those results still visualised.

We're doing something similar for school archive photos in our product. We use class photos to find student labels, then use that to cross reference other photos around the same time period.

It would be nice to see benchmarks between the versions.

I am assuming that this should be faster since it uses react's "proper" API?

I used to believe that the language didn't have any gauging on the quality of code, but I personally feel that coding in rust has made me a better and cleaner programmer, and I trust my team's rust code more than I do its java code.

It's definitely an anecdotal observation though.

I love TypeScript and use it in any new project I create. The author is right though, you need to have team discipline to avoid using the `any` type when it can be avoided, and immutability is not in scope. TypeScript is probably the closest we'll get to my personal ideal of static typing in JS, while understanding that you sometimes need an escape hatch to deal with dynamic typing as JS is a dynamic language.

I think that the focus now should be allowing other more modern languages in the browser by means of Web Assembly. Rust is a great candidate for dealing with immutability and unsoundness concerns. I can't wait for wasm to be fleshed out more.

It does beg the question though, would web development be as ubiquitous and as popular if the core language in was statically typed? Does the freedom JS offer you allow greater adoption overall, meaning that it's beneficial to loosen the type restriction as the ecosystem will flourish because of it?

If you're using this in your site as it stands, you are opening up XSS attacks as it does not appear to sanitise user input.

Just be careful about XSS: https://itty.bitty.site/#/?XQAAAAIhAAAAAAAAAAAeHMhnVbtj2LI97...

Code is here I believe: https://github.com/guxd/deep-code-search

I'd be interested to hear more about this. Is there a writeup somewhere?

Surprised noone has mentioned OnlyOffice here: https://www.onlyoffice.com/.

We use it via the integration I wrote for Alfresco: https://github.com/cetra3/onlyoffice-alfresco

Yes HTTP2 supports Multiplexing: http://qnimate.com/what-is-multiplexing-in-http2/