lhdj

My company switched to Fathom from GA about 4 days ago.

We build privacy software so it felt slightly hypocritical to use a privacy-intrusive service like GA. So far so good.

I went from 0 to Fathom in under 20 mins and for our basic requirements it works really well .

Good job Fathom team :)

Data privacy is an engineering problem - and currently there aren't any really good open-source tools to 'solve' data privacy - it's really up to the application developer to make sure they don't mess up. If the organisations is sufficiently large there is a CISO to ensure the correct processes are in place so that this sort of thing does not happen.

I think in an ideal world data privacy should be addressed by open-source software enabling software developers to easily express data privacy as code and version control it and review it much like we do with our infrastructure.

There is an product [0] which is currently in Alpha aimed at doing this. (Full disclosure I am one of the core devs) We don't support S3 buckets yet - but it's on the roadmap.

[0] https://github.com/openquery-io/parallax

Not really a database - but Parallax[0] is a data warehouse geared at private/sensitive data written in Rust - it allows you to perform data anonymisation at query-time.

Furthermore it exposes a privacy-as-code framework allowing you to version control and be very granular about how different entities interact with your datasets.

I'm on the core team - if you have any questions I would be more than happy to answer.

[0] https://github.com/openquery-io/parallax

I started a company while also learning Rust. It seemed like the right choice given that we needed something which emphasized memory safety and was also blazingly quick, but I was essentially forced onto it while dealing with the pressure of having to deliver on tight deadlines.

Our core tech is in pure Rust and I have to admit that coming from Javaland it's refreshing to deeply trust your code. It's hard to convey this idea of 'if it compiles it works' but I no longer worry about showing off prototypes to people. If they compile they work.

There is a learning curve as you are introduced to new ideas and design patterns but it's worth it! Rust has made me a better programmer.

Hey HN. We're Christos, Damien and Nodar, founders of OpenQuery to answer any questions you may have.We've spent the past few months working tirelessly developing a distributed query engine for dealing with sensitive data.

The project skeleton has just recently come together and we couldn't wait to share it with the community.We want to take the technology we've developed with Parallax and push it in the right direction solving real-world problems. If there are any particular use-cases you'd like us to look into we would love to hear about them!

I was literally developing the exact same thing (I called it Novid-19 [1]). While testing it out on HN, I saw a post filtered out.

It was this post...

[1] https://github.com/christoshadjiaslanis/novid-19

Shift-Click to create a node.

Then click on the node to modify it's attributes.

Shift click and drag to other nodes to create dependencies. The dependencies should auto-snap into place. The algorithm used for this works most of the time. Our current taskgraph at openquery has ~50 nodes and it works quite well.

I don't have cycle-checking so be careful or your browser tab will blow up.

Looks really good!

Here is an open-source version I made called TaskGraph [1], a fork from uber/react-digraph[2]. I made it for my startup [3] because I didn't really like Jira in the context of 3 people.

We have been using it for a couple of months and it works really well. Apologies in advance for the lack of documentation. If you have any questions by all means.

TaskGraph has:

- Task status (todo/in-progress/done)

- Task completion estimation (admittedly it assumes you can work perfectly in parallel which is a bit of a stretch.)

[1] https://github.com/openquery-io/taskgraph/

[2] https://github.com/uber/react-digraph

[3] https://www.openquery.io/

I really haven't researched this topic very much. It was a case of implementing as fast as possible.

Take a look at my repo for how it's implemented; it is not the most responsive site in the world.

What I can tell you is: 1) display=none is a good idea 2) Certain sites have the HTTP header 'X-Frame-Options': BLOCK' or something along those lines. Modern web-browsers wont render those pages in iframes 3) It's a good idea to add sandbox="allow-forms allow-scripts" on every iframe to stop top-level redirects.

I have noticed that it is quite heavy, and my phone's browser handles this for me under-the-hood by saving pages to disk when the iframe is collapsed (I think. I haven't actually tested this but the performance would suggest that this is the case.)

Interesting. Would get really heavy with 100 pages. I may implement a feature where you can pick the number of pages you want.

I agree. Feel free to contribute to github. If not, will implement requested features soon.

I made this last weekend over my frustrations at not having access to Hacker News when on the tube (I live in London).

Its a webservice that concatenates the top 25 hacker news links in one page as iframes (the ones that allow it). I usually load the page 1-2 minutes before getting on the underground. It has minimum functionality, but works for my needs. I use it mostly on Chrome mobile browser.

I thought some of you might find it useful.

Repo: https://github.com/christoshadjiaslanis/hacker-cache