hamsterkill

joined 2 years ago
[–] hamsterkill@lemmy.sdf.org 3 points 1 day ago* (last edited 1 day ago)

This was my first thought as well. Both sodium hydroxide and sodium bicarbonate seem like they could have a signficant environmental impact. We'd need some good studies on that before committing to this idea, I think.

[–] hamsterkill@lemmy.sdf.org 3 points 1 day ago

The technology plans for these fuel cells aren't "for now". They're for a future where we've hopefully already decarbonized most of the electric grid, as doing so is way more important than decarbonizing aviation. Converting fleets of airplanes to electric is a long process that will probably not be started for a while yet while there are more important carbon emission sources to tackle (aviation is only 2-3% of the emissions right now).

[–] hamsterkill@lemmy.sdf.org 1 points 6 days ago

Terminator 7: Robot Pirates

[–] hamsterkill@lemmy.sdf.org 10 points 1 week ago (1 children)

This is the point of collective bargaining contracts. A union negotiates the rules by which their members and companies interact, sign a contract, and then both are bound by that contract for the term.

The union is claiming the contract they have in place prevents the automation of voice by the bound company unless they get agreement from the union first.

[–] hamsterkill@lemmy.sdf.org 2 points 2 weeks ago

Thurott's article on this implies that "big customers like DDG will be unaffected". Though he also says information is scarce.

[–] hamsterkill@lemmy.sdf.org 5 points 2 weeks ago

Contributions will still need to be made outside of GitHub.

[–] hamsterkill@lemmy.sdf.org 5 points 2 weeks ago

Contributions will still go through phabricator rather than GitHub. GitHub does still give their greater visibility than elsewhere, though.

[–] hamsterkill@lemmy.sdf.org 16 points 2 weeks ago

They aren't using GitHub for issues, pull requests, or (that i'm aware of) pipelines.

[–] hamsterkill@lemmy.sdf.org 11 points 2 weeks ago (1 children)

Bugzilla is still where they are managing bug reports and contributions will still go through (I think) phabricator. Note the lack of Issues and Pull Request tabs on the GitHub repo. This is more just a change of hosting than anything.

[–] hamsterkill@lemmy.sdf.org 9 points 3 weeks ago* (last edited 3 weeks ago)

My interpretation of your request boils down to "what's a good co-op roguelike" where the grinding is the replaying.

So, depending on how many players you need it to support and preferred genres, you might check out games like

  • Risk of Rain 2
  • Enter the Gungeon
  • Children of Morta
  • Vampire Survivors
  • Streets of Rogue
  • Gunfire Reborn
  • Barony

There's also a game called Jumpship that i'm keeping an eye on the development of that's supposed to be hitting early access in the coming months.

[–] hamsterkill@lemmy.sdf.org 4 points 3 weeks ago (1 children)

I think Teams has already taken over there as well.

[–] hamsterkill@lemmy.sdf.org 1 points 1 month ago (1 children)

I expect the trusted authorities would be selected by the server where the user account resides. I.e. if a server's admin does not recognize a certain authority, it would not show their verifications to users logged in to their server.

It's possible that it could extend to user selections of trusted verifiers as well, but I think implementing that level of granularity would be more of pain than it's worth to Bluesky. Still, I could be surprised.

 

Rant incoming:

This was spurred by having just read https://www.androidpolice.com/google-tv-streamer-questions-answered/ , particularly this bit:

When I asked directly, a Google representative told me they couldn't confirm which chipset powers the Google TV Streamer — essentially, Google declined to answer.

I've been noticing an increasing trend by device makers to not disclose the SoC their devices run on. I've been seeing it with e-readers, network routers, media streamers, etc.

It's incredibly frustrating to have devices actively exclude important information from their spec sheet and even dodge direct questions from tech news reporters. Reporters shouldn't have to theorize about what chip is in a released device. It's nuts.

If you're wondering why this infomation is important, it can be for several reasons. SoC vendor can have significant impact on the real world performance and security of a device. It also carries major implications for how open a device is as SoC vendors can have dramatically different open source support and firmware practices.

I've had to resort to inspecting the circuit board photos of FCC filings way too much lately to identify the processors being used in devices. And that's not a great workaroud in the first place as those photos are generally kept confidential by the FCC until months after the device releases (case in point the Google Streamer).

view more: next ›