What is the implications / meaning of that? If a software comes from a trusted source and there's adequate mechanisms to make sure file contents aren't stolen / accessed -- why be concerned with who else has the same software?
From the general user's point-of-view: Using OnlyOffice's paid products may be problematic because of sanctions against Russia.
From a contributor point-of-view: If I voluntarily contributed to OnlyOffice, I would be unhappy that the company sold my AGPL-licensed code and attempted to hide the fact. Granted, they probably require contributors to sign a CLA, so as to make this legal. And yes, it is also unclear if P7 was a single-time fork of OnlyOffice, or if it continually takes code from OnlyOffice.
From a random Russian person's point of view, it would be very unfair to learn that the (ostensibly Russian) software you have bought (because P7 appears to be solely commercial, not freemium, but correct me if I'm wrong) is in fact open-source and gratis in the West.
Also, in the construction industry you get an updated drawing file a day before the bidding closes... good luck getting the GC to send more detailed files (that they themselves got elsewhere) in that time. You're better off sending it to your estimation department in India and letting them work through the night to put together the new estimations.
Happy to say that yes. We are in final round of polishing. mostly opening in couple of weeks. We are mainly targeting such uses cases where you can add CAD files into RAG or analytics or search pipeline without losing source of truth or geometry. I will definitely post here when we are ready, keep an eye and it will be free during beta, so you can play how much you want with it.
I think given the scale of projects worked on / being estimated (8 to 9 figure projects) -- it's unlikely we'd be willing to test on our real CAD files. Any chance for enterprise hosted solutions that aren't on the cloud?
That is the catch, yes on premise air gapped will be provided, this is purely inbuilt parsers no cloud dependency. We will also have a managed dedicated environment, if you don't want to manage the complex infra yourself. Even in Hosted model, we have provision to use your own s3 storage (only used for async parsing pipeline and file will be wiped after 3 hours)so file never touches our disc. We had considered this from a customer point of view and while designing the system. In my early career i had worked in GIS industry and know the privacy and the data security that is required for CAD and GIS files.
I had several roommates, and we each were responsible for a utility. I was responsible for internet, and Cox was our provider.
I received multiple e-mails from Cox about copyright infringement. I can't recall them, but I remember it being serious enough for me to tell people to stop.
Thinking back, I feel like Cox's position is right and fair; let users know they're being observed by copyright holders, and inform the user that they could be compelled to provide their identity to complainants.
But ultimately, the responsibility to "stop" the supposed infringement is on the holder, not Cox.
One very minor note; Anthropic and others, like most "enterprise" solution, also sell SSO + SCIM + audit logs. Their business plans have lower tokens and higher prices to cover the enterprise features, which should be essentially free to provide in 2026.
I think people will be quick to engage with the "ai is risky" angle, but the thing that jumps out to me is that you were working against a production state in the first place.
The agent made a mistake that plenty of humans have made. A separate staging environment on real infrastructure goes a long way. Test and document your command sequence / rollout plan there before running it against production. Especially for any project with meaningful data or users.
Yeah, even without the AI in the loop, testing a major migration in production is madness. With AI (or a freshly-minted intern) in the loop, it's complete insanity.
Test against staging, produce a script, make the most experienced human review and execute said script against production.
a redis geospatial index + redis distribution locks you can build a performant cache layer that is consumed by a ton of people and stay well under that rate limit.... the weather data only updates every 5 minutes too, so you can use that for your cache ttl.
