338
all 24 comments
sorted by: hot top controversial new old
[-] barsquid@lemmy.world 29 points 2 weeks ago

The results of publicly-funded pharmaceutical research also rightfully belong to the nation.

[-] volkerwirsing@feddit.org 13 points 2 weeks ago

Not just the nation - to all of mankind. To prevent people from accessing needed medicine just to gain money for your company or nation is a crime.

[-] blindbunny@lemmy.ml 27 points 2 weeks ago

I wish America had this mindset

[-] version_unsorted@lemm.ee 14 points 2 weeks ago

There is some movement, but it isn't nearly enough.

https://code.mil/

We believe that software created by the government should be shared with the public, and we want to collaborate with civic-minded peers to make this happen.

[-] blindbunny@lemmy.ml 3 points 2 weeks ago

Thanks for sharing I didn't even know this existed.

[-] sleep_deprived@lemmy.world 6 points 2 weeks ago

There's also the NSA's Ghidra which is a competitor for the best open source application IMO. Previously the only tool for heavy-duty reverse engineering was IDA Pro, which is very expensive (and not open source, of course). The NSA has selfish incentives to have tools like this be open source - free training especially - but it's still a very good thing.

[-] blindbunny@lemmy.ml 2 points 2 weeks ago* (last edited 2 weeks ago)

I don't know anything about reverse engineering but this seems like fills a void as you mentioned. Thanks for sharing. Is there a fork for Linux?

[-] TheTechnician27@lemmy.world 3 points 2 weeks ago

Ghidra is written in Java which is cross-platform.

[-] blindbunny@lemmy.ml 2 points 2 weeks ago

Thanks I just read that after editing the post 🤦‍♂️

[-] sleep_deprived@lemmy.world 2 points 2 weeks ago

Don't feel too bad. A lot of more complicated Java programs utilize JNI with platform-specfic code, so even if you knew it was Java, it's not a given that it works on Linux - especially given the incredibly complicated nature of decompilation, and that Ghidra has a DSL to define processors/"languages".

[-] Andromxda@lemmy.dbzer0.com 2 points 2 weeks ago

It works natively on Linux

[-] mvirts@lemmy.world 10 points 2 weeks ago

https://github.com/orgs/GSA/repositories?type=all

Not just open source, public domain. I also see that any pull request submitters must automatically agree to dedicate their work to the public domain for some of the repos I looked at.

[-] Andromxda@lemmy.dbzer0.com 6 points 2 weeks ago

That's actually cool! Iceland goes even further, and publishes the code for all their digital government services on GitHub: https://github.com/island-is

I was fascinated when I first saw this

[-] blindbunny@lemmy.ml 2 points 2 weeks ago

Wow I feel kinda dumb I never even heard of U.S. General Services Administration let alone all the public domain software they've created. My only question is, is any of it useful for a pleb like me or is it public domain for transparencies sake?

[-] mvirts@lemmy.world 1 points 2 weeks ago

Honestly I have no idea, some of it looks like good examples of what bureaucratic software development produces. I personally guarantee that almost all of that software is probably written by contractors 😹

[-] RagingHungryPanda@lemm.ee 11 points 2 weeks ago

Think of all the hard coded auth credentials!

[-] jagged_circle@feddit.nl 6 points 2 weeks ago

Gonna be fun to see all the weapons systems on github

[-] thesmokingman@programming.dev 0 points 2 weeks ago

While I’m all for opening up codebases after release and seeking contributions from constituents, the landing page has some terrible ideas.

Similar applications don't have to be programmed from scratch every time.

Unless there are very solid guidelines that offer a lot of flexibility to do the opposite and code things from scratch every now and then, you get very pervasive legacy antipatterns. I have struggled to effect positive software change as an SRE at massive enterprises because of this idea. Conway’s Law does a good job describing how this stratifies code. I have also spent more than year trying to get disparate acquisitions on the same tech stack with ballooning requirements as everyone tries to get their interests in. I left that one without any real movement.

Major projects can share expertise and costs.

This goes against lean principles that see the best outcomes and exponentially increases the waterfall slog most government projects are. The more stakeholders the more scope creep. Your platform team can be shared; you don’t want your stream-aligned teams to get stuck in this mire. They need to be delivering the minimum viable solution for their project.

Assuming the software is just released with an open license and the public can contribute, hell yeah. I have contributed to so many projects that I actively use in my day job and there’s plenty of shitty government software I'd love to poke at. The two things I called out require a serious amount of executive buy-in for developer tools and experience which turns into a project itself. In the private world most companies chicken out when they realize they’ve got serious cost centers just making development easier, even if their product is serious software development. I worked for a major US consultancy that talked this big game and dropped everyone the second they were on the bench. In the public sector? Fuck. It’s hard enough to get people to understand attack surfaces much less the improvements a smooth DevX with a great pipeline can provide.

this post was submitted on 17 Oct 2024
338 points (99.4% liked)

Europe

1466 readers
408 users here now

News and information from Europe 🇪🇺

(Current banner: La Mancha, Spain. Feel free to post submissions for banner images.)

Rules (2024-08-30)

  1. This is an English-language community. Comments should be in English. Posts can link to non-English news sources when providing a full-text translation in the post description. Automated translations are fine, as long as they don't overly distort the content.
  2. No links to misinformation or commercial advertising. When you post outdated/historic articles, add the year of publication to the post title. Infographics must include a source and a year of creation; if possible, also provide a link to the source.
  3. Be kind to each other, and argue in good faith. Don't post direct insults nor disrespectful and condescending comments. Don't troll nor incite hatred. Don't look for novel argumentation strategies at Wikipedia's List of fallacies.
  4. No bigotry, sexism, racism, antisemitism, dehumanization of minorities, or glorification of National Socialism.
  5. Be the signal, not the noise: Strive to post insightful comments. Add "/s" when you're being sarcastic (and don't use it to break rule no. 3).
  6. If you link to paywalled information, please provide also a link to a freely available archived version. Alternatively, try to find a different source.
  7. Light-hearted content, memes, and posts about your European everyday belong in !yurop@lemm.ee. (They're cool, you should subscribe there too!)
  8. Don't evade bans. If we notice ban evasion, that will result in a permanent ban for all the accounts we can associate with you.
  9. No posts linking to speculative reporting about ongoing events with unclear backgrounds. Please wait at least 12 hours. (E.g., do not post breathless reporting on an ongoing terror attack.)

(This list may get expanded when necessary.)

We will use some leeway to decide whether to remove a comment.

If need be, there are also bans: 3 days for lighter offenses, 14 days for bigger offenses, and permanent bans for people who don't show any willingness to participate productively. If we think the ban reason is obvious, we may not specifically write to you.

If you want to protest a removal or ban, feel free to write privately to the mods: @federalreverse@feddit.org, @poVoq@slrpnk.net, or @anzo@programming.dev.

founded 4 months ago
MODERATORS