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

There is no way it’s going to be completely rewritten from scratch in Go, and none of whatever Germany is or isn’t doing affects that in any way shape or form.


Actually, it's already been done by the former Nextcloud fork/predecessor. OwnCloud shared a big percentage of the Nextcloud codebase, but they decided to rewrite everything under the name OCIS (OwnCloud Infinite Scale) a couple of years ago. Recently, OwnCloud got acquired by Kiteworks and it seemed like they got in a fight with most of the staff. So big parts of the team left to start "OpenCloud", which is a fork of OCIS and is now a great competitor to Nextcloud. It's much more stable and uses less resources, but it also does a lot less than Nextcloud (namely only File sharing so far. No Apps, no Groupware.)

https://github.com/opencloud-eu


Thanks for sharing this, I've been wanting to look at private cloud stuff but it was all written in PHP. It looks like OpenCloud is majority Go with some php and gherkin, which is a step in the right direction.


I have OpenCloud working on my home server, and it features integration with the Collabora suite of software for office apps. Draw.io is also already supported.


They offer a Docker compose file that sets up Collabora for you, but I can't find anything info on other apps, let alone integration. Where can I see what they support?


You're right, it was my mistake. The docker compose file can set up Collabora for you and allows you to open documents from inside OpenCloud by opening the file in an embedded Collabora view. Likewise, Draw.io works in a similar fashion, opening a view to embed.diagrams.net. Underneath it's just hosting the files and offloads the operations to other apps. It's convenient, but not particularly sophisticated.


There are no "Apps". It's not a universal App platform like Nextcloud. It's just file sharing (and optionally a Radicale calender server via Environment Variable but without UI). There's optional plugins to open vendor specific files right in the browser.


OCIS does only a small part of why people deploy NextCloud. I have run it, it’s great, but it’s not a replacement for the full suite nor is it trying to be.


Looking at the product itself, it looks like it barely squeezes the mini-HDMI externally as is, let alone then PCB/internal available space.

I don't think there is, in fact, room for a full HDMI port. Mini HDMI is a compromise, and everyone knows it. It wouldn't have been included if full size HDMI was feasible.


The formfactor is self-imposed though, they could have made the device a few mm wider to accommodate a full HDMI port, but then it wouldn't be nice and square. Form over function maybe.


The form factor is based on the Apple Watch screen they use, clearly.


Mini-HDMI is fine for this use though and can just move with the item so it's not like you need to buy many.


That’s what I do, the jetkvm has its “own” mini hdmi that follows it as I have moved it from different machines. Buying one cable wasn’t the end of the world (I was able to snag the jetkvm for $70 during its kickstarter and a $10 cord) and I use it constantly so it’s never collecting dust


Pretty sure Bazzite offers all those things as well.


It does. It provides everything SteamOS does. So if SteamOS doesn't support the Xbox Ally X, why install SteamOS?


I get respecting the family while grieving but let’s be real here, is anyone from the family realistically going to even find let alone care about random strangers speculating on a random internet platform that isn’t even related to chess?

The chance of this even reaching them is infinitesimally small. We’re not standing around talking about it with them in the room, we shouldn’t be pretending like we are.


Its definitely normal to wonder "what happened?"


Even if not, we're all better off if we behave with respect and humanity.


This just feels like gatekeeping discussion at this point.


The concern is more about speculation specifically. Internet armchair-investigations regularly get out of control and fills discussion with what reliably later turns out to be misinformation, in addition to being disrespectful at sensitive time.

Low quality blogs and "news" reporters also directly pull from online discussions, and before you know it, hypothetical drug use is a major discussion point, which is unfortunate.


I have seen people that I would have never expected to have heard about HN, show up here. The odds that someone tells the family to come look may not be that high. But they are very far from zero.

Most other internet forums that I've been on I would not say this about.


Did you bother to even look at the tutorial on their website? You know, the one mentioned in the comment you replied to?

https://massgrave.dev/manual_hwid_activation / https://massgrave.dev/manual_ohook_activation / https://massgrave.dev/manual_kms38_activation

Most of those 19861 lines allow it to be an all in one script for multiple activation methods and products. And, if you're still skeptical, then you are free to audit all 19861 lines yourself.

Maybe at the very least educate yourself before acting so smug.


What circular logic is this?

Other poster writes that code is not auditable since it is not 5 lines, but 20 000 lines and you tell them to audit it?


Why would I look at the tutorial for a no script activation when I was, you know, commenting on a point about a script? Did to you forget to educate yourself to notice the difference?

> And, if you're still skeptical, then you are free to audit all 19861 lines yourself.

That's nonsense, of course, how would it help other users? Also, do you expect every single user of the crack to have the capabilities and time to do that?


I highly recommend people take a high performance/race driving course if they can. I did a single day one which involved high speed maneuverability trials designed to be useful in emergency scenarios (swerving, braking, hard turns) followed by a few laps around a racetrack.

It's one of the best ways to figure out what it feels like to drive at the limits of your car and how you and it react in a very safe and controlled environment.


Those 999 other times, the system might work fine for the first 60 miles.

This is a cross-country trip. LA to New York is 2776 miles without charging. It crashed the first time in the first 2% of the journey. And not a small intervention or accident either.

How you could possibly see this as anything other than FSD being a total failure is beyond me.


>asking a different question: how good would the FSD system be at completing a coast-to-coast trip?

>They made it about 2.5% of the planned trip on Tesla FSD v13.9 before crashing the vehicle.

This really does need to be considered preliminary data based on only one trial.

And so far that's 2.5% as good as you would need to make it one way, one time.

Or 1.25% as good as you need to make it there & back.

People will just have to wait and see how it goes if they do anything to try and bring the average up.

That's about 100:1 odds against getting there & back.

One time.

Don't think I would want to be the second one to try it.

If somebody does take the risk and makes it without any human assistance though, maybe they (or the car) deserve a ticker-tape parade when they get there like Chas Lindbergh :)


> This really does need to be considered preliminary data based on only one trial.

Statistically yes, but look at the actual facts of the case.

A large object on the road, not moving, perfect visibility. And the Tesla drives straight into it.

Not hitting static objects in perfect visibility is pretty much baseline requirement #1 of self driving. And Tesla fails to meet even this.


It does look like lower performance than a first-time driving student.

I really couldn't justify 1000:1 with such "sparse" data, but I do get the idea that these are some non-linear probabilities of making it back in one piece.

It seems like it could easily be 1,000,000:1 and the data would look no different at this point.


> and we should not tolerate self-driving systems that are as good as the worst of us

The person you replied to didn't do that, though:

> But a self-driving system worth its salt should always be alert, scanning the road ahead, able to identify dangerous debris, and react accordingly. So, different pair of shoes...


They never said they did.


I mean, those were direct quotes and it was literally half of their comment, but, sure, "they never said they did".


I think they meant the person you were responding to never claimed that the person they were responding to said that we should tolerate self driving systems that are no better than the worse of us, not that the person that the person you were responding to was responding to never said the thing you very clearly directly quoted.


I think you might have misunderstood someone here. The person you quoted made a generic statement about what we should expect from an autonomous vehicle, but never said (nor implied imho) that the person he responds to didn't expect the same.


> They were testing FSD

So if that was a human and they ran them over it'd be okay because they were testing FSD?

They're putting themselves (fine) and everyone around them (far less fine) in danger with this stunt.


It's their standard go-to excuse. "I would have done that too" really says more about them as drivers than anything else.


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

Search: