[–] 84 points 4 days ago (5 children)

Schumer and Jeffries, and whomever is pulling their strings, must be excised from the party immediately if there's going to be any real change.

  • source
  • [–] 10 points 4 days ago*

    I was disappointed when I found GOG had Ultima titles, they were the old IBM CGA versions, with ugly gfx and bad or no music. Why didn't they license the Atari or Amiga versions and just bundle with an emulator?

    ..and yeah, fuck EA. Never give them a nickel, most of those can be found on the High Seas, I bet. Yaar.

  • source
  • [–] 2 points 1 week ago* (last edited 1 week ago)

    Ha. At the bottom in the related articles list: "Your AI agent fixed the bug, but what else did it change?"

    Is as much time saved as is likely claimed, if hundreds of generated backports are actually subjected to the review scrutuny they really deserve?

  • source
  • [–] 1 point 1 week ago (1 child)

    He can't speak for all engineers, either. He can feel however he wants about how to approach game design. A game designer who decides they enjoy 'turning graph paper into hex digits' is not irrelevant, if the game they put out is fun, and the art is still valid.

    Not everything in our lives needs to be about 'efficiency'. We're always being pushed to the point of burn-out as if it's a virtue, and we should be damn sick of being made to feel guilty for not doing things the way 'some rich exec' says it should be.

  • source
  • parent
  • context
  • [–] 42 points 1 week ago (2 children)

    Deleted my ProtonMail account last evening. Quoted the 404media article from yesterday and demanded his removal as CEO in my cancellation comment. For what it's worth.

    Hopefully if thousands of users do the same it might penetrate the veil of CEO-impunity.

  • source
  •  

    It's pretty simple, really just a proposal to standardize on an admin policy. No new APIs, works with any legacy system (systemd or not), not even Linux-centric, pure POSIX/UNIX. Here goes:


    Define standard groups which *may* be present. Make each user a member of three groups: YOBnnnn, MOBmm, DOBdd, where:
    
    YOBnnnn = Year of Birth, eg. YOB1981
    MODmm = Month of Birth, eg. MOB01
    DOBdd = Day of Birth, eg. DOB03
    
    So to define an age for user 'jsmith' born Jan 3, 1981, just define three groups YOB1981, MOB01, DOB03. add user 'jsmith' to these 3 groups.
    
    Only a system admin can add users to groups, so this ensures it's admin-enforced and users can't change their own age verification.
    The groups can be defined only as required, so a system with only a few users will only have a few of these YOB/MOB/DOB groups defined and it's easy to add or remove them at any time.
    Querying a user's age is as simple as calling standard POSIX APIs to see which groups a user is a member of, and extracting the numerical suffix of any groups of pattern {YOB, MOB, DOB}.
    

    If a system doesn't want to do age verification, just don't define or assign these groups to anyone; it's up to apps to assume the age is either satisfied or not when groups are absent for a user.

    If privacy is a concern, assign only YOB (or YOB and MOB), not DOB group, so exact age is not defined (with the loss of some precision, eg., someone 17 years of age isn't considered 18 until the start of the following month after their real birthday if a DOBdd group isn't assigned to their user).


    If age verification were required to be done by 'age classes' rather than YOB/MOB/DOB, define a group corresponding to one's legal region requirements (I've heard California wants: '13 and under', '14-17' and '18+' or something like that). So just define groups 'AC0', 'AC1', 'AC2', 'AC3' for each age group, and assign users to one of those groups as appropriate. Again, apps just need to use standard APIs to check what groups a user is a member of in order to determine their age group.

    view more: next ›