moseschrute

joined 3 months ago
MODERATOR OF
 

My Apple TV updated overnight to 18.2.1. I don’t see a 18.2.1 update for my HomePods yet, so they’re on 18.2. My ATV drops WiFi constantly unless I disconnect the HomePods as an audio source output.

The solution was to update the ATV to 18.3 beta 3 and leave the HomePods on 18.2.

This is mostly a PSA in case anyone else experiences the same issue. Reset my ATV before identifying the issue.

[–] moseschrute 1 points 2 days ago

I haven’t. I can’t speak to Eufy specifically, but battery-powered wireless cameras are not ideal. Battery-powered or wireless individually isn’t ideal. I think most battery cameras won’t do continuous recording, and with wireless, expect lag issues.

I just swapped my Ring doorbell, which did motion detection recording, not continuous, for a ubiquiti g4 doorbell pro. That got continuous recording, which is so much better. But I opted not to run an Ethernet cable, which I’m kind of regretting now. I was using Homebridge for Ring and Ubiquiti to get the cameras into Apple home.

On the other hand, Eufy is probably much cheaper and simpler to set up. So if you don’t care about continuous recording and you can deal with lag, it’s probably a good option.

[–] moseschrute 1 points 3 days ago

Blorp lol. Don’t ask about the name. Very much a work in progress, but I’m aiming for a public beta in 2ish months. Though I know it’s very likely I’ll be the only one that uses it.

As an Android/iOS app, Blorp will cache the data (and optionally images) offline. So any feeds/posts that are already loaded you will be able to read offline.

Right now that’s the biggest feature setting me apart from Voyager, but I want to keep iterating and improving.

This is the website version, which admittedly is a bit more clunky than the iOS/Android app. https://blorpblorp.xyz

[–] moseschrute 6 points 3 days ago (1 children)

Yeah I’m curious too! What technical sorcery is OP doing for presumably free API access

[–] moseschrute 11 points 3 days ago* (last edited 3 days ago) (2 children)

And this is actually the issue. As a developer I want to build and app based on what interests me. Then I want to write a post about it.

The comments:

  • person 1: Why would you waste your time building an app for that platform, you should build an app for this platform that way less people use”
  • person 2: “nah that’s a waste of time you should build an app for this even more niche platform with even less users”
  • person 3: “you should just use RSS feeds and anything else is a waste of time”

Me as a developer “thanks guys I just wanted to build an app for a platform I’m passionate about”

Wrote this comment on my own lemmy client, because I like using about lemmy :)

[–] moseschrute 1 points 4 days ago

Idk maybe I'm wrong. I worked for a news outlet for a couple years and I just remember generating and parsing XML to be more work then generating a JSON feed.

It's not even just parsing. I just remember crawling the parsed JSON tree to not be as nice as navigating a JSON object.

[–] moseschrute 1 points 4 days ago* (last edited 4 days ago) (2 children)

But a lot of languages have native support for parsing JSON without the need for a library. When it’s handled by the language, it’s more likely to be done to spec, doesn’t increase bundle size (if that matters to you), and will be considered as updates to the language are made.

[–] moseschrute 11 points 5 days ago (1 children)

They put THC in drink form now too :)

[–] moseschrute 8 points 5 days ago (5 children)

I get that the idea of rss is sort of a universal protocol for publishing articles, which is really cool, but damnit if you make me parse XML in 2025. As a developer, I would be ok if they modernized RSS feeds.

Something like this

[–] moseschrute 8 points 5 days ago* (last edited 5 days ago) (1 children)

Professor (who also wrote the textbook): btw you’re using the 30th edition, but were actually on the 31st edition

Me: what’s the difference?

Professor: page 12 is totally different

[–] moseschrute 35 points 1 week ago (3 children)

Honestly my M2 MacBook Pro feels like it’s built to last. I paid a lot, but I feel like I’ve gotten great value out of it and genuinely enjoy using it. And it’s still going strong.

