• 5 Posts
  • 816 Comments
Joined 4 years ago
cake
Cake day: June 28th, 2020

help-circle




  • You are supposed to do feature detection, not user agent detection since it is easily spoofed, isn’t realiable, & doesn’t account for literally all the alternative UAs that can support it. This is bad/lazy practice.

    Fx doesn’t always have all the features you need, but often it usually does & where I have seen this as being deployed is management saying it isn’t worth the effort to support. Just having one person on the team running Fx is usually enough to catch the game-breaking bugs.






  • toastal@lemmy.mltoAsklemmy@lemmy.mlThe Condiment Wars
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    4 days ago

    Actual barbecue sauce that isn’t a one-note, sweet sauce like I find in Asia but rather has tang, spiciness, & smokiness. I made some at home based on Gates sauce & gave some to locals who they were absolutely blown away that BBQ sauce can actually have a complex flavor flavor.

    #2 would be sawmill gravy, #3 sweet chili, #4 jim jaew, #5 salsa verde, #6 tahini

    Nowhere on my list & actually make me gag: ketchup, yellow mustard, brown sauce






  • I think the parent is distinguishing between messages & the attachments as they are stored differently & often in different places in many systems. But I agree with you in assuming that the goal would ultimately be to then start scanning messages too.

    Imagine governments used something like SHA1 that has conflicts & now you have collision potential–you could even fabricate attachments that could cause a collision to get someone throw in jail since all you have to rely on is the file hashes. If you can’t scan the actually content & you are just using hashes, then you also don’t prevent new content that those in power deem ‘bad’ from being flagged either which doesn’t really stop the proliferation of the ‘bad thing’ just specific known ‘bad things’. If I were implementing clients, I would start adding random bits to the metadata so the hashes always change.

    The only way this system even works is if there are centralized points the governments/corporations can control. Chalk this up as another point for supporting decentralization & lightweight self-hosting since it would be impossible to have oversight over such a system if anyone can spin up a personal server in their bedroom.




  • These have tradeoffs you don’t see when certain groups cannot participate due to personal or systemic political or philosophical reasons. You also can’t hear from that crowd since they haven’t been given a place to voice.

    In the case of chat & forges, these are solved for quality free options (& even decentralized in some cases). The choice are at least in the good enough category if not better in some aspects (& worse in others). For chat a room in Libera.Chat or OFTC is free & meant for free software—even if it is labeled as unofficial it still gives folks a sanctioned place who wish to avoid Discord for privacy, security, preformance, or US services being blocked (as well as being an out-of-band option for when a server is inevitably down). For forges, living in part of world where Microsoft often heavily throttles my bandwidth & all outages are during my day time, it is never a bad idea to configure your VCS to push to a second mirror like Codeberg, et al. not just for freedom reasons but resilience from server outages & censorship (see youtube-dl or the Switch emulators or nations that have blocked the whole IP due to something governments didn’t like in someone else’s repo). When you start coding around Microsoft GitHub’s Actions or API or Discussions or any specific integration without an eye to the generic/portable approach which is easier done from the start, dependence starts to add up. While readonly mirror would suck for freedom of contributions/communications, it is an option if it is seen as too noisy or too much of a burden to support multiple forges outages & censorship are real (especially if not in the West).

    “Enshitification” is the buzzword for services whose quality goes down & devolves to ads + selling user data for profit maximization—usually because they can because users/groups are now locked into the service having relied too heavily on their infrastructure. We see free software projects still stuck on Sourceforge & Slack due to lock-in. Having started with the free option, the lock-in probably can’t happen. Even having one option supported as a backup makes one cognisant of features that aren’t going to port when these US-based, profit-driven entities decide to gradually make things worse to the point where users want to leave with history showing us this has happened several times.

    You might say it is pragmatic, but I think it’s both lazy & short-sighted to not have these near-zero-effort options set up even as a back up (truly can be set & forget if really wanted)—especially when you think these values are good enough for the service you are building but also interacting on Lemmy, a decentralized, self-hostable platform (who said they have every intention of migrating their code to self-hosted as soon as ForgeFed is merge for federation).