wyattjoh

Software Eng. with The Coral Project[0] here. Feeling a little odd with the same color (even the logo a bit) + name combo used for their TPU as we've used for The Coral Project for years now..

[0]: https://coralproject.net/

Would really love to see Privacy.com come to Canada now that Plaid announced support[0]!

[0]: https://blog.plaid.com/plaid-in-canada/

From what I understand, this isn't a problem for users on iOS who haven't given microphone access to the offending apps right?

It's this exact situation why I decided to write a tool that integrates with the CF API [0].

[0]: https://github.com/wyattjoh/cloudflare-ddns

How would you represent more complex types? It would work fine if your models are flat and containing only POD, but if it contains something like GeoJSON (from Postgres for example), it would be pretty difficult to ensure that the serialization works properly.

Are you using something like Vault [0] for that? Always been interested in different approaches for this.

[0]: https://www.vaultproject.io/

The builtin golang.org/x/crypto/acme/autocert [0] package manages SSL for you easily through Lets Encrypt.

[0]: https://godoc.org/golang.org/x/crypto/acme/autocert

I'd think that Pachyderm [0] would be mentioned in the article, but it wasn't. It uses Docker under the hood for the data pipelines. I've always wanted an excuse to do some data science...

[0]: https://www.pachyderm.io/

Typically, unless I'm writing a shared library, I find myself putting everything under a `internal` folder. It keeps people from importing possibly unstable code until it's exposed.

The numbers were roughly based on aggregated values across all our current partner companies working with us. Most of these orgs have not imported their historical data either, however they all have added support for integrating their own custom auth services into Talk, as that whole layer is pluggable, hence you might get most of the users auto-added with low participation.

The ease of use of the moderation system as well might mean that more bad comments are pushed out of the system, making it full of more higher quality discussions.

One of the pillars of Coral is to provide lots of research to assist orgs develop community strategies[0], I'd suggest taking a look if you're interested!

[0]: http://guides.coralproject.net/

You can certainly use the tools for anything you like! We have been focused on working with newsrooms, where we feel we'll make the most impact. You can use the Ask tool to build a form, or Talk to power your comment space.

Once we reach better adoption, and we have seen quite the adoption (just today The Intercept launched[0]), we'll be able to focus on improving the landscape further.

[0]: https://theintercept.com/2017/12/18/comments-coral-project/

Developer with The Coral Project here.

Schnack seems to provide a simple solution to the "let us put some comments on the site" in a very simple and pleasantly small package. (Like seriously small, we're jealous of those numbers :))

Talk on the other hand provides a full admin panel for moderators, a robust plugin system for configuring every part of the experience.

Admittedly, not every small blog is going to need all of our features. If you want comments to work on your small site, Schnack seems to suit that role fine. Talk on the other hand is currently supporting millions of users and tens of millions of comments. It's a matter of scale really, both are great solutions that take the data out of a marketers hands.

Wish I didn't have to open Chrome to view websocket frames though. Firefox does detect that a WS connection was made, it just can't inspect it.

I have an old release of Photoshop, didn't even install it because it demanded such an old version of Java.

Also Talk [1], which you can self host! (Disclaimer, engineer on the team!)

[1]: https://github.com/coralproject/talk

One of the features offered by Talk is the ability to ignore comments from a specific user [1]. It is designed just as you described it here. As mentioned in a previous comment, our server api's should be sufficient for you as a site administrator, to write a plugin that would allow users to do exactly what you described. The idea with Talk is that we hand control to the newsroom, so they can enable or create the plugins that they like.

[1]: See a demo GIF on https://www.washingtonpost.com/news/ask-the-post/wp/2017/09/...

As a site admin, not a user. If you see our server side plugin api [1] you can see ways to extend the graph schema, hook into existing mutations/queries completed by the system to apply any set of rules or moderation policies you want. It would be a neat implementation if as a user, you were given the ability to create your own filters, which would certainly be possible if implemented via a plugin! But don't expect to do that on WaPo anytime soon.

[1]: https://coralproject.github.io/talk/docs/plugins/server/

Good site also to check out is our Guides [1]. We've collected research on user engagement into a format that should be easy for newsrooms to adopt to create better discussion.

[1]: http://guides.coralproject.net

Believe it or not, you can! Check our the documentation https://coralproject.github.io/talk/ where you can use plugins to hook any any part of the commenting process.

The advantage of our technical solution Talk [1] is that we provide a flexible plugin layer. The benefit is that tools like the Perspective API [2] that provide machine learning tools to augment the experience. So really, we're providing a framework for newsrooms to attach more sophisticated tooling to solve the issue from both a technological perspective and a social one.

[1]: http://coralproject.net/products/talk.html [2]: https://www.perspectiveapi.com

Not at all. The software Talk [1] it installed on newsroom's infrastructure. We only provide the software the makes this all work.

[1]: http://coralproject.net/products/talk.html

Wyatt from the Coral Project here. It's all about the news rooms owning the data of the comments, not social networks like Facebook. We're using tech like GraphQL to make the experience possible on multiple platforms through our extensible and pluggable API.

Completely agree. I'll often take a look at the "top in-app purchases" as well. "$9.99", ok, but if I see a "$129.99" for a "big crate of gems"...

I just got to question how the developers felt that it was morally acceptable to create a toxic enough app experience that drives users to use in app purchases through deceptive tactics during the first few minutes of play to go and drop +$100 on virtual gems.

I think an advantage could be if you wanted to push the message from a lambda function into a google cloud pub sub topic which a google cloud function would consume possibly?

I doubt that hyperdunc was directly referring to the idea that:

> women, in particular, are statistically-significantly less strong at the software engineering industry

I think that what was they indicated was that because individual strengths may vary, because there likely isn't a strong balance of genders in the workplace. It would be obvious that due to different strengths of individuals that there would could be an apparent bias.

Up in Canada this little company made SimpleTax. Our family + friends used to use other paid solutions, but this was actually free. Great to see people helping other people =D

https://simpletax.ca/

Considering the product video described it as being a tool for system administrators, I'd hazard a guess at yes.

> Generics

I was concerned by this at first as well, but after using Go full time for the past two years, I've never found a need/use for them. Go doesn't lean towards strict OO principles, where I feel that most of the Generics uses are applied (Arrays, sorting, etc.).

Not everyone's opinion, just my two cents.

The use of `go run` here makes adopting this very hard. The benefit of using Go for projects (in my experience) is that you can build for multiple OS/Arch super, super easy. I'd thin that having uploaded artefacts would be the first thing most people do when releasing Go code into the wild that is meant to be consumed by someone just wanting to run the program.

Not having this featured built into NGINX is the reason why I transitioned my production servers over from it to Caddy. Having SSL just "dealt with" is the biggest time saver ever.