• 1 Post
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle



  • TeddE@lemmy.worldtoMemes@lemmy.mlHow I like my pi
    link
    fedilink
    arrow-up
    8
    ·
    10 months ago

    As a rule of thumb, I expect that Asus as a business only cares about adbock from two angles:

    1. A feature to slap on the box for advertising.
    2. A B2B feature for helping business management make workers more productive.

    To the first, there’s little incentive to ever update the lists after you’ve bought the device, so it’s quickly outdated. To the second, it’s like to be far more optimized for Amazon or Newegg, then for Reddit. Between the two, I don’t generally expect them to hold a candle to pi-hole and similar software.







  • I’m pretty sure @[email protected] was trying to create a simplified example. To include a generic autistic tech we can modify the example to “40 people making 10 things an hour. A clever autistic person comes along and writes a computer script that improves efficiency. Now 19 people make 20 things an hour, the autistic tech makes 5 times as much as one of the original people and has the specialty job of maintaining the script, the business owner lays off 20 people (4x of their pay compensates the tech) and the business owner pockets the other 16x as extra profit”

    The 19 people still employed don’t get any more pay for their extra efficiency, nor do they get any more time off.

    The 20 people who were let go at no fault of their own now apparently don’t get to eat or live or have any kind of security until they reeducate themselves to a new line of work.

    The autistic tech doesn’t understand where their additional pay comes from, but is happy to get rewarded well for their good work.

    If questioned about why the 20 people needed to be let go, the business owner will blame the scripts efficiency instead of their own decision to pocket the money.

    However, to answer your question directly: it does not matter how many new jobs or specialty positions are created - if the net pay available to workers is reduced and the net jobs workers can fill are reduced, some workers are destined to get the short straw.





  • I think Ubuntu is a for-profit company. I think System76 is a for-profit company. As a rule, companies tend to respect other companies in ways they don’t respect people.

    I think it’s more likely that System76 will rebase to Debian than Ubuntu kick them off, but if Ubuntu really starts pulling out the brass tacks, I don’t think System76 will show any loyalty.

    In other words, I think Ubuntu benefits from counting all the Pop!_OS users as part of the Ubuntu family (at least statistics wise), that they’d be killing a golden goose by trying to evict them, even though they’d obviously prefer them to use Snaps.



  • Ahh, so this isn’t a processing issue it’s a data access issue.

    Frankly, if you can’t access the raw data of your voicemail inbox, probably no third party developer can too. This means that the only way to implement such a tool would to be to work with the voicemail provider. If they’re a for-profit company, they probably have no incentive to make the data available unless there’s a big moneybag involved somewhere in the exchange. That’s probably why no such tool exists.





  • Honestly, I say we ditch NSFW as a on/off switch and go with a mandatory tagging system. We can clarify NSFW into content warning tags, e.g. CW - Gore, CW - Death, CW - Breast, CW - Genitalia.

    Users could then set their own preferences on which tags would cause a post to be masked or simply hidden.

    But why stop there? Tags could be very useful in our federated environment to help communities mesh better with each other.

    Communities could be able to specify a list of mandatory tags, i.e. the Swallow community could require posts specify African Swallow or European Swallow (or both or neither). Communities could also make some tags implied, so the AfricanSwallow community might just imply that posts are Africian Swallow unless user changes it.

    Underneath the hood, all tags are just treated as part of the post text, so the backend performance impact will be minimal. However moderation tools would be able to consider tags when deciding how to handle a post.

    Of course, the server/instance owner can then simply make a policy of what kinds of content warnings they require, and communities can then build other tags on that to meet their community needs.