sudneo

@sudneo@lemmy.world

This is a remote user, information on this page may be incomplete. View at Source ↗

⁨Comment⁩ on ⁨Lemmy.ml is acting as a proxy instance for Hexbear and should be defederated by any instances that defederate from Hexbear⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
You see, it’s not required for me to agree with whom you are criticizing, to criticize your inability to be civil. So keep making as many strawmen you like. We are in a post complaining about user behavior/content and your behavior and content are both completely unacceptable in a community.

Also, you can stop name-calling, this may have an effect when someone else values your opinion, I don’t.
⁨Comment⁩ on ⁨Lemmy.ml is acting as a proxy instance for Hexbear and should be defederated by any instances that defederate from Hexbear⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
Ok, but it’s the same thing from the perspective of all the people on an instance vs from the perspective of an individual. Those people are still there, creating posts etc., and they can easily move on other instances if they want too.

It’s just a “bigger blanket”, but the concept is essentially the same, with the plus that more people are “covered” and the minus that someone might be affected against their will.

Either way, it doesn’t solve the problem, it just masks it for the members of an instance. Why would it be a fundamentally better solution in this particular instance?
⁨Comment⁩ on ⁨Lemmy.ml is acting as a proxy instance for Hexbear and should be defederated by any instances that defederate from Hexbear⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
I had a look at your history, and you seem really incapable of behaving in a civil way, often using insults. I don’t think this is a good strategy to get your point across.
⁨Comment⁩ on ⁨Lemmy.ml is acting as a proxy instance for Hexbear and should be defederated by any instances that defederate from Hexbear⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

Be respectful of others.

This comment is in clear violation of the rules of this community. Be better, if you want to criticize others.
⁨Comment⁩ on ⁨Lemmy.ml is acting as a proxy instance for Hexbear and should be defederated by any instances that defederate from Hexbear⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

No, you’re putting a blanket over them and pretending they’re not there any more.

Isn’t defederation the same thing? Users won’t disappear (and they can also create accounts elsewhere…).
⁨Comment⁩ on ⁨Simple authentication for homelab?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
Thanks (grazie?)! I was looking for something similar and kanidm looks great feature wise and simple to deploy!
⁨Comment⁩ on ⁨My take on selfhosted photo management⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
I struggled with this for a long time, and then I just decided to use synology photos.

It has albums, tagging, geolocation, sharing. It has phone picture backup, it is inherently a backup as it’s on my NAS and I back that data up again.

I want to keep the thing that I really care about the most friction free and also not too dependent on myself so that I can still experiment.

I didn’t try PiGallery2 though, maybe I will have a look!
⁨Comment⁩ on ⁨Docker or podman?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
Did it sound cold? Because I didn’t mean that, I just meant to actually answer the question from my PoV. Just for the record, I also did not down vote you.

So yeah, use whatever footgun you prefer, I don’t judge :)
⁨Comment⁩ on ⁨Backblaze B2 vs other storage providers to store legally ripped media⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
Or rustic! It is compatible with restic but has some nice additions, for example the fact that supports a config files. It makes operations a bit easier IMHO (I am currently using both).
⁨Comment⁩ on ⁨Docker or podman?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
I really thought swarm was dead :)

To be honest, some kubernetes distributions make the cluster operations minimal (I use k0s managed via ansible)!

Either way, the moment you go from N containers on one box to N containers on M boxes you need to start considering how to handle stateful applications, load balancing, etc. And that in general requires knowledge on a domain which is different from having simply applications wrapped in containers locally.
⁨Comment⁩ on ⁨How to prioritize a container with regards to internet speed⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
Yeah ultimately every container has it’s own veth interface, so you can do shaping using tc on those.
⁨Comment⁩ on ⁨How to prioritize a container with regards to internet speed⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
Cgroups have the ability to limit TCP and total network bandwidth. I don’t know from the top of my mind whether this can be configured at runtime (I.e. via docker run), but you can specifcy at runtime the cgroup parent to use. This means you can pre-create the cgroup, set the limits and start the container with that parent cgroup.

You can also run some hook script after launch that adds the PID to a cgroup every time the container is launched, or possibly use tc.

