@bulkhttpstatus · X

@noctris_io · X

@danielkleach · X

is a branded client portal for files, answers, sign-offs, and signatures. No more scattered email threads, docs in Google Drive, or confusion about who is waiting for whom. Business and client both see what is done and what is in progress on both sides, in

@theHumanFlag · X

Get alerts when a site is down.

@GrammarFixApp · X

Your site goes down for 10 minutes. You lose $500. You don't even know. Free tool that checks your site every 5 minutes and alerts you the second it dies. No signup. Paste your URL → instant results.

@richardnavanda · X

@SimpleWebAPIs · X

@sl1ma4 · X

@di_spivak · X

@sitedropper · X

- Local to live without the hassle

@Ex3NDR · X

Few days ago Happy had a birthday. Tried to refresh one of the most neglected part of it: our Happy Website: also i built a new harness called “rig”. i started to use at work recently instead of codex/claude code and i liked how it does work. i want to share this with everyone. it is a codex and cause code reimplemented using Pi, but keeping native prompts and expanded a little for uniformity (like added workflows to codex yay!). when something new released that is worthy of porting - i ask Sol to mim for prompts or read sources directly and i can have a feature within an hour. why this is needed? i was constantly blocked by the needing of integrating a lot of models together, which each has their own harness or many doesn’t have any, but i didn’t want to go too far from native and don’t like the idea of extensions - i want experience to be the same everywhere. i think configuration > extensions. more soon

@sykatt01 · X

Here it is: Definitely appreciating feedbacks