But we have to talk about Apple’s hostility towards developers. It’s like they want to make devs miserable. That’s the part that’s unforgivable imo.

[–] moseschrute 1 points 1 week ago

My very not scientific understanding is that using a VPN to a remote server is like throwing your internet traffic into a blender with everyone else using that server. So isn’t this the one time it’s better to not self host so your traffic is mixed into a much larger pool of other VPN traffic? Or am I missing something.

 

The email analogy is really… boring.

Full disclosure, this idea is for a Lemmy client I’ve been toying around with making. I’ve gotten a bit in my head and would to run an idea by everyone.

The challenge:

Onboard people onto Lemmy in a way that makes sense to people that understands Fediverse and explains it well enough that typical social media users will understand it too

My onboarding flow idea.

As you read this, think of CARROT weather, an app with a funny personality.

You are an alien creature exploring the Lemmy Verse, a federation of social planets. You must chose a home planet, then you are free to explore its local communities or any of the communities in the lemmy federation of planets

I might give the alien creature a name. TBD.

Is this stupid?

Remaining challenges:

  • I suspect a guiding the user to select the same “home planet” if they log out could be an issue.
  • Should I explain that not all planets live in the same Federation? I’m thinking no.

Would love to reinforce this with animations that really drive the idea home. Almost like cut scenes from a video game. But that is beyond my area of expertise, for now.

 

cross-posted from: https://sh.itjust.works/post/29038131

I'm a decent developer, but with only a couple years' professional experience and no formal training. I'm looking for open source projects to contribute to (ideally pick one or two and get dedicated to them).

I'm open to small or large projects.

I'm using this as my source of options:

https://fediverse.party/en/miscellaneous/

But I'm curious if there are other ones, or if you all have ideas about which ones are needing and deserving help.

Thanks!

 

Recently picked up a Kinesis Advantage 360 Pro and I love it! I also love bringing my laptop to the coffee shop to do work.

I’m wondering how difficult and expensive it would be to build a custom split keyboard to match the Kinesis as closely as possible. I would want this keyboard to be flat and use low-profile keys, but have the same thumb clusters and ortholinear layout allowing me to utilize the same muscle memory. I would also like it to be flat enough that I can fit it in a laptop sleeve case.

I have no idea how difficult it is to build custom keyboards. I’ve watched a few videos, but I would love some tips. I have some very basic soldering skills and I would love a fun project!

I want something designed to last, but I would love to do this for under $200 if possible. I have no idea if that’s remotely realistic.

If there are prebuilt split keyboard that match the Kinesis closely, I’m happy for recommendations but I figured this is specific enough it would need to be custom.

Thanks in advance!

22
First ergonomic keyboard (self.ergomechkeyboards)
 

Just got my first ergonomic keyboard! Coming from a Keychron K2 and now using a Kineses Advantage 360 Pro, which I picked up refurbished for a nice discount.

I’ve been using it exclusively to type for a week, and today I used my M2 MacBook Pro keyboard for the first time in a week.

To the person that decided computer keyboards should be staggered instead of ortholinear, I hate you.

I know there is history to the keyboards being adapted from typewriters, but I realized I’ve been hitting the entire bottom row of keys with the wrong finger. For example, I’ve been hitting Z with my ring finger instead of my little finger.

I could give up the thumb clusters, but I really wish Apple would give you an ortholinear keyboard option in their laptops.

I also keep hitting the wrong key on the Kineses because all the keys are so much closer now than I’m used to. It takes so much less movement and I love it!

 

Here are the problems I want to solve:

The same app everywhere

It will run as a website, iOS app (also on macOS), and Android app. It will be responsive, supporting phone, tablet, and computer screen sizes along with everything in between.

And I’m not talking about simply resizing the interface. Navigation (e.g. sidebar or on mobile bottom tab bar) will match what you would expect to see on the device size you’re using. But everything else (e.g. posts) will look the same, which I hope will make it really easy to jump from mobile to desktop.

Onboarding and configuration

The app will allow you to configure it to look like a typical Reddit or Lemmy app. During the onboarding process, I will prompt you, asking which style of interface you prefer. Consider these presets, which change a bunch of more granular configuration options. I will also give you the ability to fully customize each option instead of picking a preset.

Caching and offline support

This is where it starts to get more tricky. Caching is easy. If you launch the app, it will have everything you previously saw still loaded.

I would like to make it so upvoting, for example, can be done offline. The app will optimistically apply the upvote to the post or comment, then when you reconnect to the internet, it will actually apply the upvote. This is a difficult problem to solve, so I can’t promise this will work, and it would likely be the last feature I add.

I need your feedback

This is a big project to undertake. I really want a Lemmy client that checks those boxes for myself, but I’m curious if any of those resonate with you? Is there anything I missed that you would like to see? If I do build this, I will likely have to keep the project very focused as far as features go initially.

Just for context, I’m using Voyager on iOS currently. I really like it, but the “the same app everywhere” concept and making it easier to onboard Reddit users are my main motivations for creating my own app. My app will also be fully open source

 

I’ve spent some time messing with WLED, which is a DIY addressable LED light solution. For example, an addressable light strip means you can control individual LEDs— instead of just the strip as a whole— which unlocks patterns and animations.

Govee is an off-the-shelf plug-and-play solution. This is pretty next level, especially considering “stage scene” is a new feature they added.

The 2min video is worth the watch if you enjoy sick lighting.

40
submitted 1 month ago* (last edited 1 month ago) by moseschrute to c/technology
 

cross-posted from: https://lemmy.world/post/22399282

Wemo Stage is one of those devices that has a horrible rating if you check Amazon. However, it fills a device category that up until now has essentially had no competition and is honestly not terrible for a first of its kinds device. The category I’m referring to is battery-powered thread light switches. As someone that rents, I can’t install light switches in the wall, so this has saved my smart home by allowing me to install renter-friendly physical controls for Apple Home.

But there are a few differences:

Wemo Stage

  • HomeKit over thread
  • Mediocre battery life
  • Responsiveness is okay most of the time, but it really depends on the stability of Apple Home and can lag
  • 3 programmable buttons, each supporting single, double, and triple tap for 9 programmable shortcuts

Nanoleaf Sense+

  • Not actually tied to HomeKit in any way
  • Uses Lightwave (Nanoleaf proprietary protocol) over thread
  • Bypasses Apple Home (thread border router) altogether
  • Near instantaneous response time, and doesn’t seem to lag ever
  • On, off, and dimming controls. Two extra programmable buttons that will eventually support Matter (coming soon supposedly)
  • Includes motion sensor that can control lights via Lightwave protocol

The Sense+ is very new. I’ve only had mine for a few days after pre-ordering the switch. I was really hoping the Sense+ would be better all around, but despite its instantaneous response time, it has a few major drawbacks:

  • lack of support for non-Nanoleaf lights
  • built-in button programming is very limited; you can’t program a button to set both brightness and hue. Seriously, Nanoleaf?

I wish they could have the switch support direct control of any Nanoleaf light, but fall back to Matter control for anything else. Though I suppose mixing protocols could get messy. But Lightwave is really solid as long as you live within Nanoleaf’s walled garden. But as soon as you throw anything else into the mix, the illusion shatters.

I’m sure the Sense+ will mature with software updates. I’m excited to see how Nanoleaf improves the product!

I may mess around with more wireless Thread switches. ONVIS makes one that is more of a button form factor than a switch. But for now I find myself having to choose between Sense+ which is more responsive, or Wemo Stage which can control more devices.

 

cross-posted from: https://lemmy.world/post/22399282

Wemo Stage is one of those devices that has a horrible rating if you check Amazon. However, it fills a device category that up until now has essentially had no competition and is honestly not terrible for a first of its kinds device. The category I’m referring to is battery-powered thread light switches. As someone that rents, I can’t install light switches in the wall, so this has saved my smart home by allowing me to install renter-friendly physical controls for Apple Home.

But there are a few differences:

Wemo Stage

  • HomeKit over thread
  • Mediocre battery life
  • Responsiveness is okay most of the time, but it really depends on the stability of Apple Home and can lag
  • 3 programmable buttons, each supporting single, double, and triple tap for 9 programmable shortcuts

Nanoleaf Sense+

  • Not actually tied to HomeKit in any way
  • Uses Lightwave (Nanoleaf proprietary protocol) over thread
  • Bypasses Apple Home (thread border router) altogether
  • Near instantaneous response time, and doesn’t seem to lag ever
  • On, off, and dimming controls. Two extra programmable buttons that will eventually support Matter (coming soon supposedly)
  • Includes motion sensor that can control lights via Lightwave protocol

The Sense+ is very new. I’ve only had mine for a few days after pre-ordering the switch. I was really hoping the Sense+ would be better all around, but despite its instantaneous response time, it has a few major drawbacks:

  • lack of support for non-Nanoleaf lights
  • built-in button programming is very limited; you can’t program a button to set both brightness and hue. Seriously, Nanoleaf?

I wish they could have the switch support direct control of any Nanoleaf light, but fall back to Matter control for anything else. Though I suppose mixing protocols could get messy. But Lightwave is really solid as long as you live within Nanoleaf’s walled garden. But as soon as you throw anything else into the mix, the illusion shatters.

I’m sure the Sense+ will mature with software updates. I’m excited to see how Nanoleaf improves the product!

I may mess around with more wireless Thread switches. ONVIS makes one that is more of a button form factor than a switch. But for now I find myself having to choose between Sense+ which is more responsive, or Wemo Stage which can control more devices.

6
submitted 1 month ago* (last edited 1 month ago) by moseschrute to c/[email protected]
 

Wemo Stage is one of those devices that has a horrible rating if you check Amazon. However, it fills a device category that up until now has essentially had no competition and is honestly not terrible for a first of its kinds device. The category I’m referring to is battery-powered thread light switches. As someone that rents, I can’t install light switches in the wall, so this has saved my smart home by allowing me to install renter-friendly physical controls for Apple Home.

But there are a few differences:

Wemo Stage

  • HomeKit over thread
  • Mediocre battery life
  • Responsiveness is okay most of the time, but it really depends on the stability of Apple Home and can lag
  • 3 programmable buttons, each supporting single, double, and triple tap for 9 programmable shortcuts

Nanoleaf Sense+

  • Not actually tied to HomeKit in any way
  • Uses Lightwave (Nanoleaf proprietary protocol) over thread
  • Bypasses Apple Home (thread border router) altogether
  • Near instantaneous response time, and doesn’t seem to lag ever
  • On, off, and dimming controls. Two extra programmable buttons that will eventually support Matter (coming soon supposedly)
  • Includes motion sensor that can control lights via Lightwave protocol

The Sense+ is very new. I’ve only had mine for a few days after pre-ordering the switch. I was really hoping the Sense+ would be better all around, but despite its instantaneous response time, it has a few major drawbacks:

  • lack of support for non-Nanoleaf lights
  • built-in button programming is very limited; you can’t program a button to set both brightness and hue. Seriously, Nanoleaf?

I wish they could have the switch support direct control of any Nanoleaf light, but fall back to Matter control for anything else. Though I suppose mixing protocols could get messy. But Lightwave is really solid as long as you live within Nanoleaf’s walled garden. But as soon as you throw anything else into the mix, the illusion shatters.

I’m sure the Sense+ will mature with software updates. I’m excited to see how Nanoleaf improves the product!

I may mess around with more wireless Thread switches. ONVIS makes one that is more of a button form factor than a switch. But for now I find myself having to choose between Sense+ which is more responsive, or Wemo Stage which can control more devices.

view more: next ›