Recent searches
Search options
#go
Releasing these for my birthday 
I'm excited to share that the complete Let's Go Project is released now:
https://soumyak4.in/project/Lets-Go/
New version (v4) of the Go Game Roadmap, visit/install it here :
https://weiqi.soumyak4.in
The first version of BadukTube, the free lectures directory, visit/install it here :
https://baduktube.soumyak4.in
Let’s continue to enjoy, learn, and master the game of Go together 
#go #gogame #baduk #weiqi #chess #boardgames #2025 #strategygames #mindsports #birthday #igo
Sigh. We are, as a security community, making good progress on some old as well as some new topics. #Rust, #Go, and other memory safe systems languages are going well and having a real impact in reducing memory safety issues - which has been the most important security bug class for decades, and we are finally improving! Compartmentalization and isolation of processes and services have now become common knowledge and the minimum bar for new designs. Security and privacy by design are being honored in many new projects, and not just as lip service, but because the involved developers deeply believe in these principles nowadays. #E2EE is finally available to most end-users, both for messaging and backups.
And again and again, we are forced into having discussions (https://www.theregister.com/2025/04/03/eu_backdoor_encryption/) about breaking all the progress.
Let me be clear for Nth time:
* We *cannot* build encryption systems that can only be broken by the "good guys". If they are not completely secure, foreign enemy states, organized crime, and intimate partners will break and abuse them as well. There is no halfway in this technology. Either it is secure or it isn't - for and against everybody.
* We *cannot* build safe, government-controlled censorship filters into our global messaging apps that are not totally broken under the assumption of (current or future) bad government policies and/or insider attacks at the technology providers (https://www.mayrhofer.eu.org/talk/insider-attack-resistance-in-the-android-ecosystem/). Either one-to-one communication remains secure and private, or it doesn't (https://www.ins.jku.at/chatcontrol/).
* We *cannot* allow exploitation of open security vulnerabilities in smartphones or other devices for law enforcement. If they are not closed, they are exploitable by everybody. "Nobody but us" is an illusion, and makes everybody less secure.
My latest recorded public talk on the topic was https://www.mayrhofer.eu.org/talk/secure-messaging-and-attacks-against-it/, and nothing factual has changed since then. Policymakers keep asking for a different technological reality than the one we live in, and that sort of thing doesn't tend to produce good, sustainable outcomes.
(Edited to only fix a typo. No content changes.)
CC @epicenter_works @edri @suka_hiroaki @heisec @matthew_d_green @ilumium
The Story Behind 100 Go Mistakes and How to Avoid Them https://lobste.rs/s/etlc6s #go
https://www.thecoder.cafe/p/100-go-mistakes
It's nice when you finish a bit of work that goes well and requires no yak shaving in order to get done.
For the past week I've been struggling again with the #frontend bits of #ONI, the single user #ActivityPub server, when I decided to take a little break and work on something else.
So today I've add support for the traversal resistant file API for the FS storage part of #GoActivityPub. I'm still waiting for the symlink support to be added in the next major #Go version, but other than that we've increased robustness a little bit despite it being designed mainly for full transparency development work and not being run in production environments.
I took some time to collect my thoughts on the age-old argument: what explains the aversion to assertion-based testing frameworks in Go?
https://matttproud.com/blog/posts/testing-frameworks-and-mini-languages.html
In particular:
1. Where did the tension come from?
2. How could it have arisen?
3. What is the philosophical basis for it
4. What are the implications of using one of these frameworks?
5. How does the assertion framework question fit in the overall psychological preference space of software developers?
I haven't painted anything #GO-related in some time, for a number of reasons... But the other day I was thinking about S3 and its possible twists, and I decided to go with the flow and paint this #Crowley and #Aziprahale inspired #hands <:
I’m interested in seeing Fedi’s opinion on this. Also reply with a more detailed opinion and your language of choice if you feel so inclined. Boost if you are interested in this too.
When my compiler reports an error, I most often see this as:
A quick recipe — how to debug individual table test rows in Go in a low-friction, development environment-neutral way:
https://matttproud.com/blog/posts/debugging-go-table-tests.html
Well, this is a little worrying. I hope there's a maintainer out there that can find 10 minutes to tag a new version. In the meanwhile using the unstable version works well enough as there's no API changes.
https://mastodon.social/@golang_discussions/114272847659788808
More predictable benchmarking with testing.B.Loop https://lobste.rs/s/mblorq #go #performance
https://go.dev/blog/testing-b-loop
#Help My current #PC is aging, i7-6700, 12GB of ram (16gb max) and it can't do 4k. I want to replace my dual monitor setup with a single #4K. Do I just get a cheap video card that can do 4k or do I just build up a new machine?
If you say new machine, I only do #development stuff, #Python, #C/C++, #Rust, #Go, blah blah blah, #Virtualization, #containers.... #AMD or #Intel? Built in graphics is more than good enough for me. I can't make up my mind, help me :)
I was trying to read a book on Go and follow along, but struggled for anything to sink in.
After a couple of months of making no progress I decided to rewrite a small #python project in #go
Although I've been moving at a snails pace compared to writing python. I have learned and retained more than just reading a book.
