jereze

No mention of DuckDB? Surprising.

Yes, I started learning drawing as an adult with zero natural talent. For me, it wasn't about becoming exceptionally good but about exploring and finding pleasure in the process. I took drawing classes following the "Drawing on the Right Side of the Brain" method, which I highly recommend.

Even if we are close to peaking emissions, we must consider the phenomenon of accumulation. Given that CO2 has an effective lifespan of around 100 years and methane about 10 years in the atmosphere, reductions in emissions now will still result in these gases accumulating and impacting the climate for decades to come.

Well, such an optimistic title, considering that greenhouse gases are excluded in the article.

And they emphasize on their stability. https://www.11ty.dev/blog/stability/

I appreciate your perspective, and you bring up a valid point about the potential for the clause to alienate users.

Could be more manageable:

* Implementing a broad clause that reserves me the right to decline clients.

* Setting standard pricing for the general market.

* Offering discounted licenses to entities that I choose/like.

This tiered approach might be easier even though I was hopping for another route. It lacks of transparency compared to a public clause.

Thank you for contributing to the discussion.

I absolutely recommend it.

How do you create your components in Jinja2? Using the include tag?

Now that we have a consensus, let's address the discourses justifying inaction or inadequate efforts. I just submitted a resource that I like on this topic. https://news.ycombinator.com/item?id=28941473

I made first tests with Timescale 10 days ago with logs of a website. First result, I was impressed by the compression: 13GB of compressed CSV files - 1 PostgreSQL table of 63GB - 1 Timescale hypertable of 4GB. Then, I saw improvements on the performance of my queries, between 23% and 92% faster on the hypertable versus the table. This is definitely interesting and I will look into it further. I'm getting from "it's not a good idea to put weblogs on Postgresql" to "why not, if it helps simplify our infra".

I take this opportunity to share a workflow I created for searching on Salesforce: https://github.com/jereze/alfred-salesforce

It leverages Salesforce REST API and it runs entirely locally.

Thanks :) I have few paying customers. I run it as a side project in my spare time.

It sounds familiar to me since I too have built a micro-SaaS that could probably make it in Zappier: https://sheet.chat to integrate Google Sheets in Slack

I'm also very curious about this.

Maybe they hash the IP address. But hashing personal data does not guarantee truly anonymisation. This ressource have more details on the topic: https://cnpd.public.lu/content/dam/cnpd/fr/publications/grou...

I had exactly the same experience.

Algolia implemented a retry strategy on a different domain, TLD, and provider in their API clients. See step 14 of this article: http://highscalability.com/blog/2015/7/27/algolias-fury-road...

Complicated to apply to a website, but it gives some thoughts.