I started reading this and was immediately charmed! I think this might finally be the time I learn a lisp language 👀
I’m going to be helping plan a potentially big rearchitecture at work! excited for the possibilities but slightly nervous as I haven’t undertaken something like this before. On that note, if anyone’s ever migrated from firebase to a more conventional system architecture/backend, would love to chat about how it went and any pitfalls to look out for!
Working on my talk I’m giving at the local Go meetup on Tuesday, and also on my silverbullet plug for posting to micro.blog!
Setting up silverbullet, then trying to decide on which laptop I should get next for a Linux hacking machine.
I’d forgotten about them! Look pretty dope, but out of my price range sadly :’( thinking of picking up a dell latitude 7280 and loading some Linux flavor onto it.
Oh man, this is so cool! I love the approach of providing students with all the tools needed to use the system included, allows for a complete understanding of the system and lends itself to being easy to hack on. Great stuff!
That’s the kind of cool things that this entire-stack-in-one-file approach enables:
I got this set up on fly.io yesterday and am loving it so far! It was relatively painless to set up, and now I have notes that sync across my work machine, phone, and iPad. The core functionality is similar enough to Obsidian that I feel comfortable moving to silverbullet full time. There’s also plenty of space to develop my own plugs, something I’ll be looking into over the next few weeks.
Now I’m considering that maybe buying an intel NUC for a closet server wasn’t such a good deal. It occurred to me as I was selling my five-year-old android phone on Craigslist for $40 what an incredible piece of technology it is that is now adjacent to junk. Multiple photo/video cameras, microphone, battery (built-in UPS!), screen with touch input, GPS, GPU, decent CPU, Wi-fi, 4G antenna (stay online even if your apartment loses power). Getting a rpi-like board with these capabilities would set you back a pretty penny. Anybody else have experience using these as mini servers?
This is a great point. I have several old Android phones kicking around that I’ve wanted to start to hack on. My first idea was to try and build a cyberdeck with my old Pixel 4a, but I bet they could be used for mini server applications! Do you know of a way to easily get some Linux running on them by chance? seems like that’d be the first step
Reminded me of encore.dev, which has a feature called Flow that shows an architecture diagram that’s always up to date.
Great stuff! This has strong micro.blog energy. If I hadn’t invested time into my micro.blog and my mastodon profile, I’d probably try to get this up and running. Keep it up!
I wonder how hard it would be to add Obsidian compatibility (same method of link resolving, block IDs, callout blocks) 🤔 It seems that it’s quite modular with its plugin system.
If I could immediately import my obsidian notes that’d be amazing! Might start working on a plugin… Seems to cover most of the use cases I have for obsidian but is open source which is a big win for me.
Logseq has different file structure, IIRC you can separate directories with dots in wiki links. I prefer Obsidian’s approach, where you specify a path relative to the root of your vault. It uses shortened version if note name is unique.
still trying to find a notetaking app that ticks all my boxes:
Logseq is a frontrunner, but is sadly lacking in handwriting support. This makes me think that I might just abandon handwriting notes on my iPad, but that also makes me feel weird because I bought it mainly for handwriting. Would love any suggestions from the lobsters community on notetaking apps!
Obsidian with some handwriting plugin and you’ll be good to go. Really the best out there right now as Logseq is in very early stages and it’s slow. I use syncthing to sync between all devices.
P.S. Logseq probably also has such a plugin.
Lately two things:
TIL/today I did posts are one of the main things that I post on my blog. I’d highly recommend https://micro.blog to anyone trying to blog more often. There’s a great community there, plus everything can be hosted on your own infrastructure and integrate with Mastodon, indie web, etc. Something that lowered the barrier for me to write small blog posts about whatever I’m currently working on was to write a shell script that makes it as easy as
mb to write a new post!
I’d heard about Dark a long time ago, this post brought it back to my attention! Gave it a try, very impressed at the speed with which changes are made live.
Thanks! This is one reason I feel confident about the vision for Darklang, even despite the challenges. I think there really isn’t anything like it anywhere else!
I wonder if they’ll be using Oxide machines… sounds like they’re looking for what Oxide is selling
There’s a physical rack that visitors have taken photos of! This means they’re very close to the end of verification testing and moving into the Pilot stage
I’m less interested in immediate feedback to the query I’m writing. I’d rather have a tool that helps me write the cryptic dsl, like a symantic editor or something with suggestions. Maybe like those regex editors online
I get that. For me, it’s all about visualising the input data and what’s produced with what I express in the
jq filter. The shape of the data and how it morphs is a key part of my understanding of
jq and the data itself.
This is one of the first things I fix on a new machine – just did it a couple days ago! It makes sense that this would be a struggle for others as well but I’m not sure why I thought it was just a me thing :)
This looks like a great overview! I might start going through these papers myself. I often fear that as our computing abstractions get more and more powerful, many engineers will forget/be unaware of the turtles down at the very bottom.
Started trying to use this at $DAYJOB today, and it like it! One downside I’ve seen after using it for a few hours is that it’s a bit clunky to use for more ad-hoc testing because you can’t (afaict) hit a specific endpoint you’ve defined within your hurl file. I wound up falling back on my usual combo of Postman/IntelliJ HTTP client for that part of my workflow. It does seem like it’s still useful for more structured testing though!
This is probably quite a useful write-up for anyone looking to improve the Gemini spec.
There are a few criticisms however that I don’t think are valid given the goals of the project:
Precisely! I think the criticisms in the article are valid… If your goal is to have a Web replacement! Gemini’s trying to be a document only platform, not an OS/application platform. Not saying that the Web’s evolution into an OS/application platform is bad, but Gemini is actively trying to avoid that route.
I don’t see how things like “have more precise descriptions”, “be more efficient” and “fix your security” are about being a web replacement. I read this criticism more as coming from an expert on protocols and their client-side implementations.
I find it especially ironic that Gemini enforces using TLS, but then has such weak security guidelines as to make it essentially useless. That’s like all those folks running websites with self-signed TLS certs. The only advantage that gives you over an unsecured connection is when you have a passive attacker who can only eavesdrop but not actively put stuff on the wire. This article goes into detail as to why, with solid reasoning. But this kind of stuff is like arguing against a brick wall.
Note that even his gripe about not being able to share multiple resources over one connection isn’t web-specific: a Gemini crawler or archiver would also massively benefit from doing this.
A significant bunch of Gemini fans are perfectly fine with gemspace being harder to crawl and archive.
Anyway, Daniel’s critiques are on point, but it won’t sway most of the community. The shortcomings of the spec have been endlessly hashed out. The people losing out are the ones who would prefer Gemini to become a bit more mainstream, with support in curl and other tools (like Lynx). The solution, of course, is to code your own tool, which is what Gemini is explicitly designed to be easy to do.
Seems like an unambiguous protocol specification would be a critically important part of making it easy to code your own tools, assuming you want them to talk to other peoples’ tools.
There were plans for that, according to the FAQ (section 1.5):
However, the main driver behind the protocol work (solderpunk) seems to have stepped back, and the mailing list used for discussions has been defunct for more than a year IIRC.
That’s how I see Gemini too. The original post that inspired it all was titled “Pondering what’s inbetween gopher and the web.” It was a Gopher post to a community of Gopher users.
So I think of Gemini as Gopher-plus rather than a Web-minus. If the intent was to be anything more than Gopher-plus, the spec would be open.