Create accountLogin

Recent searches

No recent searches

Search options

Not available on dice.camp.
dice.camp is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon server for RPG folks to hang out and talk. Not owned by a billionaire.

Administered by:

Server stats:

1.7K
active users

dice.camp: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#go

6 posts5 participants0 posts today
Public *
Jay Hannah

Oooo... that's neat. Pulls your stats from OGS. avavt.github.io/gotstats/#/use #go #igo #baduk #weiqi

Over 8 years I've played 347 different people! The future is amazing! Yay Internet!

  • Member since: 18 Mar, 2017.
  • Plays 0.226 games per day on average.
  • Most active day: 30 Jun, 2018 with 14 finished games.
  • Played in 1 tournaments.
  • Longest win streak: 14 wins in a row, from Aug 26, 2023 to Sep 11, 2023.
  • Biggest win: 183.5 points victory against rabbiliu0412 (17k) on Aug 8, 2020.
  • Longest game: Aug 2, 2017 lasting 3 months 26 days 21 minutes 27 seconds
  • Congratulations, you have lost your first 50 games!
avavt.github.ioGot Stats?
Public
Luke

Spent some time this evening debugging a deadlock issue in a personal tool written in Go. It's simple with just enough complexity that it might be useful to an advanced beginner. I used delve to inspect my goroutines and figure out what was causing the application to hang. Check it out and let me know what you think. #go #delve #deadlock #debugging

blue42.net/code/go-deadlock-de

blue42.netDebugging a Go Deadlock With Delve · blue42A simple real world example of debugging a Go application deadlock using delve from the command line. The application is a personal troubleshooting tool I use at work. Everything works as expected after application startup, but hangs after running overnight. Join me as I find out why.
Public
Miguel Afonso Caetano

"It’s not that hard to build a fully functioning, code-editing agent.

It seems like it would be. When you look at an agent editing files, running commands, wriggling itself out of errors, retrying different strategies - it seems like there has to be a secret behind it.

There isn’t. It’s an LLM, a loop, and enough tokens. It’s what we’ve been saying on the podcast from the start. The rest, the stuff that makes Amp so addictive and impressive? Elbow grease.

But building a small and yet highly impressive agent doesn’t even require that. You can do it in less than 400 lines of code, most of which is boilerplate.

I’m going to show you how, right now. We’re going to write some code together and go from zero lines of code to “oh wow, this is… a game changer.”

I urge you to follow along. No, really. You might think you can just read this and that you don’t have to type out the code, but it’s less than 400 lines of code. I need you to feel how little code it is and I want you to see this with your own eyes in your own terminal in your own folders.

Here’s what we need:

- Go
- Anthropic API key that you set as an environment variable, ANTHROPIC_API_KEY"

ampcode.com/how-to-build-an-ag

ampcode.comHow To Build An Agent | AmpBuilding a fully functional, code-editing agent in less than 400 lines.
#AI#GenerativeAI#AIAgents
Public
In #Flancia we'll meet

[[g0v]] looks great:

en.wikipedia.org/wiki/G0v_move

#go g0v.tw

Gemini:

> This decentralized, non-hierarchical community of hackers, activists, and citizens develops open-source tools and platforms to promote government transparency, citizen participation, and collaborative problem-solving. They use the internet to "fork" the government – creating alternative, open versions of government services and data.

en.wikipedia.orgg0v movement - Wikipedia
Public
Csepp 🌢

One problem that I'm running into with #CPP at work that applies even more to other more dynamic languages like #Scheme is the difficulty of automated refactoring. In #Go for example it's very useful that the LSP implementation has function extraction and inlining built-in.

Public *
René Mayrhofer :verified: 🇺🇦 🇹🇼

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 (theregister.com/2025/04/03/eu_) 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 (mayrhofer.eu.org/talk/insider-). Either one-to-one communication remains secure and private, or it doesn't (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 mayrhofer.eu.org/talk/secure-m, 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 Register · EU: These are scary times – let's backdoor encryption!By Iain Thomson
ExploreLive feeds
About