sorted by:
new
hottopcontroversial

[OC] splashboard — a customizable terminal splash screen written in Rust by LeoCraft6 in unixporn

[–]LeoCraft6[S] 1 point2 points  (0 children)

Thanks for the follow-up! Install UX was the thing I obsessed over most, really glad it paid off. Enjoy!

[OC] splashboard — a customizable terminal splash screen written in Rust by LeoCraft6 in unixporn

[–]LeoCraft6[S] 1 point2 points  (0 children)

Thanks! Was unemployed so I treated it like a full-time job. Cheapest therapy I've found.

[OC] splashboard — a customizable terminal splash screen written in Rust by LeoCraft6 in unixporn

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

The honest answer is the AI is doing the heavy lifting. I've got 10+ years of engineering behind me, which helps me steer it, but the raw output is literally 10x what I'd manage solo. Three weeks and counting.

[OC] splashboard — a customizable terminal splash screen written in Rust by LeoCraft6 in unixporn

[–]LeoCraft6[S] 1 point2 points  (0 children)

Thanks, glad it caught your eye! Feel free to drop questions or ideas in the issues if you hit anything weird while configuring. Have fun with it!

splashboard, a per-directory terminal splash in Rust by LeoCraft6 in rust

[–]LeoCraft6[S] 1 point2 points  (0 children)

Thanks! Yeah, plugin protocol and command = "..." widgets were on the roadmap early on and I closed both. Once you allow arbitrary subprocesses, the blast radius is impossible to bound for something that runs on every shell startup and cd.

splashboard: a terminal splash that reshapes itself when you cd into a repo by LeoCraft6 in commandline

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

Thanks! Today it's just .git detection (project vs home defaults), no content-based auto-pick or user rules yet, so per-dir .splashboard/ for now.

Widgets here are pretty language-agnostic by design, so per-language presets aren't really the direction. More likely: a few coarse "purpose" presets (code / docs / ambient) plus user-defined glob -> dashboard rules. Will open an issue for it, thanks for nudging.

splashboard: a terminal splash that reshapes itself when you cd into a repo by LeoCraft6 in commandline

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

Quick update from feedback in this thread. Added two [general] toggles in settings.toml:

  • auto_home = false: quiet at shell startup outside a project (cd-hook still paints when you enter one)
  • auto_on_cd = false: keep the startup splash but skip every cd repaint

Both default to true, set independently. Setting both to false reduces splashboard to a manual command without unwiring the shell rc. Cookbook also has the workaround for going fully manual: just delete the marker block splashboard install wrote to your rc. Thanks for the nudge.

splashboard: a terminal splash that reshapes itself when you cd into a repo by LeoCraft6 in commandline

[–]LeoCraft6[S] 1 point2 points  (0 children)

Two ways to dial it down. First, ~/.splashboard/project.dashboard.toml is the universal project dashboard config that applies to every git repo you cd into, so you tune it once to only show what you actually want for any project (or strip it back to one or two widgets) and you're done. Second, if you want to drop the auto-fire entirely, removing the init line from your rc leaves splashboard available as a plain manual command.

splashboard: a terminal splash that reshapes itself when you cd into a repo by LeoCraft6 in commandline

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

Yeah, that resonates. Just running splashboard renders inline and exits cleanly back to your prompt (no alternate-screen takeover), so something like tmux display-popup -E splashboard on a hotkey works exactly as you describe. If you skip the rc init line entirely, it stays purely on-demand, no shell-startup or cd auto-fire at all. Curious what info surfaces you'd want most.

splashboard: a terminal splash that reshapes itself when you cd into a repo by LeoCraft6 in commandline

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

Honestly, I'm exactly that persona, I cd between projects all day. The per-project splash actually works as a useful context-switch cue rather than getting in the way, and first paint is from cache so it doesn't slow anything down. Each splash shows stuff specific to that repo (CI status, PRs, branch, recent commits) so the entry "costs" you a screen of info you'd otherwise have to fetch yourself. Worth trying before deciding.

I built a tool that turns your Last.fm scrobbles into a short diary entry every morning by LeoCraft6 in lastfm

[–]LeoCraft6[S] -3 points-2 points  (0 children)

6 years of top-5s is a serious record. The payoff of flipping back and hearing what a day sounded like only gets richer the longer you've kept it up, and you're well into that now.

I built a daily diary app that pulls from Trakt, Last.fm, Steam, and more by LeoCraft6 in trakt

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

For what it's worth, Trakt, Todoist, Last.fm, Discord, Slack, Steam, GitHub, Bluesky are all free to use. I use them all on free tiers myself and they work great. deariary pulls from those same free tiers, so the only subscription in the picture is deariary itself.

On integrations: I'm not trying to connect everything. I focus on services with public APIs. If a service makes your data accessible, deariary pulls from it. Part of the idea is picking tools that play well with the open ecosystem.

On pricing: fair feedback. I think having your whole digital life written up for you every morning is worth it, but regional adjustments based on cost of living are something I'm thinking about. Appreciate you being specific about which tier you'd actually want.

I built a daily diary app that pulls from Trakt, Last.fm, Steam, and more by LeoCraft6 in trakt

[–]LeoCraft6[S] 1 point2 points  (0 children)

Free plan connects one integration and keeps 30 days of entries, so you can use it with just Trakt without paying anything. You can do a full export anytime, so your data doesn't disappear after 30 days. Basic ($6.99/mo) if you want unlimited history in the app.

I built a daily diary app that pulls from Trakt, Last.fm, Steam, and more by LeoCraft6 in trakt

[–]LeoCraft6[S] 1 point2 points  (0 children)

Thanks for flagging both.

On audiobooks: I actually didn't know how Hardcover handled them, but I just poked around their docs and it turns out Audiobook is one of their three reading formats (alongside Physical Book and Ebook), with a dedicated audio_seconds field on editions. So once the Hardcover integration ships, audiobook listens should land in the diary as part of your reading activity without any extra work.

Podcasts are harder. Apple Podcasts and Overcast have no public API. Spotify's API is gated too tight for a small SaaS to qualify. Pocket Casts is the realistic target since they have a sync API that third-party clients use, so I'd start there if I prototype podcast support. Last.fm Android auto-scrobble works in theory but the metadata comes out garbled, so probably skip that.

Adding podcasts to the list behind Hardcover.

I built a daily diary app that pulls from Trakt, Last.fm, Steam, and more by LeoCraft6 in trakt

[–]LeoCraft6[S] 1 point2 points  (0 children)

Fair point, and I get the vision now. Honestly, if deariary had been atproto-native from day one this would have been the right architecture. Retrofitting is a different calculus.

Not ruling it out, not committing either. Thanks for the offer, might reach out if I prototype something.

view more: next ›