Everybody knows you can get real tense and stop breathing when staring at a screen, so I thought a very low-friction simple reminder (a circle expanding and shrinking) would be useful. I couldn't find anything free, so I vibecoded this. I have familiarity with webdev and some other things but had never heard of Tauri or used Rust, but the LLMs recommended those over Electron to keep it lightweight/small.

There are some basic settings for color, opacity, minimum size, etc. You can replace the circle with a custom image. That's the most I could consider to do for now.

It's windows-only and FOSS on github.

Comments URL: https://news.ycombinator.com/item?id=46858930

Points: 1

# Comments: 0

You can only rank supporting arguments against other supporting arguments, opposing against opposing, etc, in a hope to neutralize confirmation bias for a given position. i.e., even if you agree with a perspective, you'd still have to decide what is the better argument for it.

I made this because I've spent too much time arguing with people on the internet, and sometimes you see the same tired arguments and rebuttals, and I just wished there was a place where you could point people so that they can walk through all the arguments and counterarguments themselves so it's not people just repeating themselves in circles.

I know it's a pretty common hobby horse for rationality & debate nerds; I've seen a lot of varieties of the same thing on the internet while seeing how else things were done. It started with the idea of argument mapping/trees and how different statements could connect to other statements, and perhaps there could be a massive web visual of how all statements interconnect...but it made me think of how people thought Obsidian's graph thing was cool, but ultimately pointless.

Anyways, I wanted to go the opposite direction; instead of tons of features relating to fallacies/rebuttals, etc, I wanted to make the objects as simple as possible, such that they were more easily digestible. And ultimately the form is pretty loose for how people construct their Arguments.

This is my first side project; I primarily work in film & entertainment, but minored in Math/CompSci and always wanted to build a website (what a dream, huh?). Just had a baby and not a lot of time, and only vanilla webDev experience (I STILL maintain my personal website with Dreamweaver, but am probably gonna revamp it now that I have more experience.) Over the course of the past year just learning the ins and outs of Vue, going thru a few iterations of frameworks, libraries, tweaking, DBs, migrations, local dev, etc.

Comparing it with all the AI side projects that are currently out there, it feels like a pretty humble CRUD site, but it feels nice to put something out there.

The styling obviously isn't anything to write home about, but I wanted to keep it minimalist and closer to a wiki aesthetic, but responsive. Accessibility probably leaves much to be desired, but that's why I ultimately leaned on headless and NuxtUI for interactive components.

At this point, though, the question of content/users remains. I tried seeding with an LLM, but did not really enjoy tuning the quality of content generated, the voice, the personas, etc. I'm now considering perhaps keyword scanning for debates on X/Twitter and converting those into content that links back. It feels a bit cringe going into fully automated reply bot territory for seeding/promoting it, but I'm not really sure what other avenues to pursue if it's just done.

Open to feedback, especially around UX A lot could probably be refined, but I'm sort of unsure how to make it easier for a new user to understand or to want to contribute. Higher-level feedback on the structure are also welcome; someone said to me that Statements and Arguments might still be too abstract for people and it should be one unified object, but I feel like I'd have to have more feedback to think about that.

Comments URL: https://news.ycombinator.com/item?id=46346678

Points: 2

# Comments: 0

I've got basic lazy loading implemented. Click expand on comment, it API calls for replies. It will show load more if there are more to load.

Contrast this with something like hackernews, which loads many layers at once. I can conceptualize a recursive way to retrieve the whole tree, but...

Supabase limits to 1000 rows returned; while I have not hit those limits yet, future proofing may be a good practice. Or simply limiting in general.

But limiting, paginating, and sorting all run into hurdles with a recursive call of arbitrary depth using one API call.

If the limit truncates one comment's replies, do I just need to have a column counting direct replies to compare to? Over fetching doesn't quite work here, does it?

Is it possible to sort within the recursive query such that if one of them still needs to load more, the order will be correct?

For ex, if my limit is 100 comments, there are interesting cases where it runs out breadth first or depth first.

I've been informed that I'm currently implementing something called adjacency list, but I'm not sure how I should implement eager loading of a few layers

Comments URL: https://news.ycombinator.com/item?id=44139993

Points: 1

# Comments: 1

Should people really understand every syntax there before learning simpler commands like printing, ifs, and loops? I think it would yes, be a nicer learning experience, but I'm not sure it's actually the best idea.

Good reminder to set usage caps with a deployment

And if I am to have a plan, why not just implement from the start?

Comments URL: https://news.ycombinator.com/item?id=43105042

Points: 11

# Comments: 9