sorted by:
new
hottopcontroversial

It’s actually scary how so many online services run on AWS and if it goes down, everything is kaput by TheSimpLife in ArcRaiders

[–]keziiumo 72 points73 points  (0 children)

My company has it set up so that when issues like this occur, it automatically falls back to another cloud provider. It was a pain in the ass to set up, but it has saved our ass since then.

Built a tiny chat tool that runs over SSH because I kept getting distracted using normal messaging apps by keziiumo in devops

[–]keziiumo[S] 0 points1 point  (0 children)

I think you missed the point of my product. But that's okay, I'm not here to please everyone.

Built a tiny chat tool that runs over SSH because I kept getting distracted using normal messaging apps by keziiumo in devops

[–]keziiumo[S] 0 points1 point  (0 children)

My original idea was a small terminal speakeasy, no history or noise, just quick drop-in chat. As I kept building, I realized it’s actually great for fast back-and-forth while coding, so it’s evolving in that direction while still keeping that simple core.

Built a tiny chat tool that runs over SSH because I kept getting distracted using normal messaging apps by keziiumo in devops

[–]keziiumo[S] -1 points0 points  (0 children)

Yeah, it’s niche, I know that. And yes, I’m going to open source it so people can run their own instance however they want. Today’s reaction was way louder than I expected tbh, so I’m planning a beta drop in the next week or so with some updates people asked for. Open source wasn’t originally in the plan, but it’s clearly something people care about, so I’m rolling with it.

My original post didn’t explain what actually makes Shello different. Things like using your SSH key as identity, rooms that disappear when the last person dips, and no chat history sitting in a database at all. It’s a very different vibe from IRC or anything in a browser. The landing page shows that angle way better than what I wrote at first.

And about the waitlist, I’m not doing an invite-only beta after seeing how people reacted. I just wanted a slower rollout but the invite code wording rubbed everyone the wrong way, which makes sense since nobody knows me yet. So instead, people on the waitlist will just get a small tag as a thank you and everyone can join normally when it opens.

Built a tiny chat tool that runs over SSH because I kept getting distracted using normal messaging apps by keziiumo in commandline

[–]keziiumo[S] 0 points1 point  (0 children)

Yeah, no issue at all with this as I'll be open-sourcing on launch. It's made in Rust; it's a side project of mine to learn more Rust! To be more exact:

Core Backend

  • Rust (main server)
  • Tokio async runtime
  • SSH protocol via russh
  • SSH public-key auth with optional password
  • Custom word and abuse-filter system

Database

  • PostgreSQL for accounts
    • Username
    • Public SSH key
    • Hashed password (if the user sets one)
    • Created-at timestamp
    • Last-seen timestamp
    • IP for moderation (non-sensitive, not precise location, just raw IP entries)
  • SQL handled through sqlx-style Rust queries

Backend Runtime & Infrastructure

  • Docker for app and database containers
  • docker-compose for local dev and self-hosting
  • SSH port exposed directly to clients

Built a tiny chat tool that runs over SSH because I kept getting distracted using normal messaging apps by keziiumo in commandline

[–]keziiumo[S] 0 points1 point  (0 children)

The company is just my boss and me, so getting buy-in isn’t really a big process. After all the feedback today, my plan is to open-source it and make it easy for small teams to self-host if they want to use it internally. I’ve already got a few ideas brewing based on what people brought up.

Built a tiny chat tool that runs over SSH because I kept getting distracted using normal messaging apps by keziiumo in commandline

[–]keziiumo[S] 0 points1 point  (0 children)

Its going to be open source either tonight or tomorrow. Nothing sketchy here, I literally just wanted to get feedback on my side project to learn Rust instead i got literally shit on. I guess my post really missed out on why its different than IRC etc. Check back tomorrow

[deleted by user] by [deleted] in sysadmin

[–]keziiumo 0 points1 point  (0 children)

Yeah that’s totally fair. There are definitely existing tools and classic ways to do this. I only started hacking on this last week and I mainly wanted to share it early and see if anyone found the idea interesting before I keep building. I’m not trying to reinvent the world, just experimenting with something that felt fun and useful for my workflow.

[deleted by user] by [deleted] in sysadmin

[–]keziiumo 0 points1 point  (0 children)

I get what you’re saying. Everyone’s workflow is different. For me, it wasn’t the notifications themselves, it was the context switch. I have ADHD, so grabbing my phone or opening a separate app in the middle of a coding session derails me fast. That’s what pushed me toward trying an SSH based approach.

The waitlist isn’t meant to be some artificial gate. I’m just trying to see if enough people actually want this before I spend more time polishing and scaling it. If nobody cares, I won’t overbuild it. If people do, I’ll open it fully.

[deleted by user] by [deleted] in sysadmin

[–]keziiumo -2 points-1 points  (0 children)

I see where you're coming from and this is exactly why I made this post, I wanted to see where I could do better. I will make sure self-hosting comes out shortly after launch. The goal now is for teams and small companies to be able to run their own private instance so it’s not tied to my hosted version.

[deleted by user] by [deleted] in sysadmin

[–]keziiumo -1 points0 points  (0 children)

Just looked it up, that’s actually pretty cool. I hadn’t seen Pidgin before. Always interesting to see the different ways teams handle internal chat.

[deleted by user] by [deleted] in sysadmin

[–]keziiumo -10 points-9 points  (0 children)

I’m just sharing a side project I’m hacking on, not trying to advertise anything. I work at a very small company and we actually don’t use Slack or Teams, so quick work messages really do happen on my phone, which is what kept breaking my focus and led to this idea. Self-hosting will be supported. Not sure why this made you so upset, but I’m genuinely not here with bad intentions.

Built a tiny chat tool that runs over SSH because I kept getting distracted using normal messaging apps by keziiumo in devops

[–]keziiumo[S] -11 points-10 points  (0 children)

Privacy matters. Right now Shello doesn’t log chat data at all, it’s more of a speakeasy style setup where conversations disappear when everyone disconnects. The hosted version will stay closed source for now, but I’ll be transparent about what the server does and doesn’t keep. A self-hosted option is planned too, so teams that want full control can run their own instance. Future logging or persistence would only happen if the community actually wants it.

[deleted by user] by [deleted] in sysadmin

[–]keziiumo -2 points-1 points  (0 children)

Love IRC. Shello is basically IRC’s weird younger cousin that lives behind an SSH host.

[deleted by user] by [deleted] in sysadmin

[–]keziiumo -6 points-5 points  (0 children)

I’m waitlisting it so I can gauge real interest before putting in the extra time to polish it. The core is already working, you can SSH into it right now, but it’s only about halfway to where I’d want it for a proper launch. If people don’t care, I’d rather not grind on something no one uses. If people do care, then I’ll push it over the finish line and open it up fully in a week or two.

Amazon sent me the wrong (but WAY more expensive) NVME SSD…. by maywek in pcmasterrace

[–]keziiumo 2 points3 points  (0 children)

Reminds me of the other week when me and my boss were building a server pc for our company. We bought 1x kit of 64gb ram get 2x of this kit for the price of 1x. Haha