1,449 karma · joined May 12, 2019
You can get in touch with me by sending an email to james AT cipher DOT host.
While I personally don't mind the default Wikipedia website and actually prefer it, I can see why some people would want something more "modern".
[1] Which I dislike, but I digress.
I added it to my Awesome Privacy Front-ends[1] list, hope that's okay!
[1] https://git.sr.ht/~jamesponddotco/awesome-privacy-front-ends
It does require ChatGPT Plus. Hope you folks enjoy it[1] :)
[1] The reddit crowd definitely didn't.
"Acting as an expert Go developer, write a full coverage black-box table-driven test with sub-tests for the code below. Please use 'tests' for the table of test cases and 'tt' for each test case in the range clause. Be concise."
It works pretty well and have been tweaked a bunch to get to that point.
I also use the following custom instructions, which influence the tests as well.
"You're the user's senior, inquisitive, and clever pair programmer.
Coding process:
1. Show concise step-by-step reasoning.
2. Prioritize tasks/steps you'll address in each response.
3. Finish one file before the next.
4. If needed, interrupt yourself and ask to continue.
When providing advice, reviewing, or writing code, adhere to the following guidelines:
- Follow the Uber Go style guide.
- Use the latest version of Go.
- Follow Go best practices for writing idiomatic code.
- Follow DRY principles.
- Do not use deprecated modules and functions.
- Properly handle errors.
- Include logging where appropriate.
- Include all the code, do not skip details or methods for brevity.
- Don't apologize for errors, fix them.
- Include comments in the code.
- Do not include TODO comments; write the code instead.
- Comments MUST describe purpose, not effect.
Bias towards the most efficient solution, with security and performance as a priority.
When writing tests adhere to the guidelines above, but add the guidelines below:
- Make the test a black-box test, unless asked otherwise.
- Name the test package with a _test suffix.
- Do not use third-party packages such as stretchr/testify.
- Always use methods like t.Parallel, t.Cleanup, and t.TempDir.
- Use tt := tt to capture range variable.
- Use errors.Is() instead of comparing error values directly.
Write concise answers and speak in a casual, unapologetic, and assertive tone. Minimize any other prose. Respond in Markdown."
I also use GPT-4 with ChatGPT Plus, which matters a lot.
Hopefully, this will help someone :)
https://git.sr.ht/~jamesponddotco/privytar
Still need to write tests and deploy an official instance, but the code itself should be working already. I'll consider it ready when those tasks are done and I can have a senior Go developer review the code.
I was inspired by projects like Nitter and Bibliogram. No real reason for it to exist aside from that and "because I wanted to." I guess I also don't trust Automattic all that much either.
There's also acopw, a small cryptographically secure password generator module for Go:
https://git.sr.ht/~jamesponddotco/acopw-go
I'll consider it ready once the underlying cryptographic implementations have been independently audited.
The tool made my therapy sessions more productive and richer in details, and I hope it can help others too :)
The API is still not stable, hence the version[2], but I would love some feedback or a review so I can remove the notice at the start of the README file, haha.
[1] Programming in general, really, as servers are my forte.
[2] Still debating if the Random.Generate() and PIN.Generate() should return an error or not.
[1] Two, actually, since my wife has one as well.
[1] https://git.sr.ht/~jamesponddotco/acopw-go/tree/trunk/item/w...
I recently released imgdiet[1], a simple and fast image processing and compression Go module that provides a simpler API for libvips[2]. I usually only need to optimize or resize an image, so I wrote something that lets me do just that.
The module only supports PNG and JPG images for now, but I'll be adding more formats with time. Patches are welcome and I would love the community's feedback!