I am not aware of the ability to only limit uplink bandwidth, but I have not researched this.
⁨Comment⁩ on ⁨Docker or podman?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
I think k8s is a different beast, that requires way more domain specific knowledge besides server/Linux basic administration. I do run it, but it’s an evolution of a need, specifically when you want to manage a fleet of machines running containers.
⁨Comment⁩ on ⁨Docker or podman?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
Because the lxc way is inherently different from the docker/podman way. It’s aimed at running full systems, rather than mono process containers. It has it’s use cases, but they are not as common IMHO.
⁨Comment⁩ on ⁨Docker or podman?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
I would say Docker. There is no substantial benefit in running podman, while docker is a widely adopted tool (which means more tooling in the ecosystem, easier to find answers to questions etc.). The difference is not huge tbh, and some time ago the biggest advantage for podman was being able to run rootless, while docker was stuck with a root daemon. This is not the case anymore (docker can run rootless), so I would say unless you have some specific argument to use podman, stick with docker.
⁨Comment⁩ on ⁨Bluesky’s Stackable Approach to Moderation⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
They have millions in funding, they will always move at a faster pace. The question is in which direction they will move, I suppose.
⁨Comment⁩ on ⁨Researchers jailbreak AI chatbots with ASCII art -- ArtPrompt bypasses safety measures to unlock malicious queries⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
Yes, an exploitative thing that mostly consists of free labour for big orgs.
⁨Comment⁩ on ⁨Lemmy's Image Problem⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
I am sure that for such small shops it’s trivial to explain that resources are extremely limited, I don’t see any data protection authority actually pursuing anyone based on the lack of privacy by design. The point is, nobody is forcing you to deploy the software as is, and technically anybody could write tools that bridge the gaps in the software. If the software does not offer data deletion, any instance admin could have identified this gap (a risk assessment for data collection is also needed technically) and wrote a script that would allow to satisfy data deletion requests or anything else that would have made them comply.

That said, I agree that these features are important. I do not agree that they are what the devs should work on right now, or that at least it takes some convincing to convey the fact that these are important features for instance admins to be compliant and for users (in general).

I also get the point about the “I am not taking your word for it” approach. Look how many people in this thread talk about GDPR without actually understanding who is the data controller/processor and who has to be compliant. I can only imagine the amount of uninformed people who open issues and waste time for already busy devs. We are seeing the couple of examples that the article picks, we are not seeing the rest of issues which justify this harsh approach.

The way I see it, having certain features implemented in the Lemmy software is one way to ease compliance for admins, and they should just upvote the issue and explain why it’s important for them, possibly even adding a bounty to the feature. OP’s approach doesn’t seem this and it’s much closer to demand stuff, as if the compliance responsibility was on the devs and the donation were some sort of reason to make them work on what other people want.
⁨Comment⁩ on ⁨Lemmy's Image Problem⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
To be precise, it’s not devs that need to worry about GDPR, it’s instance admins. I don’t disagree with you, but I think it’s an important distinction to make.
⁨Comment⁩ on ⁨Best way to dockerize a static website?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
If there is already another reverse proxy, doing this IMHO is worse than just running a container and adding one more rule in the proxy (if needed, with traefik it’s not for example). I also build all my servers with IaC and a repeatable setup, so installing stuff manually breaks the model (I want to be able to migrate server with minimal manual action, as I had to do it already twice…).

The job is simple either way, I would say it mostly depends on which ecosystem someone is buying into and what secondary requirements one has.
⁨Comment⁩ on ⁨Lemmy's Image Problem⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

That’s not the argument being made. What’s baffling is to pretty much only rely on the efforts of third party devs to fill in the missing gaps. It’s a profoundly bad strategy.

I literally quoted the article:

At this point, most of the solutions the ecosystem

I mean, there are some moderation features in Lemmy, for sure with gaps, but there are many gaps on other aspects as well, and if people can’t run the instances due to other technical issues, there is also nothing to moderate, so obviously prioritization is complex when resources available (dev) are so limited.

