Not sure if it has been mentioned already but photoprism added face recognition a few releases ago and it is working well for me: https://github.com/photoprism/photoprism
The quality of this software is overall extremely good. It is a solo-developer as well so you might want to consider sponsoring them if you end up using it.
Seconding photoprism. The face recognition was pretty meh when it was first introduced, more of a gimmick than anything. But (I assume) a recent update pushed it into "wow, this is actually really good" territory.
Thirding photoprism, got it hosted on a raspberry pi and made it accessible outside of my home via Tailscale. Seems to work fairly well... though I could probably make it faster with an SSD vs an HDD over USB.
To photoprism users: do you know how well it handles identifying photos of kids over the span of years?
Google photos absolutely blows me away with its ~1% false positive rate (that is, given a photo, correctly identifying with kid(s) are in it) identifying each of my kids, nieces, and nephews. I don’t really know what its false negative rate (a false negative would be an uploaded photo of John but that doesn’t get tagged as having John in it) is, though.
I can search for each of my kids and see photos of them going back to their birth.
Photoprism is absolutely amazing. It was the quickest donation I’ve ever made to an OSS project.
I have a Photoprism instance running on my home server backed by a raidz1 ZFS pool (1st backup). Photos are periodically synced to a Backblaze bucket with versioning enabled (2nd backup). The source of most photos is an iOS device with iCloud enabled (main copy). I rely on PhotoSync to periodically sync from the iOS device to Photoprism.
This gives me sync across my devices for free and the data format is just CSV so I can easily paste it into a spreadsheet app and do the end of month accounting.
There is hacking the functionality together in an hour or two and then there is polishing it to the point where it doesn't have rough edges and can easily be used by anyone with terminal experience.
Personally, the chosen feature set resonates a lot with me. I like services that don't need accounts f.e. because they are so easy to use.
I guess it depends a lot on what you think a government should spend money on or what its role is. IMO the 9€ ticket was a great idea because it was simple and unconditional.
Social security laws and subsidies are usually riddeled with exceptions and rules on when you qualify which require more people (meaning more expenses for the government) to check them.
In a society that is constantly chasing for even more convenience, reducing as much friction as possible for taking public transport seems like a good idea and far from a disaster?
Water electrolysis is around 60-80 percent efficient. Hydrogen fuel cells are around 40-60 percent efficient. Plus you spend additional energy to either compress or cool the hydrogen in order to be able to store it.
Electricity storage in a lithium-ion battery is on the order of 98% efficient, and electric motors are around 90% efficient (if you take into account the whole drivetrain).
Yes, hydrogen and ammonia handling efficiency will mostly go up, unless extra-cheap (to buy) electrolysers come out with unfortunately lower efficiency.
What always matters most is cost. Inefficiency will get cheaper and cheaper as generation cost falls. Switching from gold & platinum catalyzing electrolysers to something not dependent on those and less efficient is still a win if you get a lot more electrolysers for your money.
Conversion from water to hydrogen via hydrolysis is only 60-80% efficient so it takes more energy to generate the hydrogen than the hydrogen will produce in future.
It is absolutely trivial that separating hydrogen from water uses energy. Then, when you burn it, you get water and energy back. That is the whole point.
That is trivial yes and I was well aware of that :)
What wasn't obvious to me from the parent comment was why it is apparently completely impractical. No energy conversion has an efficiency of 100% so the answer couldn't just have been "because thermodynamics" but as other comments have since revealed, it is because _current_ hydrolyzers only operate on an efficiency scale of 60-80%.
And, turbines and fuel cells are also at ~40-60%. So, round-trip is a fair bit lower than that, as little as 25%. But it doesn't matter much. Efficiency is improving, and will be much better before anything depends on it.
What do you imagine is the raw efficiency of making hydrogen from. NG, vs the enthalpy of the input gas?
BTW, "electrolysers". Hydrolysis is a thing plants do.
> When you commit to a version 1, you assume that every user of the package is using every feature you provide through your official API. If you break any slightest piece of the API, you've broken compatibility.
That is not how semver works. If you read the documentation [0], it says right there that the public API must be clearly defined but that can also happen through documentation and you only have to up the major version if you break that specified public API.
You can certainly consider it bad programming practice to expose something via the means of the language that is not defined as public API but it is not against semver to do so.
If you think that way, then everything is incompatible, because the person using your lib could always do a hash of your lib file and create code that depends on it:
if hash(libpath) != predefinedHash {
log.Fatal("broken compatibility teehee")
}
In the context of semver, "API" means "public API". There is no other API but public API.
Yes perhaps I misunderstood you. I was trying to point out that semver is okay with having elements in the "public" API of a library (public in the sense of you can import and use it, i.e. not hidden in private modules etc) but explicitly documenting that it is not considered public API in regards to semver.
If that is what you meant with "official API" then we are on the same page.
The quality of this software is overall extremely good. It is a solo-developer as well so you might want to consider sponsoring them if you end up using it.
I am not affiliated, just a happy user :)