tobypadilla
Joined 17 years ago
Karma
146
Submissions
17
Member since
Nov 13
Recent submissions
Comment · 4 years ago
Thank you so much!
Comment · 4 years ago
Hi, Toby from Charm here. With Soft Serve the account system isn’t tied to the machine. You can configure access by cloning the config repo, then editing a yaml. This makes it easy to add collaborators vs adding user accounts to the underlying server. It also allows for anonymous access. You can test our server:
ssh git.charm.sh
We also made it so it creates repos on first push. The navigation TUI is served directly over SSH.
Comment · 6 years ago
That's correct! In fact when we announced this we mentioned that the BBS technique was what inspired this PR:
https://twitter.com/charmcli/status/1320184218794795010
It's interesting to see forgotten lore or techniques reemerge. We (Charm) have just published a TUI framework called Bubble Tea and imgcat was one of the first tools that implemented it, so we were excited to see the progress and help with rendering.
Comment · 6 years ago
Yep! This is actually where muesli got the idea from:
Comment · 6 years ago
Thank you and sanbor for the detailed reply. I think it's really interesting. We can't promise anything now but it's definitely something we can look into. I self-host Sourcegraph and Gitea and enjoy the freedom (and can also see why someone would pay to not self-host).
Comment · 6 years ago
For what it's worth, you don't need to use the Charm Cloud features. If you run `glow` in a directory, it will recursively search subdirectories for markdown files and display them for viewing in the TUI. Stashing will encrypt them then push them to the Charm Cloud though.
Comment · 6 years ago
As one of the Charm co-founders, I think that's fair! That being said, others have asked us about this recently as well. I'll paste a reply I made the other day on Reddit:
Your concerns are well founded! I've certainly been burned by services disappearing...
It's a compromise to have a business model that allows us to develop Charm full-time vs. being completely open source. Our plan is to have a business model similar to GitHub: free and low cost services for individuals with enterprise hosting options (colo or hosted by us).
One thing that I think we should do is allow for a very easy export of all of your data. We can build that into glow and charm (vs. having to email us and ask for it or some other draconian option).
This is very much a 1.0 release of the Charm Cloud and one of the reasons we wanted to ship it early was to get feedback from the community and build out the features our users want. Your point is a great one that we should solve for ASAP. A glow export feature that spits out a .tar.gz of all your stashed markdowns seems like a great idea.
We're also open sourcing the libraries we use to build glow and charm, most of which don't require the Charm Cloud. We just made our TUI framework Bubble Tea open source for instance:
https://github.com/charmbracelet/bubbletea
We also have a library for applying JSON stylesheets to Markdown called Glamour that is independent of the Charm Cloud (and currently in use in GitHub's cli):
https://github.com/charmbracelet/glamour
Thanks for your question, it's a problem worth addressing.
Comment · 6 years ago
We actually ended up making our own encryption library that's based on age, it's called sasquatch (built by our team member muesli):
Past: Charm founder, TweetDeck, Last.fm, Musicmobs, Apple