1,691 karma · joined April 15, 2014
With the Grafana Loki UI the main issue is if you log perfect JSON / logfmt and Loki parses it, the Grafana UI can struggle a bit with rendering views of logs in the way you'd want. Kibana's columnar views with nice filtering UX is much easier to use. I think Elastic still has this over Loki (that, and the capacity to build big expensive indexes if you have the stomach to manage them).
I wrote a custom CLI for Loki to work around this, because the Loki CLI has a similar problem. All that said, I'd still recommend Loki, it's really good IME.
You wrote that you don't like Loki's LogQL, but it looks quite similar (Victoria's LogQL first):
log.level:error _stream:{app!~"buggy_app|foobar"}
{app!~"buggy_app|foobar"} | "log.level:error"
The pipes are arguably a bit noisy in Loki queries (compared to spaces in Victoria's), but I find they do make the queries a bit more readable, and it's easier to understand under the hood how the queriers will handle the query, and coming from PromQL I found Loki's approach quite intuitive: https://grafana.com/docs/loki/latest/query/.Maybe I missed something fundamental though, interested to hear more about the differences, since I only read the couple links you shared!
This article is an interesting companion to "No more pink mustache" [1] wherein Lyft is described as "broken at a scale that is hard to believe" - often the explanation for quality is the org, not the human in the chair :-)
There was story last year in the UK, where the power usage of data centres in west London were blamed for a lack of housing development. This turned out not to be true and an exercise in blame-shifting [1]
[1] https://www.computerweekly.com/news/252523510/Datacentre-sec...
I absolutely think we are going to get out of this by making money.
The incentives preventing action on climate change are not moral/ethical, but economic.
Countries and individuals use fossil fuels because they are cheaper, and are unwilling to make decisions that put them in a worse position relative to others.
While de-growth naively sounds appealing, the results are horrendous – countries with approx. the same GDP that they had 20 years ago are not places you would want to move to.
You might also point to the ozone layer issue in the late 80s and argue an accord will fix our current problem, but fossil fuels are far more fundamental to our way of life than CFCs were.
Tl;dr = Climate change is best addressed by producing technology that makes things more efficient and/or that helps the developing world decarbonise.
If anyone is working on something gamechanging please hit me up -- I'm happy to help out on the dev / infra side pro bono.
Y Combinator is actively looking for founders starting climate tech companies: https://www.ycombinator.com/rfs#climate-tech
It sounds like the worry is this overfit generative AI will spew out some private input verbatim… which I can see happening honestly. Look at GitHub copilot, it’s almost a copy paste machine.
> If you do hope to stay, expect to keep spending. The low-cost luxuriating necessary for healthy third places isn’t considered profitable.
A lot of people struggle with this after college and a social club (sport, dining etc.) is usually the best way to keep your social life going. But yeah you usually have to value and invest in it, which maybe people aren't doing so much as prices have increased in the physical world while prices for entertainment over the wire has decreased.
I also think communities (third places FTA) that enable these friendships need to be, to some extent, closed or invite-only. I feel like as a social network grows each individual edge is a little weaker, which is the reverse incentive of developers of social networks and explains why socialising over the Internet feels the way it does.
* https://github.com/hashicorp/nomad/forks
* https://github.com/search?q=nomad%20fork&type=repositories
* https://www.google.com/search?q=hashicorp+nomad+forks
There are products that do similar things of course.
> So, yes, greening is complicated. It’s not inherently good. Sometimes it’s very bad. Context, it turns out, matters a lot.
The tone suggests they're afraid of the change, but the article can't articulate why since the reason for the change and result are both possibly good and bad, but we don't really know yet.
The NASA MODIS project is ongoing and produces data that people are using to measure "greenness" (which the article indirectly cites) and has been going for 20 years https://en.wikipedia.org/wiki/Moderate_Resolution_Imaging_Sp... - it's definitely an interesting dataset.
Didan seems to be leading the vegetation research for MODIS and the data set has been cited thousands of times (https://scholar.google.com/citations?user=TxQK6U8AAAAJ&hl=en...)
This is what I mean -- previously I built a similar search engine on top of slack, notion, etc., but didn't launch the product because I thought that requiring users to constantly add bots to private channels would be a subpar experience. I thought this would be a blocker for good UX, so didn't go further, but maybe you'll find a nice solution!
Searching over public internal data is addressed by a few existing tools, but it's the private aspect which is pretty difficult to handle and disastrous to get wrong when managed ad-hoc - e.g. someone accidentally adds the bot to a private slack group called #layoffs :) so you'd want this handled properly and centrally.
I guess you'll also need to handle privacy well, ~maybe it's OK when run as a SaaS for db admins to have access to ingested data, but if it's OSS then the people that run it probably shouldn't be able to read the private data that's ingested, so now you need to handle search over encrypted data, which is a fun problem :D
I guess the main problem is the "private" aspect, if I've understood your goals correctly. Since most SaaS products lock down the private data unless you pay enterprise fees for compliance tooling.
For instance, if you want to ingest data from private Slack channels or Notion groups, you have to get the users in those groups to add your bot to them, otherwise there's no way of your service getting access to the data. It's possible, just a bad UX for users.
That said, built-in search for most SaaS products built after 2015 is generally quite good (e.g. Slack has an internal Learning to Rank service for a while now, which makes their search excellent: https://slack.engineering/search-at-slack/), so you'd be solving for companies like Webex and Confluence where their internal search is not great. At companies like Google they have internal search across products, which is the ideal end state, but have the benefit that they own the source code for most of their internal products.
To my mind an "x product" is rarely the framing that will lead to value being added for customers. E.g. a web3 product, an observability product, a machine vision product, an AI product.
Like all decent startup ideas the obviously crucial thing is to start with a real user need rather than wanting to use an emerging technology and fit it to a problem. Developing a UI for a technology where expectations are inflated is not going to result in a user need being met. Instead, the best startups will naturally start by solving a real problem.
Not to hate on LLMs, since they are neat, but I think most people I know offline hate interacting with chat bots as products. This is regardless of quality, bots are rarely as good as speaking with a real human being. For instance, I recently moved house and had to interact with customer support bots for energy / water utilities and an ISP, and they were universally terrible. So starting with "gpt is cool" and building a customized chatbot is to my mind not going to solve a real user need or result in a sustainable business.
Regarding your second point, the way congestion avoidance algorithms typically work is to punish the local client for the state of the global congestion. If Remy can do that in a more efficient way (ie greater throughput or fairness for the local client) then it would be beneficial to use the algorithm before others switch.
“The Intergovernmental Panel on Climate Change concludes that it is the most-researched solar geoengineering method, with high agreement that it could limit warming to below 1.5 °C”
There’s a risk it’d affect the ozone layer. But Paul Crutzen, who won the Nobel Prize for his ozone research in 95, said the sulfur plan is “the only option available to rapidly reduce temp rises and counteract other climactic effects”.
We’d also need to add shockingly little SO2 to the stratosphere. We currently emit 200m tons per year (25% is humans, rest is volcanos and other natural sources). We’d need to add an extra 100k per year.
Edit: I think one of the Microsoft co-founders was looking into it, the problems of proving it would work were political - not engineering-related.
Of the two options for sustaining human civilization (AI singularity/human-computer integration and space exploration) colonizing other planets seems to me more fun and less likely to fundamentally alter/end humanity.
I’d be curious if anyone here is working on these challenges
Also, you can still get EV Nova on a Mac as far as I'm aware. The price hasn't decreased in about 20 years though.
One thing I thought would be cool would be an API for similar blogs or articles, pretty much opening up an internal part of blogosphere. I think one could use that to provide a webring.