Nama is pretty good and for more traditional DAW workflows, greatly simplifies using ecasound at some cost. Would love to see ecasound start getting developed again.
Edit: was comparing nama to ecasound there, not the more common graphical DAWs.
Images of what it's supposed to look like would really help, as I'm pretty sure none of my browsers are rendering it as you hoped. For me in Chrome the first image looks vaguely like a landscape, with no identifiable features, and in Firefox it looks like grass (both on Android). The dog and tree shapes look distorted and glitchy, but recognisable if you know what they're supposed to be.
I think your volume per bill should be 6.14 * 0.0254 * 2.61 * 0.0254 * 0.00011 ≈ 1.137e-6 m³. That means about 227 m³ total volume, or about 2800 wheelbarrows.
For me on desktop there's no info other than "Henge Finder requires a desktop or laptop computer" (Chrome/Edge/Firefox on Windows, not exactly uncommon!).
The following in the browser console will enable it:
They long pre-date the demoscene, going back centuries in mathematics. Ray tracing/casting of implicit surfaces (described with SDFs and more general signed functions) for computer graphics goes back to the 1960s and 70s. The 1990s demoscene 2D metaball effects were based on computer graphics work by Jim Blinn for Cosmos in 1980. Most current applications are based on that long ongoing research. (I did my PhD in implicit surface stuff, so I've seen tons of academic papers on it going back ages, and I never ran into demoscene methods in that context.)
Not sure about SDFs, but ray casting/tracing goes back a long way being used to design sundials thousands of years ago. A method of ray casting was published in the 1600s to show how to trace out the outline of the Moon on the Earth during a solar eclipse.
I can tell you how we approach enterprise partnerships: absolute accountability. If something is wrong with the data, it is not our customers' fault for trusting us, it is our fault. End users talk to us directly. And because the data is so good these days, we just have to present evidence, that's it.
We with multi-billion-dollar corporations, and for every product integration we maintain an active, visible presence in their user communities.
Customer support teams are encouraged to build support pipelines that either route data-related questions directly to us or send users directly. We remove friction rather than hiding behind layers of enterprise support.
We make a deliberate "account manager for everyone" effort when introducing ourselves to a partner's user community. We engage with influential community members and MVP users and encourage them to contact us directly when issues arise. We also connect with the engineers who work hands-on with our data and make it clear that they have a direct line to our engineering team.
We actively and aggressively monitor social media for reports of issues related to our data within partner platforms and engage with users directly when something comes up.
To be honest, this is not difficult. Once or twice a month, we may need to present evidence to a user to explain our data decision.
This is not a paid add-on or a special clause in an enterprise contract. Our customers do not pay extra for this level of engagement.
Developers hold us in high regard. Maintaining that trust requires ongoing investment of time and resources. We fundamentally believe developers trust us because of the quality of the product and the lengths we go to provide clear, honest explanations when questions arise.
90% of end users, not 90% of your customers. If your product blocks 10% of end users because it provides wrong geolocation data to your customer, sucks to be them!
That is a great point! For us, it is 100% of end users not limited to our customers. If you are impacted by our data in any way, it is on us. We are accountable for that.
Our free database is licensed under "CC-BA-SA" (freely distributable but requires attribution) because of accountability. If you use our data as an enterprise or a free open-source project, if there is any issue, you can come to us and talk with us.
It is not even end-users. We maintain open communication policies in general. Even if a streaming service does not use our data, if they come to us, we try our best to help them based on our industry knowledge.
How can somebody who is blocked from (looking at your homepage) Docker Hub or Microsoft know that the reason they are blocked is that you have wrong data on them? How would they know to ask you? If they ask Docker Hub or Microsoft, they'll get funnelled into the "well it works for 90% of people" funnel.
Also the reason most IP information companies don't do this is the obvious risk of false information. I am currently in Somalia via a remote connection via Germany. Actually I'm not, but if I emailed you and said I was, how would you know?
And alcohol wipes. Just the other day someone stopped to give me alcohol wipes after I put my chain back on. The alcohol cleans off the grease completely, unlike paper towels. I'm carrying a pack in my car now.
I’ve started waxing my chain rather than oiling it.
It’s a hassle, but doing 2 at a time means the admin is much reduced.
There is a huge amount less dirt and grease in my life now. Even when I change it to re-wax it I don’t get dirty. I probably get 2-3 weeks, 500-600km out of each waxing.
Interesting. My usual approach at home is actually to put a few drops of cooking oil on my hands, which dissolves the grease; regular soap can then remove the oil.
I already have some alcohol wipes in my bag as part of an emergency medical kit. I'll add a few more for grease emergencies. :-)
reply