No, that started out as something of a happy accident, then I leaned into it for consistency. It's a feature that could be added, though it's not one I've ever actually used in other similar apps, so I haven't prioritised it.
No, that started out as something of a happy accident, then I leaned into it for consistency. It's a feature that could be added, though it's not one I've ever actually used in other similar apps, so I haven't prioritised it.
I've been using my Phosphor Notes project for about a month now as a replacement for Loqseq / Obsidian, and I've got to say, building something custom was the right call. This is working out really well. The long-form writing support is much better than what Logseq offers. github.com/adcaudill/ph...
Partial application screenshot showing a Valentine's Day banner over the daily note for Feb. 14th.
I have a bad habit of forgetting about holidays - so I took advantage of the fact that I'm building a PKM app to add a banner to daily journal notes for holidays. Simple & thoughtful touches like this can make software so much more useful.
For users of YAWAST / yawast-ng: The project has moved to a new location, and will have a major feature update next week, with plugins, new injection testing, automation & performance improvements, and more. It'll be the biggest release in years. github.com/adcaudill/ya...
For years I was tempted to draft an updated IRC specification that extended the protocol to better address features in Discord/Slack that are missing, and address the variety of privacy issues.
Suddenly I wish I had actually done it.
Rough morning for the GitHub folks. And everyone trying to work.
For those that enjoy my short stories, here's the latest: "Sweet Dreams" - an exploration of technology & human motivations, and the nature of escapism. adamcaudill.com/writing/2026...
Thanks! This is super helpful, and generally aligns with my prototype: 1) Electron/TypeScript (language that's easy for most), 2) Long form has a first class exp. (and is a major focus), 3) Docs are on the todo list, 4) I'll give thought to ref. management, great point, 5) atproto is a good idea.
Agreed! That was requirement #1 for this project: everything local, any sync is left to the user and their preference. It's all markdown files, so there are countless good sync options. With optional file encryption if added security is needed.
If you use a PKM tool (Logseq, Obsidian, etc), what do you like? What do you hate? What needs do you have that aren't being met? I'm working on a new PKM, and I want to make sure that I'm hitting the key points early in development.
Is it just me, or are GitHub Actions seriously lagging again? 20+ minutes before jobs are even being queued, and then a lag before starting.
Long term, I'm guessing the damage will largely be around products where users often need 10% of the functionality they are paying for - which is far from uncommon. These are the ones that are easily replaced, and have a decent chance of the numbers working out well into the future.
I must be listening to too many YouTube videos with narrators from the UK. I'm starting to think of "Z" as "zed" instead of "zee."
That brings back memories - I've always loved the flexibility of email, especially in automated processing, but it can be such a mess. And every component in the system opens the door to them being 'helpful' and trying to decode, leaving people like us to clean up the mess they leave.
Epstein used Gmail, and it does MIME encoding for HTML emails. This very much lines up with the encoding being broken as it's moved between systems. I've had to build software that unmangled messes like this, it's an annoyingly common problem.
I hope your right, though the ever expanding set of laws and regulations has made regulatory capture a very real thing. I was working on a small project that could be called social media if you squint the right way, and realised I'd need an entire compliance team, for an otherwise 1 person startup.
Hugs to those being impacted by Amazon's latest round of layoffs. A loss of a reported 16,000 jobs is painful, but especially so in this market. I wish all impacted the best of luck.
This isn't just about students cheating, the "AI detection" tools are so bad, that a lot of human writing gets flagged as AI, especially for people that are actually good at writing.
I've seen my writing ranked as 50%+ likely to be AI, when not a single word was from AI.
It's amusing(?) to see a popular account mine carefully articulated points I made on a topic, for pithy social media posts - unacknowledged, naturally. I guess I should just be happy that the points resonated.
Roughly 15 years ago, I ran a speed test with Speedtest[.]net, and it generated this image URL to share the result. Much to my amazement, the URL still works: www.speedtest.net/result/12119... That's honestly pretty impressive. And make me wonder how much storage are they wasting?
It's been a few years since I've done anything interesting with the Windows USB stack - my recollection is that it's fairly well contained, but descriptor handling was quite buggy. I was once working on a code exec as SYSTEM bug in the handling code, so not much would surprise me. It's complex code.
Hope you stay safe & stay warm. Doesn't sound like a great morning.
For me, looks like all emails from today have that banner (or at least those from 9AM and later), older emails don't. Something is very much broken on their filtering system.
I'm in the midst of drafting an essay with a working title of "Generative AI: Garbage In, Garbage Out" - so I think we're in agreement there.
Given that some engineers see it as a useful boost, Iโve suspected that thereโs another angle to this.
AI seems to produce better results when instructions are clear and the expectations are well defined - similar to managing a Jr. employee. Management experience may change results & perception.
That's honestly a pretty clever approach. Somewhat risky in terms of having wallets blocked once identified, but it's a clever work-around of the sanctions system, I've got to give them that much.
The worst part of writing in a dream: rushing to your computer at 6AM so that you don't forget that one great line, when you'd much rather still be sleeping.
I applaud your persistence. Listening to DJT talk gives me a headache after about 60 seconds; reading the transcripts later is generally bad enough as it is.
And reading the transcript of this one was certainly painful, in multiple ways.
I'm tempted to write an article on how the lessons learned from the WWII-era US Mark 14 torpedo (and the disastrous Mark 6 exploder) can be applied to security. I wonder if it would land with people, or be too niche and only appeal to those with an interest in both security and naval history.
For the last week I've been building out my own PKM app - I've long loved Logseq, but the sharp edges were getting to me, especially the fact that it doesn't work well for long-form writing. Building something that's meeting my needs from Logseq, iA Writer, &c. is working out so nicely.