Feels like this would just be adding on a centralized feature to a system designed to be decentralized. If anything, it should be based on a decentralized system like Bitcoin or something.
Personally, that isn’t how I think about a smart home system. There isn’t a need to do major changes until maybe you need to get it replaced anyways. Starting with things like lights, a few shades, door sensors, are good ways to start. The biggest question is what do you want to get out of it?
The craziest thing is that Elon’s tweets are still completely visible.
So if you were moving to another home or apartment, is it a reasonable strategy to stop paying rent at your current home while you’re looking for a new place? Of course not. Same idea here.
I’ve seen some weird behavior on other things like this.
Has 2023.6.2 or 2023.6.3 been better for you?
@MentalEdge@sopuli.xyz If the instance is overloaded, how do you still get posts then?
Does the subscription being pending remove any functionality or change the behavior at all?
I have a lot of them from Beehaw.org. What I didn't expect is I still seem to be seeing posts from those communities in my subscribed feed.
@dessalines@lemmy.ml Thanks for the information here and all the hard work you have put into this release.
Gotta say tho, as the maintainer of Lemmy-Swift-Client, breaking API changes like this without an API version bump, make API development within the community incredibly difficult.
So my question to you would be, what is the purpose of having v3 in the API path, if the true test of API compatibility is the GetServerResponse version field? And breaking changes will occur in GetServerResponse version changes as opposed to the version in the API path? That doesn't quite make sense to me.
Would love your perspective so I can figure out how to best design the package API to accommodate client developers who might have to contend with multiple server versions.
If you're into JavaScript, https://github.com/dynamoose/dynamoose is a project I maintain, and has a lot of great documentation, Slack channels, and more.
Although my attention on it goes in waves, it could for sure use more help. I'm also totally willing to help answer questions and point people in the right direction.
We currently have 80 open issues, 6 open PRs. 9 of those issues are marked as "good first issues" and 8 are marked as "help wanted".
So there are for sure some easy jumping off points to get started. But I'm also always happy to answer questions and assist in anyway I can as well.
Beyond that, it's all about diving into something. I found Dynamoose when it was much smaller, and just started with small contributions and built up from there. Following developers on social media, and following programming communities and newsletters can be helpful too.
Good feedback. This is meant to be extremely initial. I absolutely understand the hesitation to collecting PII. TestFlight does capture a lot of this data automatically when you sign up using a link anyways. Once it gets into beta (or even later alpha stages) I plan on releasing a public link that doesn’t require an application. I really appreciate your honest feedback tho, and I’ll definitely take it into consideration and consider alternatives in the coming days. Thanks again!