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

Steam often provides every version of a product. (The ui has no option to download them, but you can fetch them via the builtin console)


There is nothing about stopping/killing rsyslog in thst virustotal output. `kill -s HUP` sends SIGHUP to a process (read rsyslogd(8) to know how it interprets HUP).

It seems like virustotal also records unrelated processes running on that host, logrotation is a normal thing.


Kopia allows you to run scripts before and after a backup. It also allows you to redirect the base from where to read the files.

They Document it for the likes of FreeBSD, for Linux one would skip the mount step and just set the snapshot path to the magic .zfs directory.

https://kopia.io/docs/advanced/actions/#zfs-point-in-time-sn...


Why wouldn't you use the magic .zfs directory on FreeBSD as well? Are the instructions assuming an older version?


> Shibboleth is the last major IdP I know if that is SAML-only

Shibboleth has officially supported Plugins for OIDC for some time now.

As others said, Shiboleth is still rather pupular at Universities and higher Education, OIDC will have a hard time to set foot there without the OpenID Connect Federation Draft beeing finished and then Implemented by the different Metadata Federation that exist (most National Research Networks manage one)


It is Open Source, but under a Non-Free License (PolyForm Noncommercial License 1.0.0).


The PolyForm Noncommercial License 1.0.0 is not an Open Source license.


Licensing is a nuanced subject so we've written a detailed post on it. But in short, our license grants you the same rights that come with an open source license, except the right to sell or commercialize Umbrel.

Here's our post that explains our licensing in detail: https://blog.getumbrel.com/everything-you-need-to-know-about...


No, it's not Open Source. It's a perfectly justifiable decision, but it's not Open Source, nor is it equivalent.

Yes, your license means that individual users can make little patches to customize the product to their needs, and even share these customizations with other users. That's great!

But the license effectively prohibits borrowing code from your codebase for use in other projects, meaning your code does not become part of the aether of Open Source code that anyone can build upon. That's a very important part of what it means to be "Open Source".

It also effectively prevents any large-scale modification or forking effort, since maintaining patches as the underlying codebase evolves is a hard job, and the license prohibits people from funding such effort. If users want timely security updates, they will need to stick close to your version of the codebase. So the lock-in is there.

Again, this is all a perfectly justified direction for you to take. I don't blame you at all, and I definitely understand that it's Amazon's fault that we cannot have nice things. But it's not Open Source.

On a tangentially-related note, a little tip: You have defined all noncommercial organizations -- including education, public research, and government -- as being permitted users. That may be dangerous. I was the founder of Sandstorm, and these organizations were exactly the ones most interested in paying for our product -- literally the only big sales we ever made were a couple universities, a big research org, and a government. Despite being non-profit, these orgs have lots of money and a need for self-hosting.


Thanks for the insightful reply. Everything you said makes total sense.

Re noncommercial organizations being permitted users, this was a conscious decision on our part. We're purposefully building Umbrel purely for consumers, and don't plan to serve any commercial or noncommercial organizations. We want to align our incentives directly with consumers instead of enterprises, and this is purely to help us focus on building for the user-base that excites us the most.

I'm a big fan of Sandstorm btw. It was way ahead of its time.


I see. Well, I hope you are able to succeed at that. For what it's worth, we initially focused on consumer use but weren't able to find a path to revenue there.

Despite a lot of noise on HN, we had only a few hundred signups for our paid hosting service. We built super-scalable hosting tech but it turned out we could have hosted them on a single big VM all along... oops.

I think the problem is that the apps, while functional, weren't competitive with their SaaS competitors, and so the only reason to use the hosting service was if you really cared about the Open Source aspect. Maybe if we had a killer app that was actually better than any SaaS alternative, we could have gotten somewhere? But we never found that.

Meanwhile, we got a lot of feedback from people working at big orgs that were forced to self-host for regulatory reasons. Such orgs are terribly served by the current software market, since they can essentially only buy software from companies that specialize in building regulated software, and those companies generally build software that is expensive and terrible.

Real-time collaboration essentially didn't exist in this market, making our apps actually better than what these organizations had! But we had absolutely no expertise in selling to orgs like this, and we never really figured it out. We should have hired for it much earlier, or maybe even brought on another co-founder with enterprise sales experience.

So, we were unable to get anywhere before investors pulled the plug.

With that said, I always say you should not trust anyone's advice. Your story is different and you need to do what makes intuitive sense to you. If your intuition is right, you succeed. But you certainly can't succeed by going against your own intuition, so if someone says something that doesn't make intuitive sense to you, ignore it.


Thank you for your work on Sandstorm! I live in the highly-regulated, not-for-profit world. Sandstorm's architecture was very compelling for us. Self-hosting was a good place to start and the Capability-based Security solved a lot of problems.

I agree that the overall functionality for the apps wasn't quite up to snuff. The problem is, self-hosted apps are structurally under-resourced relative to their hosted peers. This is because SaaS providers can amortize development costs over a much bigger user base while simultaneously capturing operations efficiencies.

