saghul
If someone is committed enough to help out but using Matrix (either directly from the web browser or installing the Element client) is too big a burden I'd question that original commitment.
PS: I'm not affiliated with Matrix in any way.
While it being a very large file, it's sorted somewhat semantically, so it's easy to work on adding a new iterator method, for example, since they are all close to each other.
Thankfully, lima has landed a new port forwarder with UDP support! [0]. I'm hoping to be able to use it soon once it makes into a release.
[0]: https://github.com/lima-vm/lima/commit/13e9cbcabc6a0a05ec389...
According to the docs it only uses that if the model doesn't begin tieh gpt- and uses an old API, so alas it doesn't seem compatible with ollama.
Edit: here is the relevant part of the code: https://github.com/gnachman/iTerm2/blob/a196d31658a8d0aa2dc5...
Looks like adding ollama support is really a matter of changing a few lines of code.
Edit 2: Seems to be fixed in the next beta release: https://github.com/gnachman/iTerm2/commit/fcd212490626f1d8ea...
So what are you up to now? (if you can share, that is!) :-)
Since the room won’t start without users, the first one will need to log-in or wait for someone else to do so.
We’ll keep moving forward making (hopefully) the best open source meetings tool out there.
To answer a few recurring questions:
- Only the first user needs to be authenticated
- This change does not affect the self-hosted deployments, you can choose what auth (or none at all) to use
Many think they can go P2P, but browsers implement one bandwidth estimator per PeerConnection, so that begins to hurt quickly in practice.
In addition, sending multiple HD streams to serveal participants it's going to hurt the sender, but an SFU helps with that.
There are many more reasons, this is just scratching the surface.
Fun fact about the Flutter SDK: it's a wrapper over our native SDKs, which themselves wrap our React Native codebase :-)
Right now we have a shared codebase between web and react-native, and from there are able to provide all our mobile SDKs:
- Native Android SDK (Java wrapper for RN) - Native iOS SDK (ObjC wrapper for RN) - React Native SDK (JS component of the RN parts) - Flutter SDK (Kotlin / Swift wrapper of the Java / ObjC SDKs)
It has been quite fun to work on these!
I'm using the Joplin sync server for keeping my stuff in sync and it has worked flawlessly.
If Laurent or anyone from the Joplin community is reading: great job everyone! <3
He had gotten some new heavy machine, some 400 pound stuff, that he needed to put down in the basement.
He had no idea how he'd get it down the stairs, but he started pushing it closer, since that got the problem closer to a solution. He'd figure the stairs later, once the machine was on the edge.
It's simple, but I found it insightful.
When I'm faced with a problem and am not sure how to solve it or if it's actually solvable, I think of how a solution would look like and start making small steps in that direction, hoping to get elucidated later on :-)
If you’d like to dig into it, please reach out to us on GH or to me at [email protected]