joshspankit
This is where I tapped out. They could have done so much to open the industry for makers once they had traction but instead they went the other way. Disappointing at best.
If RMA process includes hardware verification then rpi doesn’t get bled out by absorbing the cost of “counterfeits”
If they widely tell people what the market is doing and make all the tools public, they will offload the work of dealing with counterfeits while levelling up the tinkerers
When they can justify it, they will add features to macOS which bog down the older systems. Eventually they will say that older systems just don’t have what it takes to run macOS and stop supporting them
Apple has never had an issue with taking machines that can last out of the market
See iOS for a great modern example
Look at rowhammer: a completely novel exploit that was off the collective radar
And then, look at the software industry as a whole: an industry that works towards refined and perfectly secure code is also working towards boring and restrictive, essentially the opposite of it’s trend so far
hard:
- Overall security
- User permissions in multi-user deployments
- Input sanitization
- RDBMS schema design
- Parsing
- Bit-rot protection (here because it’s rarely on the radar of the general user)
easy:
- DB queries against a known schema
- Working in a front end HTML/CSS/JS stack
- Making UI components
- Moving those components around
To your question about why moving front end away from devs would reduce load: a person making a UI they want is a different category of work than creating a UI that everyone wants. Even if it’s easy, it’s distracting to be thinking about everyone’s use-cases and refining the details.
I am not a regulator but that feels like something that needs new rules
Many powerful and interesting people were having powerful and presumably private conversations in rooms because they say people walk in and out and legally CH could not record without consent. But what they could do was “collect metadata”. Emotional and tonal analysis is metadata. So is time, date, location, username (each user had their own mic stream), email, etc. Transcription is also metadata.
Essentially the tech has left the laws in the dust as you could now reasonably and legally record enough metadata to accurately resynthesize a recording.
What I meant to ask was “If you use GOS, does it matter if Google ends support” and after your comment I read deeper to find the answer “yes, because GOS relies on Google to maintain the firmware”. Thanks for the push
Like, let’s use a simple photos example: a photo file has metadata standards already embedded, but doesn’t store it’s edit history, event, or who’s in it. Immich already does a lot that’s great here with parsers and ML and if they changed focus to the data storage layer they could essentially boil down to a table for edit history, a table for events, a table for people, etc, the ability to store in SQLite or sidecars, and an API layer for people to hand to their AI.
Not only would it reduce the dev load, but then we could have an ever-expanding sphere of personal data ownership as Futo adds schemas/tables for video, audio, documents, and maybe everything else most people need to build their own UIs for specific uses or even “god view” UIs.
I feel like Futo is going in the wrong direction. In the age of AI, anyone can write a DB query, anyone can design a simple UI, and with docker the structure of hosting is no longer a barrier.
I think Futo and Immich should be focusing on data itself. Export, import, store, parse metadata, process, suggest relationships
If you’re targeting data for people to use on the same call then requires more intense work, while if you’re targeting data for people to use after or on an ongoing basis (eg an established business meeting with staff/vendors/etc) then having a predefined one seems good. Same interface as a CRM: picture, some audio clips for users to choose from, and confidence scores on each section of the recording for cases where people sound similar or are talking over each other. Over time the diarization gets better as users accept/reject/tag samples and that work helps them feel more aligned with the tool.