Jonkman Microblog
  • Login
Show Navigation

  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Notices by clacke (clacke@social.heldscal.la), page 47

  1. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 03:15:56 EDT clacke clacke
    in reply to
    • clacke
    • Sal Torito
    @saltorito Another evil measurement that comes to mind is the floppy MB, where 1.44 MB = 1440 KB = 1.44 * 1000 * 1024 bytes. I used it for years without realizing the inconsistency.
    In conversation Tuesday, 15-May-2018 03:15:56 EDT from social.heldscal.la permalink
  2. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 03:09:00 EDT clacke clacke
    in reply to
    • clacke
    • Vee Satayamas
    • Champion AR-15
    • Ligma Balzac
    @veer66 @skoll3 @ayy When using containers, of course you can actually enforce mounting the /nix volume read-only.
    In conversation Tuesday, 15-May-2018 03:09:00 EDT from social.heldscal.la permalink
  3. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 03:07:56 EDT clacke clacke
    • Vee Satayamas
    • Champion AR-15
    • Ligma Balzac
    @ayy @veer66 @skoll3 Don't. :-)

    /nix/store is supposed to be read-only, except when creating new paths. That's why hardlinking is considered a safe optimisation.
    In conversation Tuesday, 15-May-2018 03:07:56 EDT from social.heldscal.la permalink
  4. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 03:00:34 EDT clacke clacke
    • Sal Torito
    @saltorito Carefully fact-checking only the inch definition part, it was indeed the case that the US yard was 3600 / 3937 m, whereas the UK yard was 3600 / 3937.0113 m, so their inches were 25.4000508 mm and 25.3999779 mm, respectively.

    https://en.wikipedia.org/wiki/Mendenhall_Order

    https://en.wikipedia.org/wiki/International_yard

    Swedish angle or not, a difference in < 0.0001 mm/in probably was smaller than the tolerance of any hand-held measures, and small enough to not matter in most 1927-1933 engineering.
    In conversation Tuesday, 15-May-2018 03:00:34 EDT from social.heldscal.la permalink
  5. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 02:44:20 EDT clacke clacke
    • Sal Torito
    @saltorito Apparently "metric foot" and "metric inch" with the meanings 300 mm and 25 mm have been used in the construction industry as well:

    https://en.wikipedia.org/wiki/ISO_2848
    In conversation Tuesday, 15-May-2018 02:44:20 EDT from social.heldscal.la permalink
  6. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 02:41:05 EDT clacke clacke
    in reply to
    • clacke
    • Sal Torito
    @saltorito People called it the "metric inch", but the actual metric inch is the modern 25.4 mm inch.

    Fun anecdote please don't fact check:

    When time came to standardize the inch, the British and US inches were of course slightly different. One was slightly longer than 25.4 mm, one slightly shorter. 25.4 mm was a reasonable compromise.

    Now people were worried they would have to throw away all their measures and buy new 25.4 mm measures. But it turned out they had all been using Swedish measures, which were already 25.4 mm to be able to sell them to both markets and be accurate enough.
    In conversation Tuesday, 15-May-2018 02:41:05 EDT from social.heldscal.la permalink
  7. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 02:36:42 EDT clacke clacke
    • Sal Torito
    @saltorito Reminds me of the Soviet 25 mm "electronics inch" which made Western replacement components *almost* fit:

    https://en.wikipedia.org/wiki/History_of_computer_hardware_in_Soviet_Bloc_countries
    In conversation Tuesday, 15-May-2018 02:36:42 EDT from social.heldscal.la permalink
  8. Dr. Roy Schestowitz (罗伊) (schestowitz@joindiaspora.com)'s status on Tuesday, 15-May-2018 01:56:43 EDT Dr. Roy Schestowitz (罗伊) Dr. Roy Schestowitz (罗伊)

    #eff and clueless media that parrots the EFF may "Expose OpenPGP Users" to FUD http://www.eweek.com/security/efail-email-encryption-vulnerabilities-expose-openpgp-users-to-risk

    In conversation Tuesday, 15-May-2018 01:56:43 EDT from joindiaspora.com permalink Repeated by clacke

    Attachments

    1. Invalid filename.
      Efail Email Encryption Vulnerabilities Expose OpenPGP Users to Risk
      from eWEEK
      Researchers detail a series of flaws in the widely deployed OpenPGP and S/MIME standards that could potentially enable attackers to decrypt encrypted emails.
  9. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 02:28:48 EDT clacke clacke
    • zerohedge
    @zerohedge Putin's persistent propaganda push proceeds predictably.
    In conversation Tuesday, 15-May-2018 02:28:48 EDT from social.heldscal.la permalink
  10. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 02:16:31 EDT clacke clacke
    in reply to
    • clacke
    • Vee Satayamas
    • Champion AR-15
    @veer66 @skoll3 Docker allows some dedup by basing images on other images, so at least the "whole operating system" bit is often not a huge deal. All dependencies beyond the base system will usually be repeated several times in different images, though.

    Nix also does per-file hard link dedup, so even if each library -- and even several derivations of the exact same version of a library, but with different versions of its dependencies -- may have its own directory, a lot of space can be saved by running `nix optimise-store` or including `auto-optimise-store = true` in nix.conf.
    In conversation Tuesday, 15-May-2018 02:16:31 EDT from social.heldscal.la permalink
  11. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 02:12:22 EDT clacke clacke
    • Vee Satayamas
    • Champion AR-15
    @skoll3 @veer66 Sounds correct.

    * AppImage - same as Flatpak (re: this aspect)
    In conversation Tuesday, 15-May-2018 02:12:22 EDT from social.heldscal.la permalink
  12. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 02:10:49 EDT clacke clacke
    • Piggo
    • Spencer Alves
    @impiaaa @mightypork They usually do mention GDPR.

    GDPR is a bother. I would be worried about providing any network services without consulting expensive lawyers.
    In conversation Tuesday, 15-May-2018 02:10:49 EDT from social.heldscal.la permalink
  13. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 02:05:55 EDT clacke clacke
    • Del
    @welshpixie Trademarks are not only geographically limited, but also limited to a business field. Hypothetically you could start a Starbucks record company and be in the clear, but in practice huge corps have superior bullying power. But for corp vs corp, see e.g. Apple Records vs Apple Computers.

    But yeah, a business that has no presence in a country generally can't say anything about their trademark. And, as you noted, there's no Mamma Mia pizza chain, so every town has a local Mamma Mia (and another dozen pizzeria trope names) and it's totally fine.
    In conversation Tuesday, 15-May-2018 02:05:55 EDT from social.heldscal.la permalink
  14. peter hessler @openbsd (phessler@bsd.network)'s status on Monday, 14-May-2018 09:32:43 EDT peter hessler @openbsd peter hessler @openbsd
    in reply to

    Holy shit, that was a boring ass-vulnerability. Shame on EFF for being scary, and HTML email is Satan. We Told You So(tm)

    In conversation Monday, 14-May-2018 09:32:43 EDT from bsd.network permalink Repeated by clacke
  15. cynicalsecurity :cm_2: (cynicalsecurity@bsd.network)'s status on Monday, 14-May-2018 10:10:31 EDT cynicalsecurity :cm_2: cynicalsecurity :cm_2:

    At times I wonder what exactly HTML-enabled e-mail has improved:

    * phishing, definitely,
    * illegible e-mail because fonts & stuff never look the same at the other end,
    * bandwidth wastage,
    * forcing people to "load remote content".

    Once I was in an argument where HTML e-mail was meant to help those visually impaired but surely a text reader has a much better chance of getting it right with plain text?

    In conversation Monday, 14-May-2018 10:10:31 EDT from bsd.network permalink Repeated by clacke
  16. clacke (clacke@social.heldscal.la)'s status on Tuesday, 15-May-2018 01:47:41 EDT clacke clacke
    I consider info-zip, not PKZIP, the de facto standard implementation for ZIP files. It's free software and it is available on VMS, MS-DOS, and uncountable[0] other platforms, and it has been implementing extensions like 64-bit support, bzip2 compression and more.

    But it seems info-zip.org has expired and is controlled by a domain squatter.

    The latest versions released were Zip 3.0 in 2008 and Unzip 6.0 in 2009.

    Is it perfected? OOXML 2016 and OD v1.2 from 2015 define PKZIP 6.2.0 from 2004 as their ZIP, but the latest ISO/IEC 21320-1:2015 ZIP standard uses the 2012 PKZIP 6.3.3 definition.

    Steven Schweda [1] posted a comment to the SourceForge tracker just a few months ago, so it seems the project is alive in some capacity. 3.1 and 6.1 betas were mentioned in their forums in 2015.

    [0] Hyperbole. Just go to the release notes and count them: http://infozip.sourceforge.net/UnZip.html

    [1] https://sourceforge.net/u/antinode2/profile/
    In conversation Tuesday, 15-May-2018 01:47:41 EDT from social.heldscal.la permalink
  17. clacke (clacke@social.heldscal.la)'s status on Monday, 14-May-2018 23:47:25 EDT clacke clacke
    @gameragodzilla I try to only use "nincompoop".
    In conversation Monday, 14-May-2018 23:47:25 EDT from social.heldscal.la permalink
  • After
  • Before
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.