That said, I really don’t see the problem of third parties. We rely on third parties for one of the most fundamental features, which is community discovery (lemmyverse.net), for example. What’s the problem with that? I think that’s literally one of the benefits of making an open platform, where other people can build other tools in the ecosystem. We are not purchasing a service, we are not talking about an organization who has a substantial revenue and tons of people and can’t deal with basic functionalities. We are talking about a project with a team that is smaller than the team that in Facebook deals with which colors to make buttons, and it’s “paid” 1/20th of that. So I still don’t understand, what is “baffling”? Because from where I stand, all things considered, it’s totally normal that a project with these resources and that gained popularity less than a year ago has still tons of gaps and a long roadmap, and that tools in the ecosystem address some of these gaps.

It’s like with Bethesda releases a shitty half-finished game

No it’s not. Bethesda is company that sells you a proprietary product while having a revenue in the order of hundreds of millions. The relationship between Bethesda customers and Lemmy users has absolutely nothing in common.

Here, Lemmy makes some money

Lemmy makes no money. Considered the opportunity cost, Lemmy loses money. A single dev with a full time job can easily double the amount that Lemmy devS earn. Not to talk about the fact that the money they make are donations, without a contract bounding them to anything and also not granting them anything (tomorrow everyone could cancel donations and the income would disappear).

They can’t do that if the tooling is too brittle, shitty, or threadbare to actually handle the deeply fucking intense problem of managing and maintaining a server and community on the open Internet, where literally anything and everything goes. Factor in a myriad of local jurisdictions and laws about data and content, and a lot of these things end up becoming severe liabilities.

Sure, but again, if those were the only problems and the devs would be sipping cocktails in Hawaii splurging on those 4k/month, I would agree with you. If they think priorities are elsewhere, or are also elsewhere, they might have their reasons. In fact, in the article there is a complaint about them answering in a “hostile” manner, but I also understand that the issue in question is probably the 100th issue in a week/month in which other people tell them what they should do. This is a regular problem in OSS (See mastodon.uno/@bagder@mastodon.social - the maintainer of curl - for plenty of examples). After they understood better what’s the problem, their stance changed as well, which is also reasonable.

Look at it this way: with federation, a handful of volunteers themselves are doing labor for free, for the devs, by propping up their platform, client ecosystem, and reputation in the space. If this gets bad enough, people will literally say “fuck it” and walk away.

I don’t look at it in this way as well. I think the devs made it extremely clear (even given the political stance of both) that despite the happiness of seeing their project flourish, they have no interest in growth as an end. In fact, I would say that nobody is doing work for the devs. But I see that we have a fundamentally different perception on the dynamics in Lemmy, so I see no reconciliation between our opinions.
⁨Comment⁩ on ⁨Lemmy's Image Problem⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

The fact that Lemmy’s core team is taking a fairly laissez faire position on moderation, user safety, and tooling is problematic, and could be a serious blocker for communities currently hosted on Lemmy.

At this point, most of the solutions the ecosystem has relied on have been third-party tools, such as db0’s fantastic Fediseer and Fedi-Safety initiatives. While I’m sure many people are glad these tools exist, the fact that instances have to rely on third-party solutions is downright baffling.

Honestly, what? Why would be baffling to have third party tools in this ecosystem? It would be baffling if that was the case for Facebook. Also the devs did work on some moderation features, but they probably have tons of other stuff to work on, all for an amount of money which is a low salary for one developer.
⁨Comment⁩ on ⁨Best way to dockerize a static website?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
I would consider the lack of a shell a benefit in this scenario. You really don’t want the extra attack surface and tooling.

Considering you also manage the host, if you want to see what’s going on inside the container (which for such a simple image can be done once while building it the first time more likely), you can use unshare to spawn a bash process in the container namespaces (e.g., unshare -m -p […] -t PID bash, or something like this - I am going by memory).
⁨Comment⁩ on ⁨Best way to dockerize a static website?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
It really depends, if your setup is docker based (as OP’s seems to be), adding something outside is not a good solution. I am talking for example about traefik or caddy with docker plugin.

By versioning I meant that when you do a push to master, you can have a release which produces a new image. This makes it IMHO simpler than having just git and local files.

I really don’t see the complexity added, I do gain isolation (sure, static sites have tiny attack surfaces), easy portability (if I want to move machine it’s one command), neat organization (no local fs paths to manage essentially), and the overhead is a 3 lines Dockerfile and a couple of MB needed to duplicate a webserver binary. Of course it is a matter of preference, but I don’t see the cons honestly.
⁨Comment⁩ on ⁨Best way to dockerize a static website?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
Containers are a perfectly suitable use-case for serving static sites. You get isolation and versioning at the absolutely negligible cost of duplicating a binary (the webserver - which in case of the one I linked in my comment, it’s 5MB of space). Also, you get autostart of the server if you use compose, which is equivalent to what you would do with a Systemd unit, I suppose.

You can then use a reverse-proxy to simply route to the different containers.
⁨Comment⁩ on ⁨Best way to dockerize a static website?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
I personally package the files in a scratch or distroless image and use github.com/static-web-server/static-web-server, which is a rust server, quite tiny. This is very similar to nginx or httpd, but the static nature of the binary removes clutter, reduces attack surface (because you can use smaller images) and reduces the size of the image.
⁨Comment⁩ on ⁨The Fairphone 5 is less about what comes in the box and more about what you get over the years⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

Our starting point for design is longevity, which means making our devices more repairable, a very different approach to the electronics industry standard. To support maximum longevity and because of the IP rating, Fairphone 4 does not feature a headphone jack. In the end, it comes down to how we make a product that lasts for at least five years. We needed to eliminate as many vulnerabilities as possible, and the headphone jack is subject to dust and water ingress over time.

Again, you might disagree, you might know better, I don’t know. But this is their motivation when it comes to longevity and hence sustainability. To me, it seems a reasonable idea: if the jack helps reducing the consumption of batteries in headphones but decreases the lifespan of the phones, it seems a bad tradeoff.
⁨Comment⁩ on ⁨The Fairphone 5 is less about what comes in the box and more about what you get over the years⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:
They have literally an …fairphone.com/…/9836188988049-Audio-Jack-3-5mm for this on their website. You might disagree, but saying “it makes no sense”…makes no sense.

Also, they discontinued the earbuds and still no jack on FP5, so the idea that “they wanted to sell their own buds” doesn’t seem to be likely.
⁨Comment⁩ on ⁨Autostart Jellyfin flatpak⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:
Just a small note: docker can also run rootless for a while. The configuration is slightly convoluted, but can be done.
⁨Comment⁩ on ⁨Tear Down Walls, and Build Bridges⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

None of those are requirements to be part of the fediverse.

They are de-facto values of the fediverse today. It depends what you mean by “requirements”. Technically, you can join the fediverse in many ways, but the fediverse is not just a bunch of servers talking to each other, it’s also a community of people. This community rejects some members for different reasons.

there’s multiple companies invested in the fediverse: Mozilla, Flipboard, Facebook, Automatic being the most obvious.

But those companies are very different, aren’t they? Mozilla and Flipboard are participating within the fediverse, they are not plugging in their things, and their business models are not the same as Meta, and it is compatible with the values mentioned (well, Mozilla is a no-profit, in theory?). Wordpress is on the other hand very much aligned with the values of the fediverse. It is not the same as Meta and Bsky, both with the Silicon Valley DNA in them and all that it entails.

Truth Social, Gab, Spinster, etc are all on the fediverse despite being abhorrent to the majority of the rest of the fediverse.

And this is exactly where I disagree. Are they part of the fediverse? I wouldn’t say so. They are completely isolated islands, that happen to use protocols that are similar to those used from the fediverse (software). They are not part of the fediverse if by that we mean the set of communities that populate it at all.

I suppose this is where the root of our disagreement lies. For me the technical network that links tools is not the fediverse. The fediverse is what is built on top of that network and it is inherently linked with the community and their values, in other words, it’s a social subject. Personally, I can’t care less if tomorrow anybody starts using AP and can (technically) interoperate with Lemmy or Mastodon etc., I would definitely push for the rejection of - say - Facebook (like the literal facebook) or Reddit, or Twitter etc.