On the petty side—gets frowny cat, rather than horror cat. After a decade of Python, it’s surprising to me that Javascript doesn’t allow arr[-1] and such. Maybe negative indices returning undefined is widely relied upon, leading to compatibility issues? Not sure why it’s not a thing—arr[arr.length - 1] is just no fun.

In Javascript, Set treats objects only by reference, not by value, requiring weird contortions to maintain unique sets of non-primitive values.

In every other modern language I’ve worked with, the standard library set allows custom comparisons. But not Javascript.

In Java / Kotlin, HashSet defers to an object’s hashCode method, which can be overridden to control comparisons. With TreeSet it’s even easier: just pass a Comparator of your own into the constructor.

Python’s set will handle any hashable value, so overriding __hash__ and __eq__ should do the trick.

Rust’s HashSet relies on the Eq, Hash, and PartialEq traits—conceptually somewhat similar to Python’s approach, with Rust’s trait implementations and Python’s special methods being two ways to accomplish much the same thing.

But in Javascript, and by extension Typescript, the standard library provides no facility for useful sets of custom types.

https://medium.com/coding-at-dawn/how-to-use-set-to-filter-unique-items-in-javascript-es6-196c55ce924b

No Array.prototype.remove (a la Array.prototype.filter) 😿

You have to use splice based on an index instead. Would be much simpler to provide an item to be removed. The equivalent of arr.splice(arr.indexOf(item), 1).

https://stackoverflow.com/questions/5767325/how-can-i-remove-a-specific-item-from-an-array

A contact manager on steroids. Real social networks. A person or group view that shows all known interactions, notes/diary entries, etc.

Desktop application, I hope.

Set a weekly / monthly / annual donation level.

Daemon monitors app usage, and distributes donations proportionally, possibly through a third party service.

Identifies, indexes, and manages music files, and exposes them for playback via the Music Server Protocol.

Difference from Concept: Music Player Daemon: the playback occurs on the client, not the server

Differences from Navidrome: no built-in web interface; supports editing of tags.

Differences from Subsonic API: supports tag editing; has a concept of permissions; mult-user; more efficient than XML (I hope).

Differences from Plex: Music only.

Jellyfin: architecture looks good, all open source, but it seems video-focused and like it would suck for managing music; also seems to be .net-based

Totally novel API ?

Requirements:

• Scanning and discovery
• Uploads
• Permissions / users and ownership
• Tag editing
• Playlist building, names, images, descriptions
• Reencoding / transcoding
• Desktop and mobile client support
• Low-bandwidth connection support
• Gracefully handle albums, multi-artist albums, singles
• Music only. No videos, no podcast-specific support.
• Offline mode

Coming back to local Linux music playback, I’m pretty disappointed with the state of things. Spotify’s UI feels nice in comparison, which says something, given how neglected it seems. Things largely feel like 2016 or so. Every music player seems to solve the same problem using a totally new codebase, with only low-level libraries shared between them (reading MP3 or FLAC files, for example).

I can’t be the first person to have this idea… but, do like neovim did for text editing, like the Language Server Protocol does for coding: split apart core music playback functionality in a UI-agnostic fashion, and let interfaces interact with it via a socket protocol or whatever the equivalent of that is nowadays. (D-bus? MessagePack? no idea)

Handle the file formats, indexing, tag editing, output interfaces, notification of events, maybe interaction with online music repositories (e.g. FunkWhale)

Like this document. But in the open. Allow for comments on my project ideas, refinement, collaboration, etc. to bring things to reality.

this blog

A system for transcribing and selectively exposing your old journals.

Option: ship your journals to us, we use ML models to automatically transcribe and integrate everything.

Allow people to select which pages / passages, which people, etc. they want to reveal, and to whom. Set minimum age (e.g. only release 20 year old entries or older)

Automatic named entity recognition; similar to what photo services do with photos

Q: How good is handwriting recognition getting?

My stab at evolving a self-replicating virtual lifeform.