dmv.community is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small regional Mastodon instance for those in the DC, Maryland, and Virginia areas. Local news, commentary, and conversation.

Administered by:

Server stats:

160
active users

#go

1 post1 participant0 posts today

Limeleaf@limeleaf@social.coop

"We are a worker-owned cooperative that helps teams build fast, reliable, maintainable software using Go and Rust.We're also building ethical, privacy-focused, and open source products for real people and the #Fediverse. We're currently working on limecast.net and apply.coop"

mastodon.social/@limeleaf@soci

Limecast - A Privacy-First Podcasting PlatformLimecast - A Privacy-First Podcasting PlatformComing soon: Limecast, a privacy-first, open-source, distributed podcasting platform.
#coOp#rust#go

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

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?

matttproud.com/blog/posts/test

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?

matttproud.com (blog) · Testing Frameworks and Mini-Languages
More from mtp
#Go#Golang#SWE

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:

#rust#cpp#c

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.

@icecolbeveridge Compare the technique of "tewari", from the game of Go, which asks, "Would these moves have been effective if played in a different order?"

(This makes more sense for Go, a game of placement, than for Chess, a game of movement.)

senseis.xmp.net/?Tewari

senseis.xmp.netTewari at Sensei's LibrarySensei's Library, page: Tewari, keywords: Theory. SL is a large WikiWikiWeb about the game of Go (Baduk, Weiqi). It's a collaboration and community site. Everyone can add comments or edit pages.
#go#igo#baduk