chhs

https://docs.bazzite.gg/Installing_and_Managing_Software/Baz...

It's designed to integrate with Maven projects, to bring in the benefits of tools like Gradle and Bazel, where local and remote builds and tests share the same cache, and builds and tests are distributed over many machines. Cache hits greatly speed up large project builds, while also making it more reliable, since you're not potentially getting flaky test failures in your otherwise identical builds.

https://jrecc.net

It's designed to integrate with Maven projects, to bring in the benefits of tools like Gradle and Bazel, where local and remote builds and tests share the same cache, and builds and tests are distributed over many machines. Cache hits greatly speed up large project builds, while also making it more reliable, since you're not potentially getting flaky test failures in your otherwise identical builds.

https://jrecc.net

It's designed to integrate with Maven projects, to bring in the benefits of tools like Gradle and Bazel, where local and remote builds and tests share the same cache, and builds and tests are distributed over many machines. Cache hits greatly speed up large project builds, while also making it more reliable, since you're not potentially getting flaky test failures in your otherwise identical builds.

https://jrecc.net/

There is also Troi[1], a tool provided by ListenBrainz to generate playlists and radios from your local music collection.

[1] https://troi.readthedocs.io/en/latest/index.html

[1] https://github.com/kgarner7/navidrome-listenbrainz-daily-pla...

[2] https://troi.readthedocs.io/en/latest/

https://github.com/chhs1/content-seeder

I think a better solution would be some way for clients to query the DHT for a specific "pieces root", but I don't know if all clients publishing "pieces root" for the torrents they know about would also be a good idea. Some kind of distributed metadata database where clients can query would be ideal.

I built it with libtorrent and after loading in all of the torrents (multiple TBs of data), it would promptly and routinely crashed. I couldn't find the cause of the error, it doesn't seem it was designed to run with thousands of torrents.

One problem that I've yet to build a solution for is finding the metadata to use for the lookup phase. I haven't been able to find a publicly available database of torrent metadata. If you have an info hash then itorrents.org will give you the metadata, if it exists. I started scraping metadata via DHT announcements, but it's not exactly fast, and each client would have to do this unless they can share the database of metadata between them (I have an idea on how to accomplish this via BEP 46).

But there's no way for other clients to know that there exists another torrent containing the file they are interested in if they only have the metadata for torrent A. In other words, there's no lookup mechanism for a "pieces root" to know that torrent B exists and contains file C.

If you were to make a v2 torrent of your entire drive, other clients won't know to download from your torrent. They'd need to have the contents of the metadata to know it would contain a file they are interested in, and have no way of knowing which metadata contains the desired "pieces root" entries without downloading all of them.

I'm very interested in this problem space, if you are aware of clients/mechanisms that allow for this I would love to hear them.

A recurring problem I've noticed in companies with large, legacy codebases is upgrading dependencies. Typically these projects have been around for a long time, no one currently working on them understands the project deeply, and test coverage is quite low. The result is that developers cannot rely on a successful CI/CD result to know if an upgrade didn't break the project. They instead resort to a lot of manual searching and testing to verify that everything is still working.

I built Dutest to easily identify where dependencies are used within a project, and what the level of test coverage is like, broken down by the test type (unit, integration, or end-to-end). This allows me to quickly triage whether an upgrade can be done quickly and safely (high test coverage + low number of usages), or if it is more risky (low test coverage + high usages). It also provides references to quickly jump to that line of code within an IDE.

I thought I'd build this as my first solo SaaS product, and see if this solves a problem that others are experiencing. I'm happy to hear your feedback and to answer any questions.

> According to Kirsty Gogan, cofounder of TerraPraxis and a senior climate and energy advisor to the U.K. government, “All three Green Zone applications by nuclear groups were rejected.” However, it seems some of that may be due to miscommunication regarding application deadlines for the COP26 Green Zone.

I couldn't find the original source for the miscommunication on application deadlines, hopefully someone can find it.

[1] https://www.ans.org/news/article-3188/controversy-over-nucle...

There's currently no way to horizontally scale an instance, so after an instance grows past a certain size it can't transcode uploaded videos fast enough. I love the project but if it can't utilize multiple compute instances to transcode video (or plug into a cloud platforms video transcoding offering), it's never going to grow past this blocker.

  Location: Australia/New Zealand
  Remote: Yes
  Willing to relocate: No
  Technologies: Java, Spring Boot, Maven, PostgreSQL, Terraform, Docker, AWS, Git, Bash, D
  Résumé/CV: Available upon request
  Email: [email protected]