Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)SU
Posts
4
Comments
133
Joined
1 yr. ago

  • Quite aggressive there friend. No need for that.

    You have a point that intensive and costly training process plays a factor in the usefulness of a truly open source gigantic model. I'll assume here that you're referring to the likes of Llama3.1's heavy variant or a similarly large LLM. Note that I wasn't referring to gigantic LLMs specifically when referring to "models". It is a very broad category.

    However, that doesn't change the definition of open source.

    If I have an SDK to interact with a binary and "use it as [I] please" does that mean the binary is then open source because I can interact with it and integrate it into other systems and publish those if I wish? :)

  • Do you plan to sue the provider of your "open source" model? If so, would the goal be to force the provider to be in full compliance with the license (access to their source code and training set)? Would the goal be to force them to change the license to something they comply with?

  • You would be obligated, if your goal were to be complying with the spirit and description of open source (and sleeping well at night, in my opinion).

    Do you have the source code and full data set used to train the "open source" model you're referring to?

  • Excellent notes. If I could add anything it would be on number 4 -- just. add. imagery. For the love of your chosen deity, learn the shortcut for a screenshot on your OS. Use it like it's astro glide and you're trying to get a Cadillac into a dog house.

    The little red circles or arrows you add in your chosen editing software will do more to convey a point than writing a paragraph on how to get to the right menu.

  • Love the example here!

    I'm still learning about available references (ex config.services.navidrome.settings.Port). What resources did you find to be the best for learning that kind of thing?

    I'll accept RTFM if that's applicable :)

  • Hm.. if I'm reading the README correctly this is a LAN only drop mechanism between a phone and a laptop. Syncthing does that already, albeit with a cumbersome number of features and config for that use case. If that's not accurate I'm sure you'll let me know :)

    I would love to see this develop an airdrop-esque Bluetooth / PAN phone to phone feature though! Especially if a compatible iOS app were available that would be really slick.

  • Is there a reason you're not considering running this in a VM?

    I could see a case where you go for a native install on a virtual machine, attach a virtual disk to isolate your library from the rest of the filesystem, and then move that around (or just straight up mount that directory in the container) as needed.

    That way you can back up your library separately from your JF server implementation and go hog wild.

  • Syntax-wise, it's meant to be identical. I got on board when they were the only ones that enabled rootless (without admin privileges) mode. That's no longer the case since rootless docker has been out for a while.

    I'm personally a fan of the red hat docs and how-to's on podman over the mixed bag of tech bro medium articles I associate with docker.

    At the end of the day this is a bit of a Pokemon starter question. If your top priority is to get a reasonably common and straightforward job done just pick one and see where it takes you! :)

  • Syncthing is my answer though I appreciate it doesn't get to the root of your question.

    There are local backups that include your system settings, text messages, contacts, call history and (optionally) apps. The one thing I want is the ability to pick a directory for the local backup so I can make it work with syncthing without jumping through hoops.

    It's also compatible with Nextcloud and WebDAV if those are options for you.

  • Chiming in to note that GNSS communications are actually receive only. A typical phone can't physically broadcast a strong enough signal into mid-earth orbit (where most of those satellites typically are) to achieve the "pinging GPS satellites" issue.

    Note this only refers to how that signal physically hits your phone. Once your position is deduced and digitized there's an entirely different attack surface.

    The other concerns (especially cell tower data tracking) are valid though.