

I don’t see why this would be funny or weird. It isn’t like Apple where there would be no other devices to use them…


I don’t see why this would be funny or weird. It isn’t like Apple where there would be no other devices to use them…


Immich obviously does not follow semantic versioning when 2.0 is to be considered the first stable version.


I’ve had a bunch of different smart plugs, but as of today I only use the Shelly ones. They never failed me, have hardly any delay, are very configurable (if needed) and I even converted some of my wall plugs to Shelly devices.


I totally agree with you that having Google as the only one able to assign these certificates is a problem. This needs to change (and I rely heavily on the EU to enforce this), but I still think that everyone who is publishing an app to an undisclosed number of people (and therefore there is no implicit trust by design) should identify him- or herself to some authority.


My argument isn’t “it could be worse” - my argument is “that’s how it should have been from the beginning”.


At the moment (I am willing to change my opinion if that changes) Google has announced that for your personal use you won’t need to submit any ID. This just shows me you haven’t even read the whole thing, but just the headline and your opinion on this was set.


That freedom is still there. The only thing going away is installing from an undisclosed source.


If you want to distribute an app to a larger audience you should be willing to do so. Sure you could say it’s everyone’s personal risk installing an unsigned app on their phone, but making these people compile the app themselves isn’t too much to ask for. Tools to automate this to the max will appear.


I know I will get downvoted for this opinion, but I like this.
Developers who decided not to use Play Store can still do so, but are required to identify themselves. I get that not everyone is willing to do this, but there still is a free way to compile apps yourself and put it on your phone.
I am a developer myself and I have published apps for iOS and Android in the past and this process still is way easier than anything an iOS developer has to do to just install an app on his personal phone.


It is, but hear me out: There is a difference between failing with a reason and failing silently - and seemingly with no reason. I don’t know this project and I don’t know what happened and how the creators handled this, but I have been on Kickstarter since it came to life and I have seen projects with poor communication fail and everyone was furious and I have seen projects fail who managed to communicate their struggles to their investors very well and they didn’t get overrun with refund requests. I know it is hard to admit problems and finally failure, but it has to be part of the progress.


I liked it. It was the perfect length to listen to and the voices are well cast and distinctive enough. The only thing I didn’t like was the intrusive (for a lack of a better word) music in some parts. As if they needed to further emphasize “this is the part where romance is supposed to happen”.


This is something my mother used to do as well. When the machine was finished she opened the door and let it vent. I asked the guy installing our machine some years ago and he told me that in newer machines that won’t be necessary and could even disable the integrated venting mechanism. But of course this depends on your machine…


alternativeto.net is also my go-to resource because they have a good filtering system and are not solely focused on open source.


The new automation editor is nice. I have some automations that are quite complex and it is always a pain to edit them (especially on mobile devices).


There is Cesium. But the thing you actually need is the actual maps. There are free maps (many of them based on OpenStreetMap), but the fidelity you know from Google Earth is usually not free. Also if you also want to self-host the actual maps you need a tile server for that and lots of disk space because these tiles take up a lot of it…


That might be cynical but it’s true. The fans who liked the book(s) will with a fair chance not like the adoption. So an amount of your hardcore fan base is already against you. The idea would only work if the book series has for some reason a (partially) different target audience than regular trek.
That’s not quite all of it. It can also do diff updates (so you don’t have to download the whole apk), staged rollouts and different builds for different devices. And of course it provides APIs for license management, in app purchases, update notifications, etc. All of this could be achieved by using other services (like F-Droid) or custom build websites, but the convenience for the everyday user isn’t quite the same.


Also maneuvering a space vessel with two thrusters which are facing in opposite directions may be impossible…
Adding a single airlock replacing one of these thrusters (which therefore must be incredibly weak) makes it even more of a mess…


Yet the movies only got successful once they got a lot of the TV guys back for set design, wardrobe and makeup for the second movie.
You may want to change the title and include the word “protection”…