carlio

I still cling on to the quaint idea that "upvote" means "adds meaningfully and coherently to the discussion", while "downvote" means the opposite. So not "I agree with this" or "that made me chuckle" but rather "this enhances the conversation" - and especially if it's a well written argument I disagree with because that might make me learn or rethink my position. Humour in a well argued point is very welcome, of course.

Wish and reality aren't in alignment here but some places like HN or /r/AskHistorians are my refuges.

There's always been a general pushback on HN against turning threads into a series of quippy oneliners. It tends toward having a serious discussion about a topic, rather than farming low-effort humour for upvotes. I consider this a good thing, as there are plenty of other places where that is rewarded.

minio is an S3-compatable object store, the linked s3mini is just a client for s3-compatable stores.

"Something went wrong. Please try again".

Do you suggest not doing it then?

While you might be able to continuously update the model, are you able to continuously update the moderation of it? As the article says, it takes time to tune it and filter it; if you allow any content in without some filtering of outputs you might end up with another Tay. You'd have to think the liability would slow down the ability to simply update on the fly.

Also, if the proportion of training data available is larger for more established frameworks, then the ability of the model to answer usefully are necessarily dictated by the volume of content which is biased towards older frameworks.

It might be possible with live updating to get something about NewLibX but it probably would be a less useful answer compared to asking about 10YearOldLibY

It takes too long to iterate on a character design.

For more explanation: I've been playing around with stable diffusion on my laptop recently; I have a gtx 4070 with 8GB dedicated VRAM so it's not nothing.

The main problem I have is that it takes a lot of iteration on a prompt to get what I want, at lower resolution and sampling steps, before I know that I'll get roughly what I want.

I tried making a character in Eggnog, and before I could be sure what I was getting, it told me it'd take 15-20 minutes to be ready. I worry that this will just make me wait a long time for a character that isn't what I want, and starting again too many times will put me off.

The iteration and feedback loop needs to be tighter in my opinion, or people will get unsatisfactory results and be unwilling to go back and fine tune.

I think you're talking about spinning up a temporary environment running the code and connecting via a local IDE to inspect it, whereas OP is talking about hosting the IDE remotely.

I use InfluxDB for this, it comes with a frontend UI and you can configure Telefraf as a statsd listener, so the same metric ingestion as datadog pretty much. There are docker containers for these, which I have added to my docker-compose for local dev.

I think it does log ingestion too, I haven't ever used that, I mostly use it just for the metrics and graphing.

I work as a contractor so I move between places. I have found a few companies trying to introduce kafka, and every time it has been a solution in search of a problem.

I don't doubt that it has a good use case but I have so far only encountered the zealots who crowbar it into any situation and that has left a residual bad taste in my mouth. So I fall into the "hate it" side.

Final Fantasy 7. It was the first story-driven game I played as a teenager and it changed how I thought about games.