In my world, we want all the latest stuff, but refuse to let anyone host our data. We wind up with a small vendor pool that specializes in meeting regulatory requirements instead of making good software. I am very interested in finding technical solutions to this problem. Or at least, technical solutions that create new options to solve the operational and cultural problems!


To be fair, I think Umbrel has a very different consumer story: Since it has a much stronger crypto focus, it is targeting consumers much more likely to spend (crypto)money, I think, than the average consumer.

And a key difference is that Cloudron and Umbrel may monetize selfhosters, which I believe Sandstorm did not endeavor to do at all.


Ah hah... Well... I have no intuition for what might succeed in the cryptocurrency space.

With Sandstorm we did plan to have paid apps and in-app purchases eventually, believe it or not...


Cloudron devs have said they're profitable the core team is salaried, but they have some larger nonprofit/NGO type customers.


Yeah that doesn't surprise me, you pretty much have to pay them regularly if using Cloudron, even as an individual, whereas nobody hosting their own Sandstorm server ever had to pay anything. Even when Cloudron was open source, updates weren't automatic unless you subscribed.

I think personal servers is pretty key, so I'm glad there are a few endeavors working on it.


> It's a perfectly justifiable decision...

Especially when one of the VC firms that funds your project is also the one behind formulation of the PolyForm set of licenses, I'd imagine. At least, PolyForm is better, in some sense, than fully closed source projects built atop other MIT/BSD/Apache licensed projects (say, the V8 JavaScript engine ;), and never shared.

The only reason I dislike non-OSI approved licenses are, the "users" of such licenses want to have their cake and eat it too: As in, they want to project open source ethos while also denying the advantages/rights otherwise afforded by Open Source, as defined by the OSI.

Imo, source-available licenses are justified only when companies using it are honest about their intentions and forthcoming about the license's limitations. Nothing specific on Umbrel, but generally, misdirection by firms insistent on source-available licenses as being some convenient 'middle-ground' is off-putting, to say the least!

I've followed Umbrel since I first stumbled upon it in August 2020, and of course, I'd have liked them to be open-source (since I don't believe software is their core advantage, rather their brand is; but then again, what do I know): https://github.com/getumbrel/umbrel/issues/291#issuecomment-...

That said, Umbrel already brings a lot to the table... its licensing is a predictable HN distraction from discussion on its true potential.


Except it denies me the right to purchase support services from the vendor of my choosing. It also denies me the ability to hire a contractor of my choosing to create a derivative of the product or even contribute changes to the product. It further denies me the ability to receive sponsorship from another individual to create a derivative work (This falls under commercializing, but the other two would not be me doing the commercializing).

These are all rights I have with Open Source software that is denied by your non-commercial license. Reading your blog post, you seem to not understand Open Source nor do you seem to understand the implications of your own license very well.


Fair, one can see this as just source available. But still far more permissive than cloudron's license.


Cloudron is also source available - https://git.cloudron.io


Okay, I will admit I am only familiar with Sandstorm from that list :)


This is pretty much -Os. Void Linux provides -O2 builds of GCC for both musl and glibc with a negligible performance difference. I have not benchmarked it lately, but it is clearly below 10%.


Podman can also be optionally be run as a system daemon that provides a docker socket, but still has/used to have quite a bit of compatibility isues.


My first intuition would be, to run the game inside gamescope and use a 2x (or higher) scaling factor.

https://github.com/Plagman/gamescope


Very nice, thank you!


I don't think a Pi 4 would be fast enough to provide a enjoyable experience. I just tested OpenMW on a Pinebook Pro (RK3399 SOC, should be slightly faster than a PI 4) and I do get like ~30-40 fps with lowest draw distance in Morrowind. Fallout 3 should be even slower due to far more and more detailed objects.

edit: Rendered at a meager 800x600 px


https://youtu.be/Fb1UUesbNlY shows a Pi 4 running OpenMW not badly at 720p with medium draw distance.

Still looks pretty bad, I think I'd rather run the Android port of OpenMW with an HDMI adapter I think.


Maybe I'm used too much to playing with 60+ fps, but I would call a highly unstable framerate with dips below 20fps bad.


How comes the Android port is supposed to be faster? Isn't Raspberry PI 4 similar to a good Android smartphone in hardware?


I would have characterized it more as a midrange phone from half a decade ago.


Half a decade is not much. My phone is a flagship from more than a half a decade ago and everything (except the GPS module - it usually takes minutes of standing still to hit enough satellites and knocks out the whole new battery in under half an hour) works perfectly fast.


Half a decade in mobile CPU time is massive. The A15 is, at minimum, literally 5x faster than the A10.


I played Fallout 3 on a Core 2 Duo with Intel graphics. I used the lowest graphics settings possible (the display's native resolution though - 1440x900, not the minimum) but enjoyed. Is Raspberry Pi 4 supposed to be even slower?


You should be able to build and include boost json as a standalone subproject in CMake if you are using C++17. (Or also possible to use as header only lib)

It gets far more complicated with C++11, since you also need a ton of other boost modules there.

For more Details you can read the Readme of it. https://github.com/boostorg/json


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

Search: