chaospatterns @ chaospatterns @lemmy.world

Posts

25

Comments

153

Joined

2 yr. ago

I'm on Wayland and KDE/Plasma. It worked on GNOME, but sadly not on Plasma.

Not all filtering is the same. Client side filtering requires more data to passed over the network that then just gets dropped. It also means rules that are not shared across devices.

Most importantly, these use CSS filters which are computationally more expensive because it has to take an entire DOM element, serialize it to text, string search it vs a server side filter that can just look at a one or two field variables. Even if it's not filtered in SQL on Lemmy's side I'd say it's still more efficient overall.

You do what you want, but adding extra work on the client side is not what I'd want for my users. Of course, if your Lemmy instance does not supporting filtering, then this is moot.

And it'll be faster and more efficient to do it server side as opposed to making uBlock Origin handle it.

How many users are using browsers that are old enough they don't even support JS? It's one thing to disable it for security/privacy (which the OP was talking about), because those users are probably more tech savy.

Do these old browsers not support DuckDuckGo?

I tried self hosting Pixelfed but gave up because it wouldn't work. I'm used to Docker containers that are able to just start up by themselves, but the guide didn't work for me. Maybe it's time to try again.

One place it would be useful is if you are worried about somebody breaking into your home and stealing your computer. Don't store the key on the home computer, instead store it on a cloud server. The home computer connects to the cloud server, authenticates itself with some secret, then if the cloud server authorizes, it can return the decryption key.

Then if your computer gets stolen or seized, it'll connect via a different IP and the cloud server can deny access or even wipe the encryption key.

this doesn't protect against all risks, but it has its uses.

Example: https://www.ogselfhosting.com/index.php/2023/12/25/tang-clevis-for-a-luks-encrypted-debian-server

Unfortunately, unscrupulous companies can build shadow profiles that bypass cookie and storage based isolation techniques like this.

Your browser gives off a lot of information. See here for some of the information they can use: https://amiunique.org/

You're best off blocking things with uBlock Origin vs something that just isolates.

This is a good idea. It's a lot easier to incentivize a maintainer who is already familiar with a project and invested in it with some money than it is to get a person who is unfamiliar with a project.

How much you should donate and how likely they are to agree depends on how complex your request is, whether they feel it fits in with the project for other people, and how busy they are.

No, the cable isn't going to implement the protocol. You need endpoints that are able to talk that protocol. That might be done with a firmware update or require new hardware.

I just saw this one mention endurain, a fitness tracker. I've been looking for something to self host data about my health, fitness, etc. Has anyone tried this or anything else in the self-hosted or open source fitness space?

Those countries are Belarus, Bolivia, Indonesia, Kazakhstan, Cuba, Malaysia, Thailand, Uganda, and Uzbekistan.

I think I ignored a lot of signs and indications under the feeling that well "I'm promo tracked to the next level and I worked hard so I'll ignore it." My partner told me to talk to somebody, friends said I worked hard. But then slowly my motivation to work at my job decreased. I delivered less, I made up excuses, I stop caring about projects when I used to really care. Which was a huge difference because I used to be a top tier developer every year.

But the big part was my personal life. After work I was tired and not motivated, even though I would barely do any work. loosing interest in hobbies was a big indication. Going to the gym, but not really pushing myself, etc. I think there's some parallels with depression, but I never felt like I had that because I kept getting out of bed doing things.

I had a friend deacribe their experience and I just started thinking yeah I feel the same way. I finally had a health issue/mental breakdown that caused me to go to the doctor and pursue FMLA leave which is giving me partial pay to just focus on myself, focus on friends, and talk to a therapist. I don't know what I'll do when it ends. Probably won't go back to the company.

Weirdly, a lot of my friends in the big tech industry have hit a breaking point and are leaving or on leaves.

I'm recovering from burnout after working at a big tech company for 10 years. I think this article tries to focus on how just giving people the right work will prevent burnout, but I think the causes are very complex and vary for different people. But it's important to catch it before it's bad. For me, I had difficult to please managers, or projects that went nowhere, or passion projects that were not invested in, or lack of strong non-work relationships, or even just looking at the company I worked at slowly lose all culture and turn into something that started to abuse customers and focus on profits.

Monthly active users. A metric to show the number of users who are considered active at least once per month.

The spec mandating its as a single string isn't that crazy. It's good to have a consistent response format so a basic deserializer can deserialize any error response object and get something out.

If you have different providers. One that returns error: { code: string } and another does something else, you end up with the same problem this post talks about-- Inconsistency.

As far as I can tell, the spec doesn't limit you to just the one field and you can add other optional fields to the top level to the response that the caller can optionally decide to handle. But if you know there's going to be a field called error that is a string. You always get at least something out of that to present.

It just goes to show the small parts of API design matter just as much as the big parts. I've worked with a lot of engineers who are so eager to draw big boxes and arrow architectural diagrams, but then just rush the details because that's not important.

The hard part is browsers. Cookies and local storage are limited by the origin URL. You need it explicitly set on the domains you intend to visit, but those domains don't know your age. The one that knows the age is the identity provider, but it can't set it for all domains. There are other techniques that you could use, like a smart card combined with a browser extension to do local based user info attestation, but those are difficult to manage at a nation scale and I suspect people will struggle with them, though there are some countries that do have national smart cards (e.g. Estonia.)

Its possible to implement something that hides your actual age from a website, but the tricky part is hiding what website you're visiting from an identity provider.

Let's walk through a wrong solution to get some fundamentals. If you're familiar with SSO login, a website makes a request token to login the user and makes claims (these request pieces of user information.) One could simply request "is the user older than 18?" And that hides the actual age and user identity.

The problem is how do you hide what website you're going to from the identity provider? In most SSO style logins, you need to know the web page to redirect back to the original site. Thus leaking information about websites you probably don't want to share.

The problem with proposals that focus on the crypto is that they actually have to be implemented using today's browser and HTTP standards to get people to use them.

True, but even if there's only one supplier, there's still demand-side elasticity of price, which means that price increasing causes some customers to not buy the product. Thus, a company may or may not be able to increase a price 1:1 with the tarriff.

All this is fun economic theory, but I was specifically responding to the claim that tax incentives were better than a tarriff. They both translate into some increase in cost of the goods sold.