what the fuck lmao
- 1 Post
- 14 Comments
jbk@discuss.tchncs.deto Technology@lemmy.world•California Bill Would Require That AT&T And Comcast Make Broadband Affordable For Poor PeopleEnglish6·2 days agohow much subsidies has the taxpayer provided to these parasites?
thought you were talking about poor people at first lol
jbk@discuss.tchncs.deto Lemmy Shitpost@lemmy.world•The clueless people are out there among us4·2 days agothat sounds like hell lmao where
jbk@discuss.tchncs.deto Showerthoughts@lemmy.world•Digital security and encryption in Movies and TV Shows are in a superposition of being unbreakable and weak, depending on plot convienience.5·4 days agoAren’t most things if you know more in those fields than the average joe?
jbk@discuss.tchncs.deto Showerthoughts@lemmy.world•Digital security and encryption in Movies and TV Shows are in a superposition of being unbreakable and weak, depending on plot convienience.1·4 days agoa simple BIOS/UEFI setting change, or windows update could trip the Secure Boot settings they could work around that though, but I still agree that backing up the passphrase to an arguably safe online system is good
jbk@discuss.tchncs.deto World News@lemmy.world•Mother of autistic boy left with £10,000 debt after breaching DWP rules by £1.92 a weekEnglish152·5 days agoterf island again being shitty
jbk@discuss.tchncs.deto linuxmemes@lemmy.world•Who needs stable, feature-rich desktops anyway1·5 days agoSo things like sandboxing or even not running everything as root should exist.
jbk@discuss.tchncs.deto linuxmemes@lemmy.world•Who needs stable, feature-rich desktops anyway11·5 days agoThey’re useful, “old” is no excuse.
the above tl;dr forgot something massive: all current protocols are unsafe (e.g. need exporting the entirety of org.kde.* in dbus) and/or only work on X11
jbk@discuss.tchncs.deto linuxmemes@lemmy.world•Who needs stable, feature-rich desktops anyway52·5 days agoa single setting like that being a dealbreaker for a whole DE
seems a bit like an overreaction
with ISO 8601:
Sure, how about 2018-W06-1? Or 2018-036?
ISO 8601 contains way too many obscure formats. RFC 3339 is pretty much a subset and defines only sensible ones. It also allows 2018-02-05 08:02:43-00:00 (no T and explicitly specifying no timezone)
Unused storage is wasted storage
and what about enby grandparents?