Just a lvl 27 guy from 🇫🇮 Finland. Full-stack web developer and Scrum Master by trade, but more into server-side programming, networking, and sysadmin stuff.

During the summer, I love trekking, camping, and going on long hiking adventures. Also somewhat of an avgeek and a huge Lego fanatic.

  • 0 Posts
  • 16 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle
  • Compare your actions to releasing a 0-day exploit for a security vulnerability instead of responsibly disclosing. It doesn’t help, it just causes chaos until the people who do the actual work can figure out a solution.

    This comparison is not fair at all. It’s not like the devs are unaware of this. They could start by removing the API endpoint that lists a post’s votes, but they haven’t, which means they seem to think it’s okay for the instance admins to snoop on votes if they so wish.


  • They can include runnable JavaScript too, which can cause vulnerabilities in certain contexts. One example from work some years back: We had a web app where users could upload files, and certain users could view files uploaded by others. They had the option to download the file or, if it was a file type that the browser could display (like an image or a PDF), the site would display it directly on the page.

    To prevent any XSS (scripts from user-provided files), we served all files with the CSP sandbox header, which prevents any scripts from running. However, at the time, that header broke some features of the video player on certain browsers (I think in Safari, at least), so we had to serve some file types without the header. Mistakenly, we also included image files in the exclusion, as everyone through image files couldn’t contain scripts. But the MIME type for SVG files is image/svg+xml… It was very embarrassing to have such a simple XSS vuln flagged in a security audit.


  • I never understood why exactly it’s such a controversial topic. It’s my third year on Mastodon, and I’ve never felt the service was lacking just because not having proper quote posts. But then, I also don’t understand most of the arguments against them, especially when/if they’re implemented as an opt-in for the original poster.

    Basically, people on both sides seem angry over nothing, and I’m just like, ‘Neat, a new feature. Anyway…’


  • You will be able to choose whether your posts can be quoted at all.
    You will be notified when someone quotes you.
    You will be able to withdraw your post from the quoted context at any time.

    To me this sounds like the right way of doing it. Quote posts have always been kinda a hot topic on Mastodon. Some people want them while others absolutely do not. So best just let everyone to decide for themselves.






  • Cool, thanks for the explanation.

    a single application that gets bundled with all necessary dependencies including versioning

    Does that mean that if I were to install Application A and Application B that both have dependency to package C version 1.2.3 I then would have package C (and all of its possible sub dependencies) twice on my disk? I don’t know how much external dependencies applications on Linux usually have but doesn’t that have the potential to waste huge amounts of disk space?