niels

🎨 Introducing advanced form customization:

- Custom form layout
- Full control over input styling
- Button design options (size, colors, alignment)

Design every detail without touching code! 😊 Available on Tally Pro — simply click the Customize button in your form builder.

An update on one of our most requested features: Tally’s public API!

Our private beta is now live, and you can request access here: http://apply.tally.so/api

Convo - The cleanest bring your own key AI chatbot Single converation focused AI chatbot. No clutter, no distractions, your API key. Just you and the bot.

Introducing Convo, the cleanest looking AI chat app you will ever use. Bring your own API key and start prompting right away. No clutter and feature bloat, just simple conversations.

convo.ist

If people want to contribute or request features I might just open source it. It would allow people to self host and switch out the KV store and encryption logic to w/e they see fit.

In the end this is just a simple Next.js app that uses @vercel.com's AI SDK with some magic sprinkled on top to make it look good and feel fast.

Under the hood there's a KV store to keep track of conversations. So if you use it on other devices you can continue your conversation there.

After seeing @t3.gg's new t3.chat I noticed one thing that all these chat apps have in common. They may differ in speed and functionality but near all of them share the same bland robotic look.

They also target a very specific audience that doesn't want to think about their own API keys.

Convo - The cleanest bring your own key AI chatbot Single converation focused AI chatbot. No clutter, no distractions, your API key. Just you and the bot.

Introducing Convo, the cleanest looking AI chat app you will ever use. Bring your own API key and start prompting right away. No clutter and feature bloat, just simple conversations.

convo.ist

Obviously being a reasoning model helps here. And being cheaper is also a nice plus!

GitHub - segersniels/propr: Generate GitHub PR descriptions from the command line with the help of AI. It aims to populate a basic PR description right from your terminal so you can focus on more impo... Generate GitHub PR descriptions from the command line with the help of AI. It aims to populate a basic PR description right from your terminal so you can focus on more important things. - segersnie...

Think I finally found a use case where I feel R1 outshines Sonnet! Generating PR descriptions.

github.com/segersniels/...

R1 gives way more human readable summaries. Where regular LLMs like Sonnet and 4o do a decent job, a lot of it is still very robotic and often requires editing.

Old Windows 95 desktop, absolutely no clue which one.
M3 MacBook Air
Probably my M1 Mac Mini back when it first released
M4 Ultra Mac Studio or w/e silicon will be in the new ones

I did enjoy 16, breath of fresh air compared to the usual gameplay

Only time I really had issues was when the first Next.js 15 RC codemod released to change the async requests API. It changed a bunch of stuff that didn't need to be changed and took me a while to fix everything that broke.

Overall love codemods. Tons of edge cases probably make them hard to write.

Keep in mind that if you start using Inskribe that this is very much in early development and breaking changes might happen every now and then as I try to clean things up and optimize. However since it's mostly locally persisted, simply clearing your browser's application data should get you sorted.

Not having a database to manage files really complicates things as everything needs to be persisted locally before it can be committed to GitHub. Definitely not my cleanest work, but just glad it's starting to come together 🙏 Will improve over time.

Inskribe Documentation made effortless. Inskribe is your streamlined Markdown editor that lets you focus on writing, not wrestling with tools. No complex setup, no configuration headaches — just log in and sta...

Took a bit longer than expected but I finally got around to add basic file management to inskri.be. Not saying it's all perfect (spoiler: there will definitely be bugs and weird UX flows), but this marks the day that Inskribe becomes somewhat usable to manage documentation 🎉

Used Spotify for years. Made the switch a couple of months ago and haven’t looked back. I mainly favourite artists and listen to their stations which seem to give a lot more variety in music than the “for you” mixes or artist radios of Spotify. Lossless quality is a nice plus 🙏

Inskribe Documentation made effortless. Inskribe is your streamlined Markdown editor that lets you focus on writing, not wrestling with tools. No complex setup, no configuration headaches — just log in and sta...

Absolute love that I discovered @tiptap.dev to improve inskri.be. Simplified the backbone of the app so I can focus on the app itself. Typical case of - why reinvent the wheel if others have done all the work for you. Better table support and file management coming soon-ish.

Finally gotten around to set up a UMR-I for LTE failover in my network. Pleasantly surprised that restoring a UDM backup onto a UDM Pro was so smooth. Was expecting an evening of manually restoring everything but no -- great user experience @ubiquiti.bsky.social 🙏

Inskribe Documentation, but simple.

Finally gotten around to implement the ability to insert images on inskri.be. Took me a while to figure out a clever solution to achieve what I wanted. You can read how I solved it here: niels.foo/post/smart-i....

New files and directories when? Still figuring out a proper solution but -- soon 👋

Initial version of inserting and editing tables is also supported now. Next up images.

Haven’t used it yet, no. But will remember to try it out, thanks!

Inskribe Documentation, but simple.

Worked on some necessary improvements for inskri.be by persisting file changes and restoring them when opening up a file again. Allowing you to switch files and not lose progress. This will eventually pave the way to support creation of file and directory 🙏 If only I had more free time.

GitHub - segersniels/smooth.nvim Contribute to segersniels/smooth.nvim development by creating an account on GitHub.

Might as well share my Smooth theme that I ported over to Neovim for whoever wants to use it: github.com/segersniels/...

Also, not hating on Supermaven or Avante. Both are amazing projects that everyone should support. It's not because it didn't check all my boxes that it doesn't check yours.

Also super excited about the fact that Cursor bought Supermaven -- to see what crazy shit they will come up with.

Today I made the switch back to Cursor. And holy shit... Cursor Tab single handedly speeding up my entire flow so much that it's actually disgusting how good it is. So for now I'm staying with Cursor -- without needing to fiddle with a bunch of plugins to get something remotely similar 🙏

As for Neovim itself. I enjoyed it, but started noticing weird quirks that bothered me like plugins interfering with each other and struggling to get them to work nicely together. File & directory management (think nested directory management) being a hassle compared to a regular editor.

While great, Supermaven often times hallucinated gibberish and just plain wrong code which reminded me of the first few months of copilot back when it first released to the public (before gpt-4). Avante, while also great, lacked a bunch of stuff I regularly used from Cursor.

For the last month I've been trying to move away from Cursor to Neovim as an experiment to see if it could speed up my workflow. I had a bunch of fun setting everything up and experimenting getting the flow just right. Avante and Supermaven eased the transition from Cursor a lot.

Made a rough base for what my idea of a simple markdown editor without additional tooling should be like. Just Markdown and Github, nothing more.

Still need to do a lot of stuff before it becomes useful:
- New files and directories
- Ease of use stuff like tables
- Branch selection

inskri.be

At that high of a frequency it probably makes sense to explore something else rather than polling an endpoint. But for now I wanted to look at how best to optimise the current state.