• 0 Posts
  • 102 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle

  • It seems that we focus our interest in two different parts of the problem.

    Finding the most optimal way to classify which images are best compressed in bulk is an interesting problem in itself. In this particular problem the person asking it had already picked out similar images by hand and they can be identified by their timestamp for optimizing a comparison of similarity. What I wanted to find out was how well the similar images can be compressed with various methods and codecs with minimal loss of quality. My goal was not to use it as a method to classify the images. It was simply to examine how well the compression stage would work with various methods.



  • I was not talking about classification. What I was talking about was a simple probe at how well a collage of similar images compares in compressed size to the images individually. The hypothesis is that a compression codec would compress images with similar colordistribution in a spritesheet better than if it encode each image individually. I don’t know, the savings might be neglible, but I’d assume that there was something to gain at least for some compression codecs. I doubt doing deduplication post compression has much to gain.

    I think you’re overthinking the classification task. These images are very similar and I think comparing the color distribution would be adequate. It would of course be interesting to compare the different methods :)






  • One of the most controversial changes of Chrome’s MV3 approach is the removal of blocking WebRequest, which provides a level of power and flexibility that is critical to enabling advanced privacy and content blocking features. Unfortunately, that power has also been used to harm users in a variety of ways. Chrome’s solution in MV3 was to define a more narrowly scoped API (declarativeNetRequest) as a replacement. However, this will limit the capabilities of certain types of privacy extensions without adequate replacement.

    Mozilla will maintain support for blocking WebRequest in MV3. To maximize compatibility with other browsers, we will also ship support for declarativeNetRequest. We will continue to work with content blockers and other key consumers of this API to identify current and future alternatives where appropriate. Content blocking is one of the most important use cases for extensions, and we are committed to ensuring that Firefox users have access to the best privacy tools available.

    https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-firefox-recap-next-steps/








  • You’re in trouble already as a business, wasting a lot of money, if you don’t know where your target audience is. What you argue is that this is used for a business to probe where an advertisement would work. I’d argue that that is a very expensive way of finding your target audience, because you still have to pay for all the ads that didn’t work. There are much better ways of figuring out where your target audience is.

    I think most people believe that this obsessive data collection is neccessary, only because Google has repeatedly painted that narrative. This better advertising is just coincidentally the form of advertising that Google is in the best position to supply.

    If you carefully pick the places you advertise and do statistics on how it affect your business while a campaign runs I’m willing to bet you get a much better return. As a bonus to saving money you didn’t have to shit on an important principle in democracy, the autonomy of the people, protected by something called privacy.