8,360 karma · joined March 21, 2014
goisser94@gmail.com
https://hobofan.com
Mastodon: @hobofan@toot.berlin (Twitter: @hobofan)
---
Currently building https://github.com/EratoLab/erato
Since you wrote your comment the official blog posts describing what exactly is the in the exploit have been released, and "shut it all down" was definitely the right advice to give.
Try to distribute a program without an embedded CA bundle to any number of users, and after a week you will surrender due to the bug reports you receive because users are running 5+ year old system CA bundles, which are not sufficient for connecting to some of the most popular API endpoints out there.
Obviously, hosting a search index locally would be best practice, for the search part, but usually comes with quite a significant hardware cost and operational complexity, if you want to have an up-to-date index. I'm not aware of good self-hostable options in the space but would be happy to hear about them if anyone here has experience with that! AFAIK LinkUp and some other provides do offer private cloud/on-premise deployments, but I think mostly for their biggest customers.
For the web fetch/access part of the equation, that is inherently live and not containable for a local deployment (unless you would host a whole internet archive/Wayback Machine, which is even more of an undertaking). There, the main options you have to prevent leaks, are a domain allowlist (if feasible), doing query parameter stripping (error prone, and still no 100% guarantee), or configuring the client (e.g. our tool) in a way that users have to explicitly allow those tool calls, and are informed about the posed risks. We are also working on a system, where certain tools are fully deactivated once e.g. an office document that's marked as confidential enters the context.
For the highest requirements on company secrets, an air-gapped system that doesn't have web search/access capabilities is obviously the ultimate solution.
That is rarely the case (see sibling comment for reasons). Even open source harnesses will usually guide you to connect a hosted provider for that.
Especially for chat-like use-cases (in contrast to coding), latency is a lot more critical, especially if you kick off a small single query question. On antother axis, scrape-reliabilty is important for a deep research job that will fire ~10+ web searches and ~100+ web fetches.
e.g. in our chat platform[0], we offer first party MCP servers for web search[1] and web access[2] which work decently well, but some of our customers that prioritize quality over cost, they go with dedicated providers like LinkUp[3]
[0]: https://github.com/EratoLab/erato
[1]: https://github.com/EratoLab/web-search-mcp
- You use Azure DevOps for SCM
- On macOS, I regularly (~once a week) end up in different broken sync states, where message histories for all chats are missing messages from the last few month. The only way to reliably fix this is to remove the whole cache, causing it to resync after a app restart. Due to this, I run a whole Windows VPS, just to be able to "reliably" receive Teams messages from customers.
- In multi-tenant usage, it's incredibly slow to switch between different tenants. If you are semi-actively chatting with users from 2-3 tenants its a big PITA
- If you are an external user to a organization, the default settings are that your Teams session will last ~24h, after which you have to re-authenticate. Teams doesn't give you any good indication that you have been logged out, unless you actively check, in which case you might be shown a warning banner after ~a minute delay (if you are lucky).
---
I'm usually one the more defensive side of cargo cult hate against software (e.g. I think a lot of people dislike JIRA to an unjustified degree, and mostly due to badly hosted or configured instances), but Teams is one of the few where it's absolutely deserved. I think it's a prime example of how Microsoft as an organization has forgotten how to build good desktop software.
Only upside is that it's a good bonding ritual with customers, as the Teams suffering is a universal feeling.
> citation
Nope, as long as the MCP server exposes enough metadata to be cited (mostly trivial), citation is a job of the client/LLM.
> trust
Also just a function of the client. The server can't aid here at all as it's inherently untrustworthy in the system.
> measurement
Maybe. Though it's debatable how much measurement _each_ server needs, and whether that actually gives meaningful insight to optimize. This might as well be measured outside of the servers, in the client/a centralized logging system that also sees surrounding context.
So you have two main modes of operations: One-shot "I have this input; give me this output" which people usually do via the web-app, and more interactive editing to documents (usually larger ones) that happens directly in the applications the users are already working in.
And yeah, that's what ultimately gets the job done. We've seen competing solutions dive much deeper into building their own native editors, but they always lack the fidelity required by power-users, and are usually not as acepted by the broader workforce that are entrenched in their ways (our typical end-user is 50+ in a enterprise-like organization structure), so we try to meet the organisations where they are.
Source: Building a "harness" for organizations with deep MS Office suite integration at https://github.com/EratoLab/erato
Even as a big Deno "hater" due to their anti-package manager stance on the basis of URLs that leads to a sleuth of dependency attacks, I must say that Deno and the people behind it have undoubtedly pushed the space forward on many aspects!
2. Even if it is non-FBA it should be in the interest of Amazon to have stronger enforcement for non-FBA sellers that are consistently lying about their delivery dates in order to get a sale. That should be pretty easy to track. In the past the variance of delivery dates hasn't been that bad, even for non-FBA sellers.
Out of the last ~20 orders (I don't order that often from them, so that's probably spanning the whole last 12 months or more), more often than not, the predicted delivery date has been adjusted upwards, often by ~2 days, and a few times by ~a week.
This may be specific to Germany/Berlin, as from what I hear, they (/ their subcontractors) have troubles finding delivery drivers. Mixed with the growing counterfeit issues, and degrading product description / details for most products, Amazon doesn't seem to be in it's prime.
I'm not familiar with the concrete wording of the regulation, but I would wager that the all the customization layers (like "One UI") that OEMs put on top of AOSP is the component for which the update clock should tick, and they should be unaffected of an underlying open source component (AOSP) being released.
As it stands right now, it proofs little more than it can replicate the post-boot screen of the original products.
Just because every tech news outlet was dumb enough to report it without trying it doesn't mean you have to join the echo chamber.
---
There are definitely examples out there that do use a similar relentlessly agentic development style that have produced great results. e.g. xberg[0] (formerly kreuzberg), is a great document content extractor, and in a relatively short amount of time has become one of the most robust and performant. I've reported about a dozen edge cases of documents of various types that were unextractable, and the maintainer (or their agents) were able to add a fix in maximum a day turnaround every time.
Just because some guy on some forum said that doesn't make it true. That's not how you establish facts regarding health claims.
e.g. this one puts multi-platform support as a high requirement, a requirement that OpenShell doesn't fulfil (and likely won't given it's architecture/goals).
Additionally, "the algorithm" rewards channels that have a lot of watchtime & retention (because againg, this leads to more ad placement opportunities for Youtube). So if you are able to produce long-form videos that keep the viewers engaged and watching, your videos are more likely to be recommended, which reinforces the popularity of long videos.
Most complexity that usually plagues authorization systems comes from complex authentication requirements, and can thus be largely isolated there. That's also where many (often legacy systems) lay a bad foundation, because they from the get-go tangle authentication & authorization into thing.
In a model as described above, that just turns into a slightly different `actor`. With that you can also handle things like context-aware authorization without littering your codebase.
Yes, but only very coarsly granular things.
- Permissions only work with entities. There are about ten different kinds of objects besides entities, that would also benefit a lot from being part of a uniform permission system.
- Permissions can only be defined for groups, not users, which is quite annoying if you want granular permissions
- With permissions only acting on groups, it also isn't possible to base permissions on user attributes. So you ultimately always have to model a permission set as a group, and then essentially have to have a synchronization mechanism that ensures that the right people are in the right groups
- This also makes scoped integration access impossible. You can't grant a third party app access to e.g. only your energy sensor data.
These days if you build it with a central policy engine, e.g. on top of Open Policy Agent with Rego as a policy language, and stick to a (actor, object, action) triple system, you can build an extensible and powerful authorization system that usually also is less polluting to the codebase as many other approaches. For HA specifically, where you have a quite low numbers of actors and objects, most of the headaches that could come with such a system in terms of scaling also fall away.
I do think the maintainers are getting better about it. The releases over the past year have reworked a lot of things to be more intuitive for casual users while also being more flexible for power users, but there is still a lot of ground left to cover.
I think with the growing popularity, and expansion of fields of use, this is something they'll ultimately have to reckon with. I've seen quite a few posts on the the HA subreddit, where it's being used for controls in e.g. hotels or other bigger buildings, because it has a great feature set and prevents vendor lock-in. There is no harm in also catering to those people & organizations.