Domi @ domi @lemmy.secnd.me

Posts

1

Comments

388

Joined

2 yr. ago

Stop recommending questionable open-source like Matrix.

Synapse and Element are fully open source, there is nothing questionable about it. Having a company backing your project as main developer does not mean it suddenly becomes closed source or said company owns the project now.

None of the issues you mentioned are a big deal or make Matrix inherently worse than XMPP. The biggest flaw you can pin on Matrix is its performance but they're working on it.

CoreELEC is community maintained and the N2+ still receives the latest builds, my last update was just last month.

However, CoreELEC can be installed on many devices (including some Android TV boxes) that have Amlogic chips. You can see a full list if you to to the download page on the CoreELEC page https://coreelec.org/.

Also, CoreELEC is not Android, it is Linux running only Kodi. If you need anything besides Kodi you might want to look at another solution or have multiple devices.

Kodi still plays via SMB/NFS when configured in direct play mode. Only the metadata is provided via Jellyfin and play progress is synced to Jellyfin.

The Jellyfin plugin is not the most stable piece of software but it gets the job done.

I have been using an Odroid N2+ with CoreELEC installed and the Jellyfin Kodi plugin for years now.

Plays pretty much everything you throw at it, including 4k HDR HFR.

Dolby Vision is supported in CoreELEC but only on some devices.

because the rain sensor doesn't seem to do jack shit in a Tesla

That's because they saved 70 cents and don't have rain sensors, they use "AI" image recognition to detect rain and snow.

It works as well as it sounds.

As another mouse lover, the DualSense controller also has gyro aiming and I can only recommend it.

I'm playing Horizon Forbidden West with it right now and it allows me to be almost as precise as with a mouse. The adaptive triggers and the detailed haptics are also pretty cool. Also a really good controller for Switch emulation.

Pretty easy to do if you use Pipewire, just add a file named ~/.config/pipewire/pipewire.conf.d/10-virtual.conf with the following content:

    
context.objects = [
    {   factory = adapter
        args = {
            factory.name     = support.null-audio-sink
            node.name        = "Virtual-Sink-1"
            node.description = "Virtual Sink 1"
            media.class      = "Audio/Sink"
            audio.position   = "FL,FR"
        }
    }

    {   factory = adapter
        args = {
            factory.name     = support.null-audio-sink
            node.name        = "Virtual-Sink-2"
            node.description = "Virtual Sink 2"
            media.class      = "Audio/Sink"
            audio.position   = "FL,FR"
        }
    }
]

  

This will add 2 virtual sinks to your device list after a restart, which you can use in all applications.

After that you can install qpwgraph and add it to autostart: https://flathub.org/apps/org.rncbc.qpwgraph

Now you can drag & drop all connections from your Virtual sinks to you output device (as shown in the image I posted). You can even send it to multiple output devices at the same time.

When you are done hit Ctrl + S to save your patchbay and select Patchbay -> Activated. Now qpwgraph will load your connections every time it starts.

Made the same journey over the years. Rocking a OPNsense DEC740 now and everything works well.

When recording in OBS, I can split the voice and desktop audio and edit them separately.

On my desktop I use 2 virtual audio devices that are linked to my real audio card with qpwgraph in order to split audio between VoIP applications and desktop/game audio.

I have used it for almost 3 years, no serious issues here.

Not sure, probably somewhere around when the new Wayland backend was introduced: https://github.com/ValveSoftware/gamescope/commit/9563271dea5ee4844b16a7e179e9f6bc7ed51168

I also normally run in Flatpak but I switched to native until everything settles in. Turns out the config files are compatible now so you can run either and they will pick up the others config with no issue. Just have to watch out with shader pre-compilation because if you have different Mesa versions the clients will pre-compile back and forth all the time.

Does the game have anything going for it at all?

Played it during the beta and it's not like it's an inherently bad game, but Left 4 Dead did it all better and 10 years before.

It's on sale for 5 bucks all the time but even for that price I never had the desire to play if over Left 4 Dead.

Isn't anyone excited?

The excited people are playing the game right now instead of shit posting on Lemmy. :D

Yes, and I did not downvote you for giving context.

Outside of any ridiculous internet drama, what does this have to do with Horizon?

According to their wikipedia page they are not involved with this game at all.

https://en.m.wikipedia.org/wiki/Sweet_Baby_Inc.

Is that a real Deezloader website? That website looks shady af.

I don't run Pi-hole but quickly peeking into the container (docker run -it --rm --entrypoint /bin/sh pihole/pihole:latest) the folder and files belong to root with the permissions being 755 for the folder and 644 for the files.

chmod 700 most likely killed Pi-hole because a service that is not running as root will be accessing those config files and you removed their read access.

Also, I'm with the guys above. Never chmod 777 anything, period. In 99.9% of cases there's a better way.

Flathub is actually fairly strict with its submissions, probably too much work for most fake submissions to follow the PR guidelines.

https://docs.flathub.org/docs/for-app-authors/requirements

https://github.com/flathub/flathub/pulls?page=2&q=is%3Apr+is%3Aclosed

Same :)

I also get unreasonably annoyed when an application replaces my ASCII emoticons with emojis.