HN user

mig_

16 karma
Posts4
Comments16
View on HN

Ext4 is most certainly still in use and not a toy. Its trusted. It takes a lot for folks to adopt a new file system.

I worked on a research topic in grad school and learned about holes in files, and how data isn’t removed until the last fd is closed. I use that systems knowledge in my job weekly.

A tip. Kernel development can be lonely, share what you are working on and find others.

But what if Googles model is to make personal data useless the root cause businesses and therefore kill off your business.

To kill off the root cause, Google could feed peoples privacy data into the SSO ranking. Websites with a lot of privacy data get a lower SSO. This cripples the business and with it, your business.

Just a hypothetical, I wish all the best for DeleteMe. I'm checking out optery.com right now and will check DeleteMe next.

"Don't be evil" I think may still be true and may actionably translate to "Don't sell user data _directly_"

Two theories.

1. Google already does a good job of filtering out email addresses. I remember searching email addresses I was curious about 5ish years ago and getting results. Today, I get far fewer hits. So my theory is that google is already attempting to sort of scrub peoples email addresses from their searches. Us filling out the form is feedback to the machine learning.

2. Google wants to corner the market on this information and this is how they bleed the companies out. (I don't they have _actually_ devoted enough resources to this to bleed the other companies out) The business motive? There isn't a particular offering this data is good for besides selling to 3rd parties besides the business Google is already in. This data could enhance other data sets for other offerings. As simple as "auto-complete" for phone number after you have entered your name or address fill after entering your phone number.

Thanks you! With COVID, I found myself calling the local health department hundreds of times a day. After day 2, I found myself deep in the world of asterisk. I figured out how to build a service similar to the one you are providing, but it damn sure wasn't easy. Wish I had found you a few days ago!

Can you talk about the stack you used? I used asterisk + questblue. I got asterisk running in a docker container. I still want to play with ASI.

Websocketd 7 years ago

The initial fork is fast because of the copy on write memory semantic. You'll pay a price later.

With arbitration, for the company, worst case the company pays the original amount. Without arbitration, in the court, worst case is the company pays the original amount + the clients lawyer fees.

Before the deeper evaluation we simply made a table of pros and cons of all the different databases. Below are what we considered the pros and cons of CouchDB for our use case.

Pros:

  * Projection feature
     address “weird” Ansible data format requirements.
     allow for a more compact and logical structure to be presented to the api.
  * Built in support for compaction
  * Built-in versioning
Cons:
  * couchdb versioning may not align with our notion of versioning
  * Requires a lot of space
  * Views instead of arbitrary queries
  * Performance not so predictable. (see how reads trigger version logic) (Colleague has had experience with this problem)
Edit: I found some other notes ...
    CouchDB appears to be a strong candidate. I am worried about the space requirements/consumptions. CouchDB uses views of data rather than queries.
Database comparison by feature matrix: http://i.imgur.com/6bdIvwE.png