How-To: Real-Time Dashboards with Go and PostgreSQL (Without Polling)
#golang
medium.com/@josesomojo...
1
0
0
0
Hashtag
#goLang
Advertisement · 728 × 90
A terminal workflow recorder that turns debugging sessions into re-playable, shareable artifacts.
#golang
github.com/AmalChandru...
0
0
0
0
goshs < 2.0.0-beta.3 has a critical path traversal bug (CVSS 9.8) 🛡️. Attackers can write files anywhere on the server. Upgrade to 2.0.0-beta.3 or newer now! radar.offseq.com/threat/cve-2026-35392-cw... #OffSeq #Vulnerability #GoLang
0
0
0
0
Build reactive Web Components in pure Go—no JS framework.
Create custom elements with data binding, conditional views, list rendering, two-way forms, hash routing, and parent-child communication—all in Go, running in the browser.
#golang
github.com/luisfurquim...
0
0
0
0
0
0
0
0
CRITICAL: goshs (<2.0.0-beta.3) has a path traversal flaw. Attackers can write files outside intended dirs. Upgrade to 2.0.0-beta.3 ASAP! 🔒 radar.offseq.com/threat/cve-2026-35393-cw... #OffSeq #Vulnerability #GoLang
0
0
0
0
🚀 Tebeka Shorts #54!
In this episode, @tebeka.bsky.social shows a cleaner, more maintainable way to work with regular expressions in #golang, by naming your capture groups instead of relying on positions.
📺Watch now to simplify how you extract data from complex strings:
youtu.be/GOXpxIvfUCE
0
0
0
0
🔥Nuevo video de YouTube🔥
youtu.be/sepnaB3-rnY
Espero que os guste y sobre todo que os ayude a aprender algo nuevo.
#golang #golanguage
0
0
0
0
🔥Nuevo video de YouTube🔥
youtu.be/sepnaB3-rnY
Espero que os guste y sobre todo que os ayude a aprender algo nuevo.
#golang #golanguage
0
0
0
0
0
0
0
0
I wrote a blog post about a CMS I started writing a few years ago that focuses on security: nwcs.sh/blog/weblet-...
Thoughts?
#technology #infosec #blog #coding #golang #webdev
1
0
0
0
🧵 took up a new challenge building "Distributed Services with Go" by @travisjeffery.bsky.social
following the book, writing as I learn and sharing what my curious mind finds along the way...
pragprog.com/titles/tjgo/distributed-services-with-go/
#golang #distributedsystems #learninpublic #sre
1
0
3
0
a log offset is defined as uint64 in Go. not int. not int64.
because an offset can never be -ve, index -3 makes no sense. By choosing uint64, the compiler refuses it for you
So, your types are encoding business rules. wow!
ashwiniag.com/uint64-what-...
#golang #distributedsystems #buildinpublic
3
1
1
1
wow! your database doesn't store state, it stores a log of events. state is just what you get when you replay it.
so, etcd does this every time a new Kubernetes node joins, it replays the log to catch up to current cluster state.
#golang #kubernetes #learninpublic
1
0
1
1
which Mutex should you use in Go?
None? or sync.Mutex or sync.RWMutex, the answer comes from one question: who is touching this data concurrently?
wrote about how to reason through it 👇
ashwiniag.com/which-mutex-to-use-in-go/
#golang #distributedsystems #buildinpublic #learninpublic
1
0
0
1
🚀 FullStack Engineer - Product Security @ Lovable (Stockholm) – Build fast end‑to‑end security features for the most secure AI‑powered platform. Tech: React/TS, Go, Rust, Cloudflare, GCP/AWS, LLMs, Terraform. #FullStack #Security #AI #golang #rustlang #React aihackerjobs.com/company/lova...
0
0
0
0
New article: The Go System Monitor
How sysmon, a thread with no P, keeps the runtime fair. It preempts goroutines, retakes Ps from syscalls, forces GC every 2 minutes, and ensure network poller keeps ticking.
The Go's watchdog internals-for-interns.com/posts/go-sys...
#golang #go #runtime
1
1
0
0
was working on a string problem in Go and hit this quietly
len("café") returns 5, not 4.
len() counts bytes, not characters. é is 2 bytes in UTF-8.
use len([]rune(s)) when you actually want character count.
the small things that matter in prod.
#golang #go #learninpublic
4
0
0
0
wrote about the slice gotcha that bites every engineer in production.
b := a doesn't copy your data, it copies the header. your original slice WILL be affected.
ashwiniag.com/arrays-vs-sl...
#golang #go
1
1
0
0
And `Den`got a proper documentation now too.
den-odm.readthedocs.io/en/stable/
#golang #happyhacking
0
0
0
0
![screenshot of the first page of my “Stamp It! All Programs Must Report Their Version” blog post:
Recently, during a production incident response, I guessed the root cause of an outage correctly within less than an hour (cool!) and submitted a fix just to rule it out, only to then spend many hours fumbling in the dark because we lacked visibility into version numbers and rollouts… 😞
This experience made me think about software versioning again, or more specifically about build info (build versioning, version stamping, however you want to call it) and version reporting. I realized that for the i3 window manager, I had solved this problem well over a decade ago, so it was really unexpected that the problem was decidedly not solved at work.
In this article, I’ll explain how 3 simple steps (Stamp it! Plumb it! Report it!) are sufficient to save you hours of delays and stress during incident response.
[…]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:eb3563jmh2vjnrlkwujxqdwg/bafkreibmyjp2vprkz3vd4quze4ptlmt5sgz32mjc2bycogzwu6ps2odxpq)
screenshot of the first page of my “Stamp It! All Programs Must Report Their Version” blog post: Recently, during a production incident response, I guessed the root cause of an outage correctly within less than an hour (cool!) and submitted a fix just to rule it out, only to then spend many hours fumbling in the dark because we lacked visibility into version numbers and rollouts… 😞 This experience made me think about software versioning again, or more specifically about build info (build versioning, version stamping, however you want to call it) and version reporting. I realized that for the i3 window manager, I had solved this problem well over a decade ago, so it was really unexpected that the problem was decidedly not solved at work. In this article, I’ll explain how 3 simple steps (Stamp it! Plumb it! Report it!) are sufficient to save you hours of delays and stress during incident response. […]
![screenshot of the last page of my “Stamp It! All Programs Must Report Their Version” blog post:
Conclusion: Stamp it! Plumb it! Report it!
My argument is simple:
Stamping the VCS revision is conceptually easy, but very important!
For example, if the production system from the incident I mentioned had reported its version, we would have saved multiple hours of mitigation time!
Unfortunately, many environments only identify the build output (useful, but orthogonal), but do not plumb the VCS revision (much more useful!), or at least not by default.
Your action plan to fix it is just 3 simple steps:
Stamp it! Include the source VCS revision in your programs.
This is not a new idea: i3 builds include their git-describe(1) revision since 2012!
Plumb it! When building / packaging, ensure the VCS revision does not get lost.
My “VCS rev with NixOS” case study section above illustrates several reasons why the VCS rev could get lost, which paths can work and how to fix the missing plumbing.
Report it! Make your software print its VCS revision on every relevant surface, for example:
[…]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:eb3563jmh2vjnrlkwujxqdwg/bafkreie44kyf3bi262fe6se54yj26txtvxmx6dwqk6jrtqhum7a7is2gs4)
screenshot of the last page of my “Stamp It! All Programs Must Report Their Version” blog post: Conclusion: Stamp it! Plumb it! Report it! My argument is simple: Stamping the VCS revision is conceptually easy, but very important! For example, if the production system from the incident I mentioned had reported its version, we would have saved multiple hours of mitigation time! Unfortunately, many environments only identify the build output (useful, but orthogonal), but do not plumb the VCS revision (much more useful!), or at least not by default. Your action plan to fix it is just 3 simple steps: Stamp it! Include the source VCS revision in your programs. This is not a new idea: i3 builds include their git-describe(1) revision since 2012! Plumb it! When building / packaging, ensure the VCS revision does not get lost. My “VCS rev with NixOS” case study section above illustrates several reasons why the VCS rev could get lost, which paths can work and how to fix the missing plumbing. Report it! Make your software print its VCS revision on every relevant surface, for example: […]
New blog post 🥳
Stamp It! All Programs Must Report Their Version
In this article, I’ll explain how 3 simple steps (Stamp it! Plumb it! Report it!) are sufficient to save you hours of delays and stress during incident response.
Read more: michael.stapelberg.ch/posts/2026-0...
#nix #golang #linux
11
3
1
0
A quiet, productive day so far:
- Released 0.4.0 of my ODM `Den` with new features and bug fixes.
- Switched my web framework `Burrow` from Bun to Den and released 0.11.0.
- Moved the documentation for Burrow to readthedocs.
burrow.readthedocs.io/en/stable/
#golang #happyhacking
0
0
1
0
A quiet, productive day so far:
- Released 0.4.0 of my ODM `Den` with new features and bug fixes.
- Switched my web framework `Burrow` from Bun to Den and released 0.11.0.
- Moved the documentation for Burrow to https://burrow.readthedocs.io/en/stable/
A Sunday, that makes me happy.
#golang […]
1
0
0
0
Midday Commander, il file manager da terminale che rinnova l’esperienza classica con funzioni moderne #Linux #Terminal #GoLang #Software #Windows #FileManager
1
0
0
0
A Go-based open-source task management with lists, Kanban, Gantt, and more
#golang
github.com/go-vikunja/...
5
0
0
0
Back in 2017 I created slurp S3 bucket scanner. Today, I have updated it: codeberg.org/nwcs/slurp
Why might you care? There is now -cloud-endpoint which you can now use to scan any s3 compatible cloud. Have fun!
#golang #netsec #infosec #aws #s3 #cloud
1
0
0
0
I just went live on #twitch https://www.twitch.tv/behavior_undefined - MnM Beta: Some Ancient Crypts Rogue leveling #godot #programing #golang
1
1
0
0
I just went live on #twitch https://www.twitch.tv/behavior_undefined - MnM Beta: Some Ancient Crypts Rogue leveling #godot #programing #golang
3
1
0
0