OT: how does anyone buy their cloud? Is it only available as a public alpha/beta with remote control? I might have a client interested into this, but needs to have some guarantees that their data remains on-premise.
> Is it only available as a public alpha/beta with remote control? I might have a client interested into this, but needs to have some guarantees that their data remains on-premise.
You are purchasing hardware. You put it on-premise. Our software gives you a cloud-like deployment model, but it's not going anywhere other than your rack.
Happy to answer any other questions, even if they're off-topic :)
Ah nice, I thought for a second it was more vertical with its own hardware (which has its pro and cons, maybe it's in your plans..). Would that work as a SAAS? Or price per hardware device/machines I can create?
> Would that work as a SAAS? Or price per hardware device/machines I can create?
I'm not 100% sure what you're asking. You could use this to build your own SAAS business if you'd like, but you can't rent the hardware from us, or run your software on hardware we own, if that's what you mean.
Ah now I understand what you meant with "You are purchasing hardware", I missed completely that point. "You are purchasing hardware from us" :) yeah, then it's what I originally understood. Good :) so I guess one time payment, I get the hardware, I set up with your software into your hardware that I purchased and then I should be good.
We sell support too, but yes, fundamentally it's a one-time payment: we don't have software licensing fees, for example (and the vast majority of it is open source). You're purchasing physical hardware.
> I set up with your software into your hardware that I purchased and then I should be good.
You don't even need to set it up! Heck, the rack comes pre-cabled. You roll it into the data center, hook it up to power and internet, turn it on, and get going.
I was wondering: does anybody know if there are any good resources for writing a good text adventure? Any nice tips and tricks? Mainly related to the content. I guess it overlaps with "writing a good novel", but I bet there're some specific advices that can be applied to the text adventure.
I wanted to write my text adventure, but I'd offer reader to have multiple options, especially for those who are not really practical with english (includes myself ^-^).
Aaron Reed's 50 Years of Text Games[1][2] is a fantastic journey into the history and the possibilities of text-based games. I got the physical book and was surprised to find it as engaging as a novel. Each chapter takes one year between 1971 and 2020 and picks a game from that year to discuss in depth. While it might not help with the writing per se, you might good ideas there (several of the games discussed are in the "Adventure" lineage).
This comment got me to purchase this book and bump it to the head of my reading queue. I'm about halfway through it and it's really, really good. I definitely think it can help with writing/design, by showing the breadth of possibilities and how the art has evolved.
For the technical side of things, use ink script. There's an editor, plugins and it's a mature project.
For the creative side I would recommend trying out all kinds of things. Should your player be able to get stuck/into a dead end? Will players play once or many times. Can you "win" your game or is it more of a narrative? How do you want the player to feel!
For some more specific ideas, think about how your game branches. Branching and decisions in games are far trickier than they might appear. Too subtle and the player misses the choice entirely. Too in your face and they become boring ("kill the baby" vs "save the baby", gee I wonder which one takes me down the evil path)
Also, merely asking a question or giving a choice can influence the player. If you ask "who is the killer?" and give a list of suspects, one of them must have done it, even if the player never considered it. The question also assumes the player knows there was a murder and gives that away if they hadn't worked it out yet.
Yeah, I like things like Ink a great deal. It's really easy to overcomplicate narrative design if you're not careful, but Ink (and so forth) do a good job of keeping things simple and staying out of your way.
I've spent the last three years building a game engine specifically to do this, and currently finishing the final draft for the game story I've created to go alongside it.
Happy to share anything you'd find helpful. The big takeaway for me has been, you're going to want to graph out the impact of choices before you write the story. If you know the flow of decisions, then that gives a much clearer structure than trying to write the story first and then create branches off it. I think the reason is that it sets a much tighter scope for the writing doing it that way, whereas if you write the story and then find ways to branch it, the scope for that is functionally infinite.
Indeed: https://marcusb.org/hacks/quixotic.html try not to block LLM bot traffic and start injecting spurious content for ""improving"" their data. Markov chain at its finest!
I would remind all the people to recompile the build themself, before downloading a random binary and allowing it to access the Slack workspace. But, very interesting project!
I’m honestly surprised there aren’t way way more… extremely nefarious straight up trojan data exfil builds out there of all kinds of rando tools posted as like “hey here’s a convenience build I got to compile for toy arch | codesigned for macOS | helpful VM or Docker image | did something sneaky to bypass API rate limits | fixes that one annoying thing YMMV” etc. and posted as comments on HN or anywhere by seemingly helpful nerds, with the web server serving up the evil build 5% of the time or GeoIP’d to the Bay Area.
Like it seems like such easy low effort “hacking” why isn’t it more common?
Hell even GitHub “Releases” on your fork can also just not match the repo.
Paged Out! is a free, experimental (one article == one page) technical magazine about programming (especially programming tricks!), hacking, security hacking, retro computers, modern computers, electronics, demoscene and other similar topics.
It's made by the community for the community - the project was created by Gynvael Coldwind with multiple folks helping. And it's not-for-profit (though it is managed by a company – see the bottom of this page) - this means that the issues will always be free to download, share and print.
> Q: But the law requi... wait, what?
We don't use any active or passive methods to track our users. There are no "user accounts" on this website, and we're fine with low-resolution statistics (like view/download count) for "project success" measurements.
I love that, I need also one for the cloud-free products. I don't need scanner files in cloud, no, I don't need a washing machine uploading some data to AWS. I just need tools that do whatever they were invented for.
