• 0 Posts
  • 37 Comments
Joined 2 years ago
cake
Cake day: July 5th, 2023

help-circle

  • If no one cares enough to reopen it once every 6 months, then it’s probably fine to ignore it indefinitely.

    It’s a matter of psychology. If I file a bug and it is ignored for years, I’m annoyed but eventually I either accept it, find a workaround or move on to something new. I may still file bugs in the future, especially if I’ve got a workaround, since other people probably want to know.

    However if my bug is closed and I have to reopen it every six months. Now I’m kinda pissed. I have to be reminded every six months for years that this is just broken. I put in the effort, but now some bot has just come along and closed it. Plus it’s going to be harder to find an existing or similar bug. I’m less likely to look at closed bugs. But also, what if I find four similar closer bugs. Now if someone was tracking that bug they don’t realize this has happened to four different users. If we had just kept it in one big we’d all know. Also someone elses workaround is better than mine, or maybe it’s worse.

    I understand if a project wants to declare bug bankruptcy. It shouldn’t happen often but if you do that’s the time to organize things.


  • The Pentaverate is solid. It’s no Austin Powers or Wayne’s World, but it’s solid. It was great to see Mike Meyers back in form, even if it wasn’t his best work, just really good.

    My hope is that he was just out of practice and he’s working on some great stuff behind the scenes. I know The Love Guru was a big miss for him and it really cut him down. He thought he’d created the next Austin Powers and it just fell flat. It wasn’t the worst film, but definitely a huge step down.

    Long way if saying if you’re a Mike Meyers can, the Pentaverate is probably worth your time.








  • Voyager for Lemmy is some seriously gourmet shit.

    But seriously the answer is usually that the big company is trying to apply to ALL USERS and usually only pleases a subset or none of those users.

    Voyager isn’t for you? That’s fine, Lemmy has a nice API and you can build whatever you like. Lemmy is also open so if that API isn’t nice you can provide suggestions and fixes.

    I’m not saying it’s perfect, but it’s a pretty good place to be.

    Look at early Twitter or formerly Reddit. A nice API. Tons of fantastic clients. Open source is the best, but even just “open” is a fantastic first step.


  • I wouldn’t classify every monolingual person as trapped in an echo chamber

    Simply being something isn’t an echo chamber, you have to have a thought or opinion being shared by the group. If every person you interact with only speaks one language, and they all share that one language is the best method of communication, that’s an echo chamber.

    Use social media how you like

    I agree. Although it is useful to be aware of your own biases.

    the solution to echo chambers is going outside and touching grass not forcing yourself to interact with every community on the internet.

    Assuming you don’t mean literally “touch grass”, the solution is seeking out opinions/thoughts outside of your echo chamber. That doesn’t necessarily mean forcing yourself to interact with terrible communities, but being aware and understanding (but not agreeing with) them.

    Although I again refer to using social media how you like is fine. No one needs to be exposed to certain communities. It’s not wrong or lazy or bad to ignore certain communities or viewpoints, especially toxic ones. However you should be aware that they exist and it can be helpful, if you choose, to understand where they come from.

    As a harmless example, if you don’t like brussel sprouts and none of your friends like brussel sprouts, it may benefit you to try brussel sprouts or to seek out and talk to or read about people who like brussel sprouts. You can still at the end of the day dislike brussel sprouts. You don’t have to change your opinion. But now your opinion is more well rounded.




  • So first off I appreciate your “about:config” dump, that is helpful.

    However, having ONLY that dump makes it difficult to actually diagnose your issue. It would be helpful to have an idea of what fails.

    • Are you only unable to join meetings?
    • Can you create meetings?
    • Only audio?
    • Only video?
    • Are there any error messages?
    • Are there any messages at all on screen?
    • Are there errors in the JavaScript console?
    • If there are a lot, can you compare it against the working vanilla version and see where the errors are unique/start to differ?
    • When did this issue start to happen? (It worked a week ago, but not now?)
    • Is your config based off a guide online?

    Second, you have “media.peerconnection.enabled” set to “false”. That setting controls WebRTC. Google Meet uses WebRTC. If I set that value to false my Google Meet meetings fail to load, it just stays stuck at the joining meeting phase.

    So maybe that’s your culprit. Of course I would expect if you’ve had this set for a long time I would have expected it to fail for a long time. Also both alternatives you mentioned use WebRTC, so I would expect those to fail with that setting disabled.

    Of course if it used to work with that disabled then it’s possible Google Meet changed and had a fallback no longer in use or something else.

    As an aside, I understand that WebRTC has (had?) issues leaking local IP addresses while connected to a VPN. So I understand why you might have it disabled.


  • in my hardened config firefox browser

    The only conclusion I can draw is that google is so desperate for my data that they refuse to service me unless I give them this.

    What is your config? It’s possible you’ve got things configured in an unexpected, but valid, way that causes Google Meet to fail.

    How does it fail? Are there errors in the console?

    You’re immediately assuming malice, but it may simply be a mistake (Google’s or yours).