Well I didn’t want to have a bio, but Lemmy doesn’t let me null it out, so I guess I’ll figure out something to put here later.

  • 0 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle
  • To be clear, you’re not going to find many displays that can reach 4,000 nits yet. A lot of HDR content actually is mastered for 1,000 nits and that’s considered kind of the target for the mid-high range OLEDs right now. My pretty much top of the line QD-OLED Samsung S95C maxes out at something like 1350 nits. A 1000 nit capable Steam Deck OLED has plenty of range in luminance for HDR to be effective there. And I’m sure it’s got pretty good color reproduction which is the other big aspect of HDR.

    One thing we haven’t talked about is the possibility that the Steam Deck is enhancing SDR content with dynamic tone mapping to such a degree that it’s difficult to tell the difference when you actually enable true HDR. I’d really have to see this with my own eyes to be able to say with more certainty what’s going on.



  • What you’re describing is only possible on de-anonymized platforms that essentially have “know your customer” type policies where users have to provide some kind of proof of their identity. While I agree that there is value in social spaces where everyone generally knows the people they’re interacting with are who they say they are, I don’t think this is ever going to be feasible in a federated social platform. I think Facebook is the closest thing we have to what you’re describing, to be honest, and I believe Meta has even kicked around having a more sandboxed Instagram for minors (though I don’t use Instagram, so I’m not certain on the details there).

    For me, in most cases on a platform like Lemmy, a person’s age is not something I care about. I care about what people are sharing and saying. But then again, none of my interests for online discussion at this point in my life are really age centric. I think there are clearly better platforms than Lemmy if people want to guarantee they’re only interacting within their age specific peer groups.


  • Personally, I think it’d be nice if you could self-host just the bridge instances and connect them with beeper yourself, so that the part that isn’t e2e encrypted is running on software you can validate and hardware you control.

    I 100% agree this would be a great solution. That’s what I thought this page was going to be at first until I kept reading and realized it’s just a config guide for the Matrix Ansible setup. I wish they didn’t say “self host Beeper” on that page at all because self hosting Matrix has absolutely nothing to do with the Beeper service other than their devs built the bridges that they’re showing you how to set up with Matrix.





  • E2EE only exists up to the bridge, not the whole way to your client

    I just want to clarify that most bridges can be set up to have E2EE between the Matrix client and the bridge (regardless of whether the bridge supports encrypted chats on the bridged service because not all do, e.g. Facebook), but it is true that the bridge itself has to decrypt and translate between Matrix and the 3rd party chat service, so as you mentioned trusting who hosts bridges or doing it yourself is really important.


  • You can run headless or do what the person I was responding to recommended and put it behind an authenticated portal, but that’s not really going to stop other instances and clients from accessing the same resources that op is hoping to limit access to except in the most basic case of people casually browsing op’s Lemmy instance through op’s own lemmy-ui.

    Edit, but to be clear, what I was responding to and my response didn’t directly address op’s specific concern (which I kind of misunderstood myself before just now rereading) that outside/guest users shouldn’t be able to search for communities from other instances and I think it’s a fair concern because just searching for a community from another instance brings in posts and could be a vector for spam/abuse.


  • Wouldn’t this do basically nothing to prevent a 3rd party client from browsing your instance without authentication? I don’t know that there’s much that can really be done about this because you need open APIs for other instances to be able to access the content of your instance in order to make federation possible. That said, it’s an important consideration that anybody running a single person instance should consider. If you run a single person instance, people can learn a lot about you just by seeing which communities are available on your instance. The only way to obfuscate your actual interests is to have a dummy account subscribe to all the top communities on the biggest instances. (Which, honestly, this isn’t a bad strategy to employ anyway if you’re wanting a fresh All feed).





  • They take a fair amount of getting used to, especially if you get an ortholinear variety. You might find yourself not really enjoying it out the gate, but it’ll force you into better typing posture and you’ll grow to love it over time and hate the times you have to type on a standard keyboard. I have an Ergodox and the ortholinear aspect took a while to get used to and settling into a function keys layout I liked took another good while. Expect to be worse at typing and less productive at the outset. Your hands and wrists will thank you in the long run, though.



  • The goal of Bluesky is to turn social media into a shared public commons.

    I agree with most of their blog post and it sounds like they’re taking a very measured approach to building out federation, but I really want everyone to stop trying to insist social networks be “public commons”. Moderation tools that do anything more than the bare minimum of blocking forms of speech that are not protected free speech by definition transform the social network into a place that’s not a public commons. Being able to block individuals, communities, topics (via keywords and hashtags), and entire federated servers makes it so that if you really want, you never have to see viewpoints you strongly disagree with. The same is not guaranteed in real public commons. Every day you walk down the street, you have the potential to be confronted with ideas you never considered and your only recourse is to engage, drown out, try to ignore, or walk away from those people, which is not analogous to blocking and thereby deplatforming them online.

    That said, I do not want my social network to be a public commons (and from what they’re describing, it doesn’t sound like Bluesky actually does either). Online, I want to be able to block and deplatform e.g. Nazis and MAGA trolls pre-emptively and with extreme prejudice because I want to enjoy my time on social networking sites, not raise my blood pressure.


  • I know I’m late to the game commenting in here, but I think it’s important to distinguish whether we’re talking about people merely adding descriptors to their NSFW posts or whether we’re talking about a whole tagging system being implemented into the Lemmy protocol. Adding a full fledged tagging system to Lemmy similar to Mastodon would be a pretty big undertaking. But anything short of that would feel like a kludgey, bolted-on solution. The NSFW flag + user added descriptors is the only way for users to go about it for now.

    I do think a conversation about adding tags into Lemmy is worthwhile because tags could potentially allow for a lot of neat things. E.g. we might eventually be able to start making custom feeds by aggregating content from multiple similar communities across instances. It would also let users filter tags they don’t want to see at all (regardless of whether it’s NSFW) or don’t want to see by default (i.e. blur the images until they’re selected). But I know the Lemmy devs probably don’t want it to end up looking like a Reddit/Mastodon hybrid or just become kbin, so this is something they’ll consider carefully. I think right now they’re rightly focused on database and federation performance and the broader dev community is helping with more immediate needs like spam account mitigation. They’ve gotta stop the bleeding and get a solid foundation established before building major changes like a full fledged tagging system.


  • You’re probably going to have a bad time in the Fediverse if you’re hoping to avoid viewpoints you don’t agree with entirely. The best advice I can give you for now is to just block that community and move on with your life. As much as I hate TD and its members, the sh.itjust.works admin has the right to administer their instance however they want. If they end up with a sufficiently toxic total userbase where their users are causing problems on other instances to the point they are a net negative, they will end up being defederated by other more reasonable instances. Beehaw is being pretty aggressive with defederation for things like this, so if you’re looking for the safest of spaces in the Lemmyverse they really might be more your speed. Or you can start your own personal instance and defederate whoever you want 🤷