soorajsanker

Wasnt loading for me

yeah, looks strange though!

yeah strange that status.anthropic.com is also not resolving and failing on a cert issue :p

That format shift is exactly the mechanic. Summary-first structure isn't just reader UX — it's how you get your passage into the top-k chunks that actually reach the model's context window during RAG retrieval. The chunk that gets cited is usually the one that answers the query in the first 2-3 sentences, standalone, without needing surrounding context to make sense.

The news sites doing this probably aren't optimizing for AI citations intentionally — but they're converging on the same structure anyway because it works for skimmers and for models. Same underlying reason.

Are you talking about the difference between 0.0.0.0 and 127.0.0.1 /localhost (loopback address)? If so It should be a tiny thing to change to implement I can add that on the next update- I just went with the express JS defaults to keep things simple:)

Or I can even make a flag to configure this :thinking

What are the main specific issues that you felt difficult in viewing logs on a browser? imagine there is better visualisation, parsing, highlighting, filtering, collapse etc.? I feel like the terminal is where I spend more time looking for the relevant parts from the logs.

Ahh actually you can do search through the logs in real-time, I forgot to split that and remove TODO from the readme. Complex filtering based on the timestamp is yet to implement.

Sure thing! The collaboration with ChatGPT was like having a friendly coding buddy. I threw in ideas, got feedback, and we built this tool together. We chatted about names, features, and even how to post it. It's like having an AI pal who's great at brainstorming and coding. Fun times!

^ asked Chat GPT to generate this from my earlier prompts :)

Some other notes, I am a developer who love to make usable products, and these years I learned the usability is most important especially when you are developing in the early stages of a product. So I fed some ideas, asked suggestions, gave some tech stacks (for example, I asked chatGPT to not go with webpack, instead simply load React from CDN for quick iteration. and suggested memoisation on React to render things faster). So process wise similar to any other product development, but it's like having someone listen to your feedback and instructions and do the work- I would like to call collaboration!

Simply suffix with any unix commands that emits stdout, ` | npx logscreen` (need npx though)

Haha yeah, I wanted to frame this as a single file tool, and hence all the quick wins. But later moved the react app into a separate file because I was not getting the syntax highlights and all.

Definitely this can be made better with proper packaging and tooling! As I mentioned, more than the idea, implementation was an experiment on the ability of collaborative iterations with GPTs- it was fun!

True, This was also a personal experiment in understanding the level of collaboration that someone can do with GPTs during the product iterations.

Depends on the size, for me it worked well with decent size JSON log lines, but if it is too much that doesn't fit on the browser memory, can think of index storage of sqlite in the future. Search and filtering can be then loaded to the server + sqlite setup.

I don't think the impact would be much on software sector.

Hey there!

I am very excited to share DB lens (https://dblens.app) with you all!

I used to spend more time understanding data relationships, long-running queries indexing, index usage, sequential scans, Disk usage, etc. and there was no single tool that provides all these pieces of information.

I decided to build an application that provides more insights about a database simpler than ever!

Idea was to identify & develop the most wanted insights that engineers would want when they connect to any DB.

DB performance is something many people would want to understand most, and there are a lot of parameters that control the overall performance of a DB. I decided to list down & filter the information based on how much impact it would make on the database. Also, understanding data relationships is another area where developers spend more time with. And it was a pain when you want to quickly jump onto some databases or schema that you want to debug.

I added a simple ER diagram page which will simplify this effort.

SQL execution and Data explorer are some default features that everyone would expect from a database client, and yes DB lens is packed with those features by default!

Its currenlty a beta version now and I would want to do more iterations based on what people want!

Hope you like it!

Looks very promising! New widgets looks awesome <3 Congrats on the launch folks!

> OSS is often built around the implied assumption that users are also developers.

I have used a ton of OSS projects across different projects, but haven't opened the source code of 99% of the projects that I used. but what it gives me (or anyone) is the liberty to look at the code at any time I want.

Another reason to choose OSS products is the OSS communities <3 , I have experienced resolving real issues over Discord/Slack way faster and more efficiently than the support workflow. once someone experiences the community, they will understand the need of giving back to the community and that keeps the community active!

Finally, In these days, I don't think there are any software *products* that are running without a piece of OSS code in it.

postgres + postgres_setup + farretDB = something like MongoDB ?

Could you add more details on "Why someone need to choose this over other DBs"from a product PoV or even the DX pov?

Can we expect IPO next year :p ?

Totally!

May be a random thought but I feel like social media is crowded and having multiple platform is going to kill the "SHARING" part and it has now become "what gets higher ranking" kind of a stuff.

Imagine if all social media posts were having RSS feeds and with one application we could all scroll through different feeds!