elvith @ elvith @feddit.de

Posts

4

Comments

250

Joined

2 yr. ago

There's a nice presentation that explains this behaviour quite understandable: https://youtu.be/sRWE5tnaxlI

I’m not sure what to think of this article. I had to read for several paragraphs to get to know, that the problem is neither selling any user data collected by the browser (e.g. text inputs), nor is it the fact that they’re a search engine. It just that they offer an API for search which not only lists the same data as on the website, but offers a longer excerpt/text snippet for each result as it is seen on other search engines for some featured results. Depending on which UI you might want to develop for the results, that’s basically a nice feature as your app can decide which snippets get shown.

And now the problem seems to be that they offer a paid API and these results are a part of it? From data that was crawled by them by (as they’re saying) respecting robots.txt and - in most cases - was public anyways?

I don't know what I did wrong, but the bug must be somewhere in HelloWorldExampleClassForTutorialBuilderFactory.HelloWorldExampleClassForTutorialBuilderFactory(StringBuilderFactory myHelloWorldExampleClassForTutorialStringBuilder, int numberOfTimesToDisplayHelloWorld)

I rarely use shodan, so I'd probably never pay for a subscription. Especially since I've never really hit any limit in the free plan. But I got the lifetime membership two years ago for $0.99. Even for the current $5 that's a no brainer.

Maybe it's a bug with vger, maybe a cache/Chrome thing but it might also be a config issue.

When a web app wants to be installable, it needs to serve a file that tells the browser some things about itself - the manifest. If you visit your own instance on your server and take a look at the HTML source code in the browser (or use the dev tools), you should see a line like this:

        <link rel="manifest" href="/manifest.json">


  

This tell the browser where to find the manifest. If you open said file, it should contain a line with the start link that gets invoked when you start the PWA. In this file, you should see a line like this with the link:

          "start_url": "/?source=pwa",


  

Make sure that this link points to your installation and not to vger.app

As I don't host vger myself, I don't know if and how you can change the values there or what should be the correct link, but this might get you started to track down the error.

As far as I know, no one tried to clone TikTok for the fediverse. But I think the inherent problem is the algorithm. TikTok isn't like Youtube or any other social network, where you follow people. You have an algorithm that tracks everything you do and watch and then suggests you video based on their topics, less on the people in them. I guess it'd be hard to implement, as many in the fediverse are not keen about tracking.

You loose time? You dont know what you did that made all that time pass? Have you considered investing in a CO detector?

Reddit: „sigh, it’s another one of those ‚look at a top post from the distant past from a community you haven’t visited in ages’l

Bottom right corner

Yes, unless Jen needs to borrow it for a presentation.

Yeah, that's a bit of a problem in general. But in this case we're talking about Meta. It's one thing, if $randomCompany from outside the EU does it. As long as they're not doing business within the EU and not specifically target the EU as a market, then they might try to get the company and fine them and may or may not succeed.

Meta on the other hand provides service explicitly for EU citizens & companies. Not only did they localize Facebook, Instagram,... for European languages, they offer the service to sell ads for European companies. In this case, the EU can and will have a way to get them fined, I they want.

Fun fact - GDPR is about European persons, not European servers. If an European citizen has a fediverse account on an American/African/Asian/… server and Meta collects all of their data and processes it, they are still in violation of GDPR. Locking European (Instagram) accounts out of Threads doesn’t make them comply magically with GDPR.

Good luck meta, have fun handling all those GDPR requests and proving that Europeans have consented that you suck up all their data…