hedy boosted

@bekopharm cryptocurrency is backed by cryptography so it's definitely not fair for the former to claim the short form (as if cryptography existed FOR cryptocurrency?!)

hedy boosted

Crypto is good.

Oh you're offended? This may be because the term is occupied by currency and blockchain bros to a point where most people do not see any difference any more and start barking.

Crypto is short for cryptography, not for currency, and that's awesome stuff.

Not convinced? Without crypto you get

* No "secure" messages
* No password manager
* Your accounts free for the taking - everywhere
* Your messages public - for everyone

Let's see how many bots I can lure out.

hedy boosted
hedy boosted
hedy boosted
hedy boosted
hedy boosted
hedy boosted
hedy boosted
hedy boosted

I think my camera's SD card is failing because I'm trying to copy moon pics off of it and every ~50 photos it spontaneously and unprompted unmounts and interrupts the transfer. No issues actually writing photos to the card, which is weird…

hedy boosted

#Rust help requested. I am officially at wits end here.

Please take a look at my source file sdlstate.rs.

I'm getting a borrow checker error E0597 on line 39, indicating that tc does not live long enough. However, looking at the sdl2 sources (via its rust-docs), I don't see how my created texture, t, can possibly still refer to tc, which as far as I'm aware, is the only way this error can be generated under current conditions.

error[E0597]: `tc` does not live long enough
--> src/sdlstate.rs:39:21
14 | impl<'a> SdlState<'a> {
| -- lifetime `'a` defined here
39 | let mut t = tc
| _____________________^
40 | | .create_texture(
41 | | Some(sdl2::pixels::PixelFormatEnum::RGBA8888),
42 | | sdl2::render::TextureAccess::Streaming,
43 | | self.width,
44 | | self.height,
45 | | )
| |_____________^ borrowed value does not live long enough
49 | self.current_texture.set(Some(t));
| --------------------------------- argument requires that `tc` is borrowed for `'a`
56 | }
| - `tc` dropped here while still borrowed

Why is this happening? Why can't I re-arrange the code to prevent this from happening?

Right now, the only way this code will compile and run correctly is if I manually inject the re-paint code where I invoke f(), which utterly defeats the purpose and benefit of using closures in the first place.

In an attempt to fix this, I've tried:

  1. Replacing the Cell with RefCell.
  2. Removing Cell all-together and just using a raw Option type.
  3. Removing the 'a lifetime annotation.

None of these work, and almost always introduce some manner of errors on their own.

Please help. Thanks.

hedy boosted

@DeveloperMemes no, use site:stackoverflow.com + search across multiple search engines + search your browser history

hedy boosted

So, how do people run their own personal #fediverse instances? What software? Self-hosted or paying for hosting?

To do my part in ensuring the fediverse stays diverse, I think I'd rather not use mastodon. Also, I'd rather not run that kind of bloat on my small homelab when selfhosting


hedy boosted
hedy boosted
hedy boosted
hedy boosted

throwback to when i forgot the word “hieroglyphics” so i told someone that the ancient egyptians used to write with emojis

hedy boosted

The inclusion of any link does not imply endorsement of the site.

Show older

masto instance for the tildeverse