• 0 Posts
  • 295 Comments
Joined 5 years ago
cake
Cake day: January 21st, 2021

help-circle






  • kevincox@lemmy.mltocats@lemmy.worldTalking to your cat
    link
    fedilink
    arrow-up
    5
    arrow-down
    8
    ·
    4 months ago

    No, this is the right meaning royal we. If you say “we are going into battle” it is talking about the person being talked to not the person talking. So in this case “We don’t eat that” would be implying that the cat doesn’t eat that, not actually saying anything about the speaker even though “we” would imply they are included.


  • kevincox@lemmy.mltoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    80
    arrow-down
    2
    ·
    6 months ago

    I hear what you are saying. But our society is pretty fucked up if you “deserve” something bad because you bought a product without imaging how the manufacturer can make it worse in the future.

    The owners should be able to return the product if something like this happens, no matter how long ago they bought it.


  • Yeah, it is very important to consider how dependant you are on third parties. At the very least the more dependence the more power they have over you. But also how screwed you are if they just go under.

    • If you use SaaS they can interrupt your use at any time and you can only react (for example demanding a reversal or lawsuits).
    • If you host closed source software they can’t interrupt service on an existing contract but can legally require you to stop using it if they don’t renew the contract. (And if the company goes under you can likely get away with using the software as long as it doesn’t need code fixes.)
    • If the software is open source you can continue using the software indefinitely including making code fixes. (Maintenance may be expensive as it is now your problem but that can be costed and an exit plan made if required.)


  • Yeah, I finally pulled the trigger and moved to my own domain from matrix.org. Man, it is just so much faster. Which is sad, because the performance is pretty bad. (Element Web seems to do some per-room request as part of the initial loading screen which is obviously not scalable) but getting off of matrix.org is a huge performance improvement.

    That being said there is nothing really wrong with matrix.org. The problem is really public rooms. People will join and spam. It is true of any protocol (have you heard about email?) but Matrix definitely needs to (and they are slowly working on) make it more expensive for spammers.


  • /favicon.ico is the only “default” URL. /favicon.ico is usually not an actual “icon” type anymore but PNG or JPG (but with the same URL). Other than that you need to load the HTML and check for Link headers or <link rel=icon> elements. While URLs like /favicon.png may be popular they aren’t part of any actual protocol.


  • Sort of…

    You can just hope that /favicon.ico works. But 1. it often doesn’t and 2. it is often of low quality.

    To find a favicon on a modern site you need to load the HTML and check Link headers and <link rel=icon> elements. However you likely can’t do this client-side for most sites because of CORS. So you need some server (at the very least to strip CORS). That lets you get the URL but 1. you probably don’t want to have connections to external domains for user privacy and 2. some domains will have hot-link protection so you need to fetch the image via your server. You will also want to consider different image formats and sizes to serve the right image to the right client. On top of all of this the site may be using some sort of bot protection which you will have to fight. Google is almost always whitelisted. The site may also have temporary outages so having a cache would be nice, especially if that is almost always populated before you even know the domain exists.

    At the end of the day you do want some sort of API. And while it isn’t complex it isn’t trivial. So it is nice to just let Google handle it. (Other than tracking risks, but you could proxy Google’s API.)


  • Off topic. But I can’t help but rate the trash cans.

    • 1995: Excellent can. Obviously not that many pixels to work with but it is clear, legible and clean.
    • 1998: I mean its fine, but a bit of a downgrade. Why so much black? Especially that top rim that apparently was painted black. The shading on the arrows also just hurts legibility, why do 2D arrows have shading anyways?
    • 2000: Nope. The only good thing about it is that it is throwing away Windows. The shading is to simple arrows are strange colours and lacks a sense of depth.
    • 2001: I don’t love the theme but the execution is great. It looks clean shiny and bright. The only real weird thing is the bag inside, it is a bit strangely round despite seemingly not going over the edge.
    • 2006: This is a nice refinement of the last one. Cleaner look, skip the bag, more realistic trash. This is the second best executed after 1995.
    • 2015: This one is bland and lacks contrast and detail. The arrows are also oddly stubby for some reason. It’s not bad, but also not good.