bss03

@bss03@infosec.pub

I’m also on Mastodon as hachyderm.io/ .

This profile is from a federated server and may be incomplete. Browse more on the original instance.

bss03,

If you can find it www.imdb.com/title/tt1228865 is a good watch. It covers other methods, but it becomes clear how fast, effective, and painless nitrogen asphyxiation can be, as the presenter has to receive assistance in order not to die while attempting to get close to the experience (without dying).

It’s also a bit sad, as it makes it clear that for at least some capital punishment advocates, suffering is a desired part of the outcome.

I’d like to avoid death, but I can foresee a potential future when my quality of life is negative and no amount of volunteer effort can bring it positive. If that happens, I’d like to opt-in to mortality via inert gas (probably nitrogen) asphyxiation.

If we must have capital punishment, inert gas asphyxiation seems to be the best known way to do it. I’m not convinced we must have capital punishment, tho.

Why is TikTok seen as privacy invading and bad, but Facebook is fine?

I’m not here to claim that Tiktok is completely harmless, or that it’s even a good site. I’m sure they absolutely do collect as much personal information as they can, and I’m sure they give it to the Chinese government whenever they ask. But I don’t understand how Meta and Facebook are meant to be any better? There’s...

bss03,

Great comment. I can’t figure out which “one” you are talking about, because I find Facebook/Meta oppressive.

bss03,

Right now? Probably.

In the past, definitely: techcrunch.com/…/amnesty-report-facebook-rohingya…

bss03,

hachyderm.io/…/111535813328842924 (This might be a duplicate, but I’m not seeing it, on my instance, yet.)

bss03,

Question (not mine) here: functional.cafe/

I think I answered it well over there. But, posting to encourage activity.

bss03,

I’d like to think having an inviting post might help… but I’m not sure. Probably should just try a manual post first, and then if it gets used enough, start rotating and scheduling.

Thanks for the quick reply!

bss03,

Is that a stormlight archive reference?

bss03,

Parsing function can return any of the types, we don’t know what was in the bytestring. So we’d need to deal with all variations in any case, no?

Yes, the parsing function could return anything, but that’s not the exclusive source of values of the GADT.

So, yes, when consuming the output of the parsing function, you have to deal with all the variations. But, when you have types that reflect some information is known about the type index, you only have to deal with the matching constructors.

This is particularly important given the copy-paste transport of code from one context to another. You might have some code that works for a MyGADT MyType and doesn’t handle all the constructors. But, when you transport that code elsewhere and ask it to handle a MyGADT a, the type system will correctly warn you that you haven’t handled all the cases. This is an improvement over writing something like case x of { Right y -> stuff y; Left{} -> error “Can’t happen; won’t happen”; }, since I’m sure works fine in the right context, but doesn’t have a type that reflects what the programmer knows about x so if it is transported to a context where that information/assumption is no longer true, that’s only discovered at runtime. (This isn’t the best example, but it’s what I have for you.)

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • tacticalgear
  • magazineikmin
  • thenastyranch
  • Youngstown
  • mdbf
  • rosin
  • slotface
  • InstantRegret
  • khanakhh
  • Durango
  • kavyap
  • osvaldo12
  • DreamBathrooms
  • JUstTest
  • GTA5RPClips
  • ngwrru68w68
  • everett
  • tester
  • ethstaker
  • cisconetworking
  • cubers
  • modclub
  • provamag3
  • anitta
  • normalnudes
  • Leos
  • lostlight
  • All magazines