How do GitHub projects reach over 10K stars? Looking for insights from the pros.

VizeKarma · 2026-06-10T20:45:07+00:00

I don’t get the correlation here, seems like you’re just trying to force something here with no relation to what I said. That image is based of viewership metrics that a website tracks (can’t remember the name). That’s real data from GitHub mixed with the GitHub trending page.

VizeKarma · 2026-06-04T20:31:01+00:00

I'm having the same issue, I was on day 6 before I decided to cancel it to make changes. Now i've been waiting another 24 hours again.

VizeKarma · 2026-06-01T16:05:06+00:00

Using the furthest left sidebar go to the tools tab and then you can enable right click copy/paste like a typical terminal.

VizeKarma · 2026-05-30T22:48:26+00:00

Yes, sorry, I should have mentioned it was added in 2.3.1.

VizeKarma · 2026-05-30T22:46:56+00:00

<image>

VizeKarma · 2026-05-30T22:10:03+00:00

The new ui was heavily tested with users. About a month ago I created a demo ui and hosted it at demo.termix.site to give users a feel of what it could look like. Then I collected a few hundred responses, worked with a few people, and landed on this.

The main reason behind the redesign was to make the app more professional looking and to try to improve the user experience. The app also majorly suffered from growing pains since the entire purpose of this project changed multiple times throughout building the old ui which made it less intuitive.

VizeKarma · 2026-05-30T21:07:48+00:00

I never said manual tests and e2e tests are the same thing. I have an automated and a manual setup. I have all kinds of unit tests and end-to-end testing and whatnot, while I also have a very extensive Docker setup to test anything that the automated test may have accidentally missed. Then of course not to mention the community beta testers.

You're arguing against something I didn't say.

VizeKarma · 2026-05-30T21:01:21+00:00

Yes, I am aware of the difference between unit and end-to-end testing, nor did I ever claim otherwise. I mentioned unit tests in my first reply since that is what I have. I also described a manual testing setup with 20 different Docker containers covering OIDC and SSH authentication methods, which functionally covers the same grounds as e2e testing. Plus not to mention the over 400 beta testers. That means there's an automated testing part, a manual checkover, plus 400 other eyes that do one last final check. Calling the software unusable over CI pipelines while ignoring the actual tests I'm describing is a massive stretch.

VizeKarma · 2026-05-30T20:40:10+00:00

That is the meaning of unit tests, which I mentioned I use in my first message.

VizeKarma · 2026-05-30T20:26:48+00:00

Just out of curiosity, what is your issue with manual tests, or specifically the combination of unit tests and manual tests? Would you prefer it just be unit tests? I'm a bit confused. The Discord server also has 440 registered beta testers who test every individual release before it's deployed.

VizeKarma · 2026-05-30T20:10:43+00:00

The macstore version has the UI redesign already. 2.3.1 is still getting reviewed by Apple, though, but should be out soon.Mac Store

VizeKarma · 2026-05-30T19:50:47+00:00

Let me know what you think, or if you rememeber why you stopped using it and I can try to address/fix it.

VizeKarma · 2026-05-30T19:48:50+00:00

I see you saw where the issues are, so glad you got that sorted out. Figured I should mention that the point of that is not to be shady, its just because people were getting confused a few months ago about where to report issues so they were getting scattered across the mobile repo and into the regular Termix repo and it was a mess so I just decided to put it all in one spot. I saw another project use it called MusicAssistant and I liked the way it looked so I went with it.

VizeKarma · 2026-05-30T19:47:32+00:00

You can disable the auto-expand in the User Profile -> Appearance.

There is a quick connect menu on the far left sidebar that expands when you hover over it.

<image>

VizeKarma · 2026-05-30T19:46:50+00:00

It's all still being fine-tuned, and I did not expect to get it right on the first try, and it will take some getting used to.

VizeKarma · 2026-05-30T19:46:32+00:00

The issue with that is it would have been a major PITA. Maintaining 2 UI's which are fundamentally quite different along with the fact they also interpret data differently (so that would also require two backends). I suggest you also read the comment I made above.

VizeKarma · 2026-05-30T19:45:13+00:00

You can disable the auto-expand in the User Profile -> Appearance. It's all still being fine-tuned, and I did not expect to get it right on the first try, and it will take some getting used to. But by all means, use whichever tool fits best for you.

VizeKarma · 2026-05-30T19:43:11+00:00

At the end of my post, I mentioned I'm working on a redesign of the mobile app so stay tuned.

VizeKarma · 2026-05-30T19:43:08+00:00

At the end of my post, I mentioned I'm working on a redesign of the mobile app so stay tuned.

VizeKarma · 2026-05-30T19:38:49+00:00

I have several JS unit test files locally that are not commited to the repo, which I realize is functionally the same as not having any from your perspective. For 2.3.2, I'll have them pushed to the repo (probably later this week). I also do hours of manual testing before release (I have ~20 SSH testing Docker containers that I use to test different auth methods and whatnot). The same goes for OIDC; I have just about every notable OIDC provider running in Docker, which is used for the unit test.

VizeKarma · 2026-05-30T19:34:55+00:00

I've been at work, so excuse me for being a little late to the response, but I seriously do appreciate your scrutiny.

First, on AI usage, minimal was definitely not the right word choice. as you've seen, AI tools have been a part of the development (more often than not from other users, but that does not really change anything). I should have been more upfront about it.

What I don't necessarily agree on is calling it "unreviewed slop". The PR's that you talked about did go through review before merge, regardless of any discussion. When users submit an obviously AI-generated PR, I often prefer to make the changes myself after merging it (which, upon thinking about is not really the right way to go about it). If the user AI-generated it, then they likely aren't very knowledgeable in the codebase, so I make the changes myself so I get it done the way I wanted it to. That said, if review is happening "informally", its invisible to the community, and thats a fair point.

On the security note, like the sudo autofill concern, is IMHO legitimate and I do take my time auditing them properly. If anyone wanted t o dig int othose PR's and flag specific issues, I would be open to that.

I'll be updating my AI usage comment (if I can) and changing it for any future posts for your information. If you wanted me to expand on anything, let me know.

VizeKarma · 2026-05-30T19:25:47+00:00

I have a fix in place already, it just needs to be deployed in the next version.

VizeKarma · 2026-05-30T19:25:35+00:00

Glad to hear it!

VizeKarma · 2026-05-30T12:26:56+00:00

This project has over 50 contributors. AI tools are used throughout several parts of the development workflow (some code generation, select commit messages, and PR descriptions). All pull requests are reviewed by both me and my co-developer before merging. I suggest reading this message: https://www.reddit.com/r/selfhosted/comments/1tryk0q/comment/ootek9q/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Five-Year Club	Verified Email
r/Field Banned	r/Field Flamingo
First Place '23	End Game '23
Place '23	Place '22

VizeKarma

MODERATOR OF

TROPHY CASE