unbolted3032

Is anybody aware of any ad-block lists (for Pi-Hole or Adguard) that block all of Google's IP addresses? And Meta while I'm at it?

I bought two (identical) of these keyboards and they're by far the worst keyboard I've ever purchased. OOB, both had Bluetooth stability issues, dropping out at least 1-2 times a day, resulting in a sustained keypress being interpreted by the OS while they reconnectedddddddddddddddddddddddddddddddddddddddddddddddddddddd.

Vendor support suggested upgrading the firmware (I was on the latest firmware) so I followed their instruction - which nuked the keyboard's ability to use Bluetooth at all. No refund or replacement offered by vendor after reporting this.

I still use the non-broken one, exclusively in wired mode, and EVERY single time I use it, I have to perform the factory reset (Fn + z + j) in order to get the lights to work. Otherwise, cycling through the presets simply dims them until they're not visible.

I'm yet to find anybody with the same problems as me.

The thing that gets me is that to even use a Passkey I need a browser addon that syncs my entire password vault into browser memory, the same memory that all the adtech JS runs! No thank you! What a ridiculous system. I will continue copying and pasting passwords myself out of KeePassXC.

I deleted Meta's products in 2009. I have never looked back. Explore alternatives and motivate others to do so.

This may be a matter of taste, because I quite like the approach the ekte team have taken.

To my eye, the app is clean and minimal and shows me everything I need easily.

I've had success marking any URL with /shorts/ in it as read. I use FreshRSS and its URL matching is pretty reliable.

I'm being forced to implement it at my job.

The hype is real. The repository says 5k+ issues and 5k+ prs. There's no way any human being knows what's going on in the codebase. How people trust this to hit their APIs and hang onto their API keys is beyond me.

This is yet another straw on the camel's back; I'm building my industry exit strategy because of AI.

I decommissioned my server 3 months ago and migrated my community back to IRC. I still had the IRC Podman containers kicking around, so that was easy.

I dealt with ~monthly issues around my devices not being correctly verified, messages not correctly decrypting, and various other rough UX edges. There seemed to be a lot of velocity in the beginning but the last couple of years have addressed approximately nothing in terms of the UX and it's a crying shame as Matrix/Element (I no longer fully understand the difference/relationship between these entities) had a lot of potential.

The beginning of a post series? Could be interesting. De-Cloud is a great term for what you’re doing.

It’s a shame. There was a brief moment where there was lots of velocity on the “MSC”s as they call them - protocol features. The reference server implementations would be updated quickly, and Element would follow suit. It was exciting to follow and I would look forward to the new features hitting the clients every month or so.

I feel like that’s completely stopped.

For example, I’m still waiting for reasonable documentation to be published about how to deploy and use Element Call, which has apparently been generally available for over a year.