Good bot
I don’t know how I feel about this personally. On the one hand, I feel like this is a privacy win for those who want it: no watch history means no algorithmic recommendations and (presumably) less data collection for those users. On the other hand, I personally really enjoy the recommendations that YouTube makes for me. Maybe it is the wide variety of content that I watch, but I’m honestly very pleased with the recommendations that YouTube provides. That being said, I feel like the opt-in to algorithmic recommendations is a good thing overall, however I am personally going to leave my watch history enabled.
Thanks for the info. That seems quite heavy handed.
I’m out of the loop, what is France trying to do with regard to DNS?
Here’s the link to the study: https://doi.org/10.3390/s23136205
I’m posting currently from the PWA after I enabled 2FA on my account (not currently working with Jerboa). It’s nice and works well, but I prefer the more compact list view present in Jerboa. Other than that, no complaints!
Baby pineapple! How long did that take to sprout? I don’t know if I can grow them in 8a, but I might give it a shot.
Same. Projects like Lemmy are pretty slick, I just hope that the perceived barrier to entry due to the decentralized nature of the Fediverse won’t keep people from joining. There needs to be a “critical mass” of users to make a platform successful and engaging. Hopefully that happens to Lemmy due to the Reddit API fiasco.
Kind of difficult to give recommendations on where to start for resoldering, but my first hunch would be cold solder joints somewhere. I have a Kyria from splitkb that I assembled myself that had spotty LEDs on one half which turned out to be a cold joint on one of the surface mount underglow LEDs. Also had no key presses registered on a row that turned out to be a cold joint at the MCU.
As for general troubleshooting recommendations, if you can get a board schematic that would be immensely beneficial for your efforts as it would show how and to what pins of your MCU everything is connected. With that you can try to identify where the fault might be occurring (e.g. LEDs die after LED 5 in the chain) and focus your efforts before/after that area.
Failing the board schematic, you may be able to just visually see where the traces connect back to on the PCB, or you could probe it out using continuity mode on a multimeter and reverse engineer the connections.
Another thing that may aid in diagnosing where the issue lies with the double key presses is figuring out how the key matrix is laid out. For example if you’re receiving double presses on only some keys in a single row or column, the issue lies in either that row/column or the MCU pin they connect back to. Again, the board schematic would be really helpful in this regard.
Best of luck!