Hacker Newsnew | past | comments | ask | show | jobs | submit | danpetrov's commentslogin

Sadly completely unusuable for our usecase - if you are targeting Enterprise, you should know better than to use OpenAI models as the only LLM available.

For now I will stick to PrivateGPT and LocalGPT.


Completely unusable for internal docs* should be the caveat. For external doc OpenAI is fine unless you have stuff behind a password.


You may be in a situation where the document is public but the question is confidential, i.e. a user having specific question about an agreement with public TOS that a legal or medical department is managing.


At the very least, I'd start with adding support for the Azure flavor of OpenAI API. It's literally the same models, but the difference is that it's your company deploying those models on Azure, under proper enterprise contract with Microsoft, literally so that they can be safely used with proprietary data.


Yea, that's good feedback - we've gotten requests for open source model support from a lot from people we've talked about. It's one of our highest priorities, and should be available soon!


Are you about to use GPT4ALL[^1] or anything else? If you're going with the second option, then please share any link to such resources... I'd be interested.

And, to share with you something: I saw somewhere a tool (maybe it was GPT4ALL itself) that had the ability to expose a OpenAI-compatible local API on localhost:8080... Ah, yes. Here it is. Actually, there are two. They are described as possible backends for Bavarder (that's a free access to multiple online models, API key is not required): https://bavarder.codeberg.page/help/local/

[^1]: https://github.com/nomic-ai/gpt4all/blob/main/gpt4all-backen...


Nice! Although the naming could be a bit better, because I cannot be the only one who thought that this has to do with https://matrix.org


Telegram is great if you like shiny native features like stickers and having lightweight native clients, but at everything else Telegram is at risk of losing in the long-term.

The big reason for this is that Telegram decided to roll everything mostly on their own (including e.g. MTProto), Telegram is not compatible with Matrix unless you use a bridge, it is not e2e encrypted (unless you use mobile 1-to-1 secret chats. The server side code is proprietary, and the builds of the clients that are published to the app stores could be anything.

While I love using Telegram right now for talking to some groups of friends, I would look at supporting https://matrix.org , since it will likely become the de-facto standard of building messaging platforms.


>Telegram is great if you like shiny native features like stickers and having lightweight native clients, but at everything else Telegram is at risk of losing in the long-term.

Whatever ends up winning is going to need:

  - Native clients on all major platforms
  - Full support for all the fun little extra's like emoji's, reactions, gifs, file transfers etc.
  - True multi-device support that doesn't require any sort of forwarding from another device
  - Group chats
  - Searchable history
  - Your full history to automatically load when you log in on a new device (manually transferring isn't going to be an acceptable solution)
  - No concept of selecting a server or anything. Users need to be able to just log in with a username/password and carry on. 
  - E2E encryption that doesn't sacrifice the user experience
Anything missing from this list? Also, does Matrix support all of that? Last time I checked Matrix out it seemed clunky and confusing (especially for non-technical users) and it was missing a ton of the 'basics' that people expect out of a chat app.


I think I can speak to how Matrix deviates from your list:

- There are technically native clients on every platform, so best kind of correct? However, the "official/main/most popular" client is Electron on Desktop. Partial credit?

- Yup

- Yup, even when using E2E, which is a hell of an accomplishment. You transfer keys from other devices, but not entire messages.

- Yup. E2E or not, your choice.

- Searchable history plus E2E is... hard, to say the least. Some clients will index your conversations while they happen, but that's obviously not the perfect solution. That said, the APIs are so open that I've written python scripts before that download and search entire rooms. It would be possible for a client to do the same, though I don't think any do. Non-encrypted rooms are trivial to search, or course.

- This as well. As before, keys transfer from other devices, messages load from the server.

- This seems like it was engineered to exclude Matrix. The default in every client is matrix.org, and there's no reason you ever need to change it if you're not concerned with it. In fact, most clients make it a couple clicks to change it (https://app.element.io/#/login).

- Not totally sure this is possible, but Matrix comes very close. On par with Signal, though with different tradeoffs (stored history, for example).


- The native clients for Matrix suck. Even the mobile clients for Matrix are full of bugs.

- No custom emojis; every chat application known to man has regular emojis supported in UTF-8, so the author must be talking about custom ones. Which Matrix still does not have: https://github.com/matrix-org/matrix-doc/pull/1951

- I don't think doing what PGP does is really impressive, but okay, fine, one point.

- Matrix group chats are broken and this is why Synapse eats resources like a bear.

- No searchable history on all but one Electron client on one platform when using E2E is terrible, and further supports the argument that all clients suck.

- Point; this is pretty convenient.

- XMPP sucks. Matrix is modern XMPP. People don't like getting confused with servers and similar nonsense, and when your homeserver goes down, you're out of luck. Federation sucks. The question wasn't made to exclude Matrix, it was made to point out that federation sucks. Matrix didn't invent federation; it chose it long after it failed.

- E2E degrades experience greatly. To list my two biggest complaints: It ruins search for all but one client, and the UX around keys is terrible. I frequently have conversations with incredibly technical people and they'll still get absolutely stumped by the UX around keys, because it's awful.

Two out of eight isn't bad.

I use Matrix every day. I have for years; long before the recent rebrand, and multiple presidents have vacated office since I started using Matrix. I love Matrix. But there's no reason to act like it's some golden goose when there are problems from 2015 that are no closer to being fixed than they were at the time. It's a comfortable protocol for usage by people who have powerful computers. For everyone else, it still isn't great.


> - I don't think doing what PGP does is really impressive, but okay, fine, one point.

it's more than PGP, it includes variable PFS, automatic key exchanges

> - Matrix group chats are broken and this is why Synapse eats resources like a bear.

I have heard it's because Synapse is a proof of concept that went into production

> Federation sucks. The question wasn't made to exclude Matrix, it was made to point out that federation sucks. Matrix didn't invent federation; it chose it long after it failed.

I disagree. Federation is a burden, but it enables interoperability between independent parties.

> But there's no reason to act like it's some golden goose when there are problems from 2015 that are no closer to being fixed than they were at the time.

There's also no reason to do the same thing into the other direction.


I also heard that Matrix will run off with your wife and kick your dog. It's a re-implementation of BoziBuddy, and will fail for the same reasons.


Signal seems to have everything you listed except for the full history transferring to a new device (works on Android but not as well with iOS). Though like you implied, it is done manually. I'm still not convinced that this can be done without making major sacrifices to security because I really do want a trustless system where my messages aren't stored on a company's servers (I am okay with optional backups though, so there's a middleground).

> No concept of selecting a server or anything.

This has been one of the big concepts that has bugged me with Matrix. It also is why I'm confused with why people pit Matrix vs Signal. Honestly I see Signal/WhatsApp/iMessage/WeChat as competitors whereas Matrix/Slack/Teams/IRC is a different ecosystem. But I can't get my parents or grandma to use something like Matrix (or even Slack) but they are able to use things in the former category. In fact, this has been one of the great successes of WhatsApp (looking at India with all the aunties and uncles using WA or China with WeChat).

> Anything missing from this list?

- Pinned messaging

- Other class of extras/plugins: on-device translation, calendar reminders, etc

Pinning messages is important for search, but seems to be overlooked frequently (I use this a lot in slack). I often know something is important and need to find it again in a day or two (e.g. traveling) but will also be talking with the other person and that message gets pushed. Pinning lightens the load of searching. It also lightens the load of backups as most people truly want a very small subset of their messages saved but are only aware of an all or nothing approach.

Plugins will be important as well. To complement pinning calendar reminders are great. Google does stuff like this frequently like when you get an email about a flight and then your phone's home screen will have all the information on it. It's also naive to think that you can think of all the things people would want. That's why smartphones have been so successful, because they provide the ecosystem. This isn't too dissimilar from creating a super app. But there's none where the ecosystem is fully secure.


> Signal/WhatsApp/iMessage/WeChat as competitors whereas Matrix/Slack/Teams/IRC is a different ecosystem. But I can't get my parents or grandma to use something like Matrix

I can't get why people need to put Matrix in either Box. It's a communication protocol. Client UX is completely independent, like you can have K9Mail and Thunderbird


Signal desktop clients are not native. They use Electron and are much slower than Telegram.


That's true. Something I wish they would fix but I think now it is tech debt.


- An option to not have a password at all and log in just by having a phone.

It's a 100% must have feature for a phone IM, most people will forget a password the very moment they are forced to create it.


I agree that it's a great option, but unfortunately it's also not secure at all. You're what, one SIM swap away from having your whole chat history owned?


> Your full history to automatically load when you log in on a new device

Most people don't actually need full history in most situations, just recent history.


If you can do recent history, you can probably do the full history.

I personally search my deep history regularly. I might be looking for a recipe, link, someones contact information, an address... There are many reasons having the full history available is important, and "losing" it by getting a new device is a terrible user experience.


Telegram the app, is the best among all messenger apps.

Telegram the company, maybe not.


It is best because they don't bother encrypting user data, loading it directly from its own servers.


I meant feature-wise, the app is spectacular, but security-wise, it's not that trustworthy.


Exactly. Features are way easier with everything plain text.


Matrix still has ways to go but Elemental is now actually usable.

On the Telegram security side of things my group of friends uses it as a more modern IRC. So no NSA proof security is truly even expected. We even bridge some IRC channels to Telegram with bots.


> and the builds of the clients that are published to the app stores could be anything.

Isn't Telegram one of very few that provides verifiable builds, (including on iOS if you root it)?

I might be wrong but I think not.

Edit, see : https://core.telegram.org/reproducible-builds

So it seems even on this point Telegram shines.


Telegram doesn’t even post their source code to match their releases on macOS and iOS. Sometimes they’ll do a code dump somewhere around that time, but it’s not a guarantee.


In the same boat as Signal there.

WhatsApp doesn't post source code at all.


Wow that is really cool!


Emacs Lisp is totally usable as a minimal scripting language outside of the regular Emacs context.

You can compile Emacs without any GUI toolkit support and run it heedlessly as a lisp interpreter. You can even make Emacs packages behave like CLIs with a few lines of code.


of course. emacs itself is written in emacs lisp. it's not just an extension script for it. but it is not the most performant language. depending on the implementation, common lisp can be a beast with unmatched interactive development (in emacs of course)


That's the thing, ideally you would perform a test for every single service that you use directly to their network.

In my previous company where we were doing live broadcast, we would have speed testers pre-installed on all the hub and edge servers, so we could get realistic numbers for a specific use case (for example, requesting. a video stream from Germany).


Huh interesting, works fine on my 2018 Intel MBP. Surprising to see a bug like this on the newest models.


I doubt its a bug in a particular model. I'm on an M1 Max and the tool works without issues.

I am guessing its an bug in the tool itself that the user ran into.


Works on my M1 Air.


There is also "networksetup", which allows you to do pretty much anything you want with network configuration. Useful if you want to e.g. automate VPN network switching or locations.


> Useful if you want to e.g. automate VPN network switching or locations

Can you elaborate on that a bit, please?


If you have a VPN named "MyVPN" you can start it from the command line with: networksetup -connectpppoeservice "MyVPN".


I use this as part of an ssh ProxyCommand. It's wonderful.


Oh no. Oh no oh no.

You don't mean Apple's implemented the Wi-Fi autoconfig functionality Ubuntu failed to deliver in ~2008, do you?

Because if they have... they'll have done it... correctly.

If the binary and/or supporting libraries have any references to FieldAgents in them... we're doomed. That's Skynet, right there.


Can you expand a bit? Some quick Googling didn't reveal anything useful to me -- what exactly are you talking about?


Sure, and apologies (I think my comment went up to 2 points but now at 0, hehe).

It's a reference to https://xkcd.com/416/.

:P


I have been studying programming since my early childhood years, because apparently I had decent logic skills and parents in the city would sign up kids for this private math and programming evening school.

Later though I originally picked to pursue an aerospace engineering degree and was working as a live dealer at a live casino company while studying, but the same company also had a large engineering department, and it was very tempting. So I went back to my roots, started out as a manual tester to get the foot in the door, and later slowly transitioned to automation QA and then to a backend developer. Now I switched universities and am doing a Bachelor's in Computer Science, mostly for fun and to fill in any knowledge gaps.

Really the new company didn't care about a degree, and I honestly learned way more from independent study and my work than I did at university so far. Blogs, conference talks and books are really what helped me a ton. While the new job is quite difficult, my colleagues are great, and we take very relaxing breaks and do lots of activities outside of work. Knowing that my work impacts millions of people around the world is quite inspiring.


The Elixir core team has been knocking it out of the park recently with features that developers actually care about, especially the developer experience like the IEx shell and error reporting. These things might not impact existing projects much per se, but this is a huge deal when new developers are learning the language and the ecosystem.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: