Yep just saw that too after I researched it a bit more. What is strange is I don’t remember Eve Energy having a firmware update since then. Makes me wonder if they had it ready to go in previous firmware versions based on internal specs they saw? Or maybe I just forgot about a firmware update I did.

but as the Matter standard doesn’t yet support energy monitoring, users are limited to basic features like on and off and scheduling

- from this link

Granted the article is almost a year old. But I just didn’t realize that Matter now supports energy monitoring. Somehow I just missed that news.

I wish it worked on more webpages. But totally agree.

What? I’m not following. Steam isn’t federating with anyone. This is about having a link to an external site. Nothing more. Has nothing to do with federation directly.

That is so bad. They clearly don’t understand the appeal of decentralized systems…

For Mastodon there is something called Tootpick which allows you to enter your server’s domain and share any content by redirecting the user. For example: https://tootpick.org/#text=https://eventfrontier.com/post/37808. So I’m not quite sure the federated nature argument makes sense. Sure it’s more complicated that a centralized system, but possible regardless.

At this point it’s like, why not use Ethernet?

https://lemmy.world/post/1293336

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!

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.

Has 2023.6.2 or 2023.6.3 been better for you?

Ads too 😉

@[email protected] 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.

Ok, but the TypeScript code is generated directly from the Lemmy Rust code (shown here).

But even for community_name the TypeScript file has no comment whereas the documentation does.

So even if the TypeScript files are the source of the documentation (which it doesn’t look like it is), it doesn’t seem like that is the original source since it’s getting generated from Rust. And not quite sure how that process works.