Interesting. If you have any talks or articles, I would love to learn more. Without knowing anything about PieFed vs Lemmy, I will say I do think it’s important with any product to nail down its core functionality first. Trying to please everyone can degrade the overall quality of the product. Is it possible Lemmy is focusing on core functionality first? Like it’s interesting that PieFed includes some features but lacks more basic features.
Swapping out API calls shouldn’t be too difficult, but if the schema of the data is very different, it could get difficult. If PieFed was a superset of Lemmy in the sense that it returned the same schema with additional information, then it becomes easier. AT Protocol is a good example of having a completely different schema, making it more difficult to implement interoperability - I know people are working on interoperability, so I’m not saying it’s impossible.
I know nothing about PieFed, so that may sound ignorant on my part, but I will do more research.
That makes sense. I appreciate the history lesson. You’re right, my account is very new, and I’m new to Lemmy. Maybe the protocols you mentioned are more compatible than I realize. I would imagine that if Lemmy.world migrates, what they migrate to will be more similar to Lemmy than something like AT Protocol. So it might be okay to run with Lemmy for now and then adapt later depending on where most users wind up.
I still would like to keep the project’s scope smaller, but if there was a mass migration from Lemmy, I would absolutely reconsider. Let me also read up on the similarity of the protocols. If interoperability is easy to do, I’ll consider interoperability from day one.
Apple is pretty stingy about how often tasks can run in the background. Offline first quickly spirals with complexity that isn’t immediately obvious imo. That’s why I don’t want to make fully local first as a core feature.
I need to set some constraints for the project. IMO, going multi-protocol will be too much work. I would rather do one protocol really well than try and satisfy multiple. I also primarily use Lemmy, and a Lemmy-based app is something I myself would actually use. Doing a different protocol would require me to put myself in the headspace of users that I’m not as familiar with. Much of building an app is sympathizing with your user base not just technical.
But I plan on making the app open source, and that means it can always be forked and adapted to a different protocol later. And I’m happy to draw inspiration from other protocols.
I appreciate the idea! I think a multi-protocol app would be great, but again I think for this project and my limited time, doing one thing well would yield a better result.
I have experience doing YouTube embeds. It’s not hard. It’s just a question of all the different types of media embeds I also choose to support.
Yes! Exactly, I don’t think offline first should be a high-priority feature. I will spend too much time trying to get it perfect at the cost of other features.
Respectfully, I don’t think it’s that simple. I think it’s one of those problems that appears deceptively simple, but when you dive into it, it becomes a big headache. One big difference between truly offline first and arbitrary web requests is an offline first app imo should let you close and reopen the app without dropping those pending interactions. When you marry this with cross platform, you need a robust database solution on both native and web, which makes the stack more complicated. I will consider making aspects of the app offline first, but I have decided not to make fully offline first a core feature.
I do share the offline first ambition! I also probably have ADHD and a tendency to start projects without seeing them through. I think it would be wise for myself to keep the initial scope of the project small. I would love to build the app that solves everything, but in practice I know I likely won’t be able to make that happen.
From what I’ve seen, fully offline first would be more work than I believe it’s worth. Especially when you add the complexity of being cross-platform. I think I have to choose cross-platform or offline first, and I would rather solve cross-platform really well (better than Voyager IMO).
So it’s not that I don’t share your ambitions, but I need to be realistic. But if an app existed that solved all the things you mentioned, I would happily use it!
I appreciate you being understanding, and please continue to share your ambitions. I just encourage you not to be frustrated if someone closes a GitHub issue you open. Maintaining open-source software is taxing, and it doesn’t mean that the person closing the issue doesn’t like your idea.
You know how when a hobby becomes your job, it often stops being fun and leads to burnout? Side projects are fun because they offer you an opportunity to build something on your own terms. I want to build the app that I want to use, and I want the freedom to make decisions.
At the same time, I want to hear from the community, and I will take into account that feedback for decisions I make.
Respectfully, some of those issues you opened up are really big asks. Specifically, offline first (RxJS) and adding activity pub support. Initially, my idea was to build an app that did both of these, but after some experimentation, I decided I would burn out before the project ever saw the light of day just trying to solve offline first.
I would still love to hear from you. But I have ideas for what I would consider core functionality, and that will come first. But I will take feedback into consideration and will likely implement some offline first functionality, which will be way simpler than being fully offline.
My tech stack will be similar enough to Voyager that it’s possible I can copy past parts of my code into their app. So I’m not ruling out contributing back to Voyager, and writing my own app doesn’t mean I won’t learn stuff that I can contribute to other clients.
That’s amazing! I’ll reach out to some of the devs.
True. The thing is, my day job dictates the tech stack I use. There are specific technologies I want to learn in my free time, and those technologies happen to align well with this app, in my opinion. Forking is probably the smarter move… but I think I’m going to do it my way.
That makes sense since upvoting and commenting seem the hardest to me. I think anything that interacts with existing content in the API will be more difficult to do offline than creating new content (e.g. creating a post offline).
I’m very new to Lemmy and I need to read through their API. Whatever settings they allow me to save, I’m happy to lean on their API. I just want to avoid writing my own backend.
Thank you! Will 100% use this as inspiration.
I’m a seasoned developer with experience in both React on the web and React Native. I’m looking for an excuse to dive into Tamagui, which is designed the tackle cross platform. So I’m excited to tackle this challenge.
That’s a great point! I kinda want to write my own client, but I haven’t ruled out contributing to Voyager. It’s very possible I totally fail, learn from my mistakes, and bring what I’ve learned to an existing app like Voyager.
That’s a great question! As far as I can tell, Voyager is optimized for smaller screens, and larger screens are supported but not as well optimized. My app would have first-class support for large and small screen sizes. Alternatively, I may consider contributing to Voyager.
Sorry, I don’t mean this to sound rude, but websites don’t magically become responsive. It takes a lot of work. And that becomes even more complicated when you want to share large amounts of code between web and native.
I’m not reinventing the wheel. I’m using the best libraries—imo— to build a responsive cross-platform app.
Wow, I totally missed that. However, it does feel like the web was tacked on as an afterthought. It feels like navigation hasn’t been optimized for larger screens (see screenshot below). A sidebar would be much more usable on larger screens than this stretched bottom tab bar.
That being said, it would probably be easier for me to contribute to Voyager than to build my own app. But I also kinda want to build my own app, lol. But I might also consider contributing to voyager if they are interested in optimizing their interface for larger screens.
I assume you mean when my app caches a post, but that post is deleted from Lemmy. That’s a good question. Off the top of my head, I would say as soon as I know a post is deleted, I would likely want to purge it from the cache.
I guess it’s a question of whether I should respect the API saying the post is deleted or act like a temporary archive. I’m open to either. From a technical perspective, it would be simpler to act as an archive.
As far as the type of cache I use, I may use a LRU cache, which will effectively prevent something from being deleted every time you view it. So even if something was cached a long time ago, if you pull up that post again, it will reset the timer.
Thinking about making my own lemmy client, but I could use some feedback
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
Not strictly related to HomeKit, but this blew my mind
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.
My Nanoleaf Sense+ impression after using Wemo Stage
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.
My Nanoleaf Sense+ impression after using Wemo Stage
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.
My Nanoleaf Sense+ impression after using Wemo Stage
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.
Trying to get the HomeKit community more active
I’m not the moderator, but I picked the community with the most subscribers. Would love to learn more about your HomeKit setups! Please join!
Please come hang out with me in the HomeKit community 🥺
Hi, I recently made the switch to Lemmy from Reddit. But r/homekit is one of the communities I miss the most. What can I do to help build this community up? I’m happy to make posts, comment, and upvote. Is trying to poach people from r/homekit a bad idea? I would love to get to know everyone better....
I love Apple Home. It has its flaws, but— just like Lemmy— I love trying out bleeding-edge tech like Thread, Matter, mesh based routers and sick lighting. I also mess around with Homebridge, and I’ve considered trying Home Assistant. I’ve learned a lot, and I want to collaborate with other home automation enthusiasts. I’m going to try to post more to that community, but I wanted to put this out there if anyone is interested in collaborating with me to build up that community.
How can I help build this community
Hi, I recently made the switch to Lemmy from Reddit. But r/homekit is one of the communities I miss the most.
What can I do to help build this community up? I’m happy to make posts, comment, and upvote. Is trying to poach people from r/homekit a bad idea?
I would love to get to know everyone better. Here’s some info about my smart home.
- I’m using Apple Home, and my primary hub is a 4K Apple TV 4K Ethernet, which I chose for the Thread radio.
- I’m almost exclusively using Thread devices, and most of those are Matter over Thread.
- Most of my lights are Nanoleaf Essentials (Matter over Thread), and despite people hating Nanoleaf, they have been much better lately.
- For more advanced lighting, I’m using WLED, which is a DIY project for controlling addressable light strips.
- My WLED lights are bridged into HomeKit via Homebridge, though I’ve considered switching to Home Assistant.
- I’m using a Deco mesh router with two nodes, and it’s been amazing for the relatively low cost.
- Outside of Apple Home, I use Ring, which I’ve bridged into Apple via Homebridge. I hate the Ring subscription, but their hardware is solid.
Excited to get to know everyone!
I really want to like Lemmy
I hate big tech controlling social media. I desperately want social media to be federated.
I really love community-driven social media like Reddit. Lemmy feels… too small. I really loved that Reddit let me jump into any niche hobby, and instantly I had a community. Lemmy, you’ll be lucky if that community even exists, and if it does, chances are nobody has posted in ages.
On the other hand, Lemmy is full of political content lately. I’ve basically been doom scrolling everything US election-related, and it’s really starting to take a toll on my mental health.
I know I can filter content. I know I can post and be the change I seek. Yet, it feels like an uphill battle.
Not sure what the point of this is, or if it’s even the right community to vent about this. I just really want to replace Reddit, but I find myself going back more and more (e.g. r/homekit is very active compared to Lemmy version).
Primary hub constantly changing
Not sure if this has always been the case, or if I’m only noticing with iOS 18 allowing me to pin a primary hub, but my primary hub constantly falls back to my HomePod mini from Apple TV 4K WiFi.
Whenever this happens, all my lights go unresponsive. Absolutely infuriating.
So I’m sure the issue is WiFi. I have really solid WiFi speed/ping and relatively good range, but I live in a pretty WiFi congested apartment. So my guess is WiFi noise is knocking my primary hub out occasionally. But the odd thing is I never notice my WiFi dropping in other contexts.
But then again, maybe it’s not WiFi, because sometimes pressing a switch seems to trigger the primary hub dropping.
I’m so fed up, decide to buy an Apple TV 4K Ethernet edition to pin as my primary hub. My thought process is WiFi won’t drop, and built in thread radio means it won’t rely on external border routers (HomePod mini).
But I can’t believe the Apple Home experience is this bad. I’m pretty sure it wasn’t this bad pre iOS 18. I’ve never had more home hub failovers.