asabla

If it's essential that I attend for such a meeting, the organizer usually reach out.

If not. Then I'll have to either live with the decision or at least give feedback on it.

Nothing is final until you build it (from a developer point of view).

> no agenda, no attenda

I've been using this mentality for the last three years. Some responds with hostility and some see the benefits, but most are just indifferent to it sadly.

I've also been observing people just throw in a short sentence or some AI generated shit list which is then not followed during the meeting.

But those who take this seriously usually have pretty darn good meetings (e.g not book the full hour, force people to stay on topic, shares notes after the meeting etc)

> LLMs for code review, rather than code writing/design could be the killer feature

This is already available on GitHub using Copilot as a reviewer. It's not the best suggestions, but usable enough to continue having in the loop.

I remember when they presented the S10, with the initial implementation of Dex.

It felt so close already back then, sluggish, but still usable. But that initial implementation was running some in-house version of Ubuntu with a custom kernel (if I remembered it correctly).

I just wish this becomes a reality much sooner then later. Especially if I can have my dev environment on some remote VPS with either tunneling, github code spaces or Azure DevBox

most services has a "studio mode" for their models served.

As an alternative you could always use OpenWebUI

oooooh, thanks for sharing.

It's exactly what I was looking for

> And if other vendors sign on to support MCP, then it becomes a self reinforcing cycle of adoption

This is exactly what's happening now. A good portion of applications, frameworks and actors are starting to support it.

I've been reluctant on adopting MCP in applications until there was enough adoption.

However, depending on your use case it may also be too complex for your use case.

for someone that comes primarily from a .net background. This looks fantastic!

Just one thing that I tried to find more information about is: are you suppose to rely on the prefix for specifying api version?

Disclaimer: I'm on a phone while writing this, so I just might have missed something obvious

other then that, kudos for releasing this package!

> there's a Profiles revamp coming up that's looking really good in Nightly

Oh wow! I totally missed this. Thank for sharing!

I've been using multiple browsers for as long as I can remember. But always liked Firefox ocer the others. Especially now with container tabs.

And the only thing I keep wishing for, has been a better experience with profile management, but also running the browser in different profiles.

I'm really looking forward for these updates

Some of the most goofiest scenes reminded me about my self growing up, recording dumb re-creations of movies/tv-shows with friends.

I had a blast watching that! thank you for sharing.

He was doing everything from his phone. But the community got together and donated enough money for him to buy a laptop.

I think he posted an appreciation post on reddit about it.

Neither the less, it's quite an achievement. Especially when it was a well received plugins

Why would you tho?

If you're working against an GraphQL based API, you should be able to pull a schema file. And use that to implement your own API.

All you would get from an Mitmproxy is example queries and mutations. With the additional complexity of extra tooling to stich together the schema file

Before articles about this started to show up on the web, I've noticed that my weekly suggestion playlist (which refreshes every monday) sometimes had music with either low quality or encoding artifacts (just like AI music).

But after reading about this phenomenon, I also started to dig deeper into which artists were actually suggested each week. And to my surprise there were quite a bit of artists I've never heard of, and were hard to find further information on.

Hopefully Spotify won't touch weekly release playlist (the one which refreshes every friday) of artists you already listen to and have saved into personal playlists.

more like hug of death from HN users. Since the site is back up and working again

Seems like an alright experience then. Thank you for sharing

I've been eye balling a pair of those for a while now.

Any other quirks you're willing to share? Such as: how's the input latency (from key press to seeing it)? early signs of tear? do I need to invest in spare parts?

Oh, this looks pretty well made. Since it's using nextjs and shadcn/ui, I wonder if they also used v0 to generate components.

Has anyone any experience with TiDB? Haven't heard about it before this post

at some extent I do agree with the point you're trying to make.

But unless you include pagination needs to be handled as well, the LLM will naively just implement the bare minimum.

Context matters. And supplying enough context is what makes all the difference when interacting with these kind of solutions.

Title might need to include "Show HN".

Very cool and interesting project! How are build times? And how big are the artifacts?

I'll for sure keep an eye on this, and add it to my ever expanding list of tech to explore.

Thank you for sharing!

Damn, that's some impressive speeds.

At that rate it doesn't matter if the first try resulted in an unwanted answer, you'll be able to run once or twice more in a fast succession.

I hope their hardware stays relevant as this field continues to evolve

This looks really interesting and could really be a nice addition to my daily work.

I just downloaded the application, but are unable add OpenAI API keys. Looks like it's probably on my end (with quite an aggressive DNS blocking lists). So my guess here is: I'm unable to add API keys when telemetry is blocked.

Suggestion: please do add some error message when then this occurs. As in, did the request fail (500), faulty key etc

Sorry about the late response. Thought I already had pushed it, you can find it here: https://github.com/asabla/gogent

As you can see, it's in a very early stage. I'm not a go developer, and I use this repository as a way to explore things both within Ollama and with go.

I'll probably add more things as the time goes by, but it isn't something I hack on every day or for that matter week. Just something to poke around and explore things with.

Since you prefer go, you might be interested in one of my pet projects. Where I've glued together some libraries, which lets you basically code all interactions with LLM's through lua. The project is written in go.

Currently it only supports ollama, but I've been thinking about adding support for more providers

Built a couple of things with Semantic Kernel. Both some private test projects, but also two customer facing applications and one internal.

It's heavily tilted towards OpenAI and it's offerings (either through OpenAI API or through Azure). However, it works decent enough for other alternatives as well, like: huggingface or ollama. Compared to the others (CrewAI etc). I kind of feel like Semantic Kernel hasn't really solved observe ability yet. Sure you can connect what ever logging/metric solution .Net supports, but it's not as seamless like the others. Semantic Kernel is available in .Net, Java and Python. But it's quite obvious .Net is a lot more polished then the others. Python usually gets new features faster, or at least pocs or previews.

Some learnings from it all:

- It's quite easy to get started with

- I like the distinction between native plugins and textbased ones (if a plugin should run code or not)

- There is a feeling of black magic in the background, in the sense of observe ability

- A bit more manual work to get things in order, compared to the alternatives

- Rapid development, it's quite clear the development team from Microsoft is doing a lot of work with this library

All and all, if you feel comfortable with writing C#, then Semantic Kernel is totally a viable option. If you prefer python over anything else, then I would say llamaindex or langchain is probably a better option (for now).

edit: updated some formatting

I don't see it like that at all. Some 0-days can (somewhat) be mitigated by other hardware/software.

I rather have as many "known" 0-days in the open. Then having it the other way. Even if it means I won't see any updates to affected devices or software

Ooh, this looks like a lot of fun. Really hope they'll either have recordings and/or stream this event.

Alright, thank you for sharing. Then I'll just hope either Skyler or Brian wants to share their story some day here on HN

Just want to say thank you for your contribution. A lot of the wonky stuff made it really funny to watch, but at the same time impressive (for what it was).

Do you have any links to share about details surrounding the project? Would be fun to understand more about the process but as well the work in general.

edit: fixed some weird autocorrects

It's going to be interesting to see what Wendell finds out about the oddities on Windows.

I think with this CPU it will also be the first time I'll no longer dual boot for gaming, or for that matter have a dedicated Windows machine only for gaming.

I wonder if go ever will get some sort of enum type? Or if int/string based types will be the goto way?