Well, Cory recently said in a podcast we can use it to mean "product got worse", so I've become less pedantic on this point fwiw. (I think it was in the episode of Adam Conover from about a month ago)
HN user
joshbuddy
Code while high, debug while sober. Best of both worlds!
Good feedback, let me see what I can do about this and thanks
Oh darn, sorry about the email notifications. I'm going to disable them and give them a little extra polish later. Thanks for letting me know
Fwiw, we're only using Discord for disposable communication. We have a docusaurus site up for the docs, and otherwise all the development is taking place on Github. Discord seems very popular with the board game crowd, so it was kind of the first place we went to try to reach gamers before we started reaching out to developers.
What do you prefer to discord for disposable communication? Certainly open to suggestions.
Yeah, I can totally recommend boardgame.io as well. Nicolo is super helpful and friendly. Also check out his other project https://boardgamelab.app/.
Polyfill is in place, please let me know if its fixed and thanks
Polyfill added btw, happy to take any more bug reports either here or in discord and thanks!
Oh wow, thanks, I'll check this out.
We were doing something more like merely recording the game moves and applying them to arrive at the game state (having deterministic per-session rng). It's a good way to do it, but for the same of simplicity, this time around we just record the whole json blob per move. It simplifies undos and it also lets us easily move through history if you want to view a previous state.
But I'd love to try to apply some of your lessons to a later version. The challenge for us now is making a good api for expressing board games. That's been really tricky tbh. We've been working on this for ~7 years and have gone through many iterations of this api trying to get it right. I sure hope we're closer this time.
Thank you, polyfill incoming!
I'm going to add a polyfill later for this. Thanks for the bug reports
The reason the server isn't in Python is because in boardzilla, you don't express your game twice, once for the client and once for the server. Instead, you express the game once in typescript, and that code is actually used on both the server and client. The client is operating a lot like the server, just without the hidden information.
The React aspects are really minimal, all the animation logic is by outside of React. We're really just using it for the jsx syntax to make it easier to return markup-looking components.
Thanks Soneca. Fixed and deployed.
I think I have a fix deployed now. Please try it again if you have a moment.
Hey Doublerabbit. Thank you for the bug report and stack trace, super helpful.
I'm taking a look at it now. I've got to go to bed soon, but I'll try to fix this as soon as I can.
Um, wow, I had no idea. I've got some other pretty good domain names at the ready, so, maybe I need to pull the trigger on that.
Hey Joemi. I wanted to make a self-hosted single game runner, but I haven't gotten to it yet. The interface used by the game/server is detailed here https://github.com/boardzilla/boardzilla-devtools/blob/main/... so it should be pretty easy to make this runner. I hope to get to it soon.
Hey jamager, thanks for the kind comments.
Totally agree, Asmodee has basically prevented a real competitor from entering the market. We have an idea in mind that doesn't involve going up against BGA, but instead looks at more smaller games from indie publishers. Not sure how viable that is, but not sure what else someone is supposed to do.
On my Miele at least, there is a 65° power wash setting which takes less than one hour
I'm working on a protocol that hopefully addresses some of these ideas, with a heavy emphasis on mobile-first. I'm just about to have a formal security audit, but if you have any interest in this, I'd love any early input I can get to see if it solved some of these problems.
If you're interested at all, please drop me a line at josh@meow.io.
Roost | Remote international | Swift iOS + Desktop | Contract-basis
Hey there, I’m Josh and I’m working with my friend Jared on Roost. I’m a developer and Jared is a designer who codes. Roost is a private by design, offline-first, and ultimately open-source iOS and macOS app that makes it easy for people to get things done and manage life with the people they care about. Roosts are essentially chat rooms organized around topics with todo lists. Our vision is for Roost to have the security and privacy benefits of Signal via end-to-end encryption with the interface design and user experience of Things.
We’ve already built a data and application layer in Go that provides an API for sending a message, creating a todo item, and all of the other functions needed to support the app. We also have high fidelity designs for the app in Figma that illustrate the concept and flows with some of the finer details still TBD. We’re looking for someone to join us on a contract-basis and not only take the designs and implement them in Swift using the data model we’ve built but also set up a strong foundation for future developers to build on in an open source community.
We have a full job posting over at https://getroost.app/careers and if this sounds interesting or want to chat about any of it, send me a line over at hello@getroost.app. Thanks!
I'm working on an offline/delayed syncing sqlite that deals with conflicts. It uses last-write-win for conflict resolution, the target audience is small sql databases you want replicated among a small group of people.
If it sounds like something that might be useful to you, I'd love to talk about your needs.
You should check out this paper where they tested different representations on humans to see what they could tell apart, and came up with a novel representation called Moji.
https://exascale.info/assets/pdf/students/MSc_Thesis_-_Micha...
This exactly mirrors the situation where I work. They picked flask/sqlalchemy early on, the actual glue code is hard to get right, people were confused over the session api vs core api and problems ensue. As much as we want to tell people you should read docs carefully, libraries should make it hard to misuse and introduce footguns, and this is an aspect sqlalchemy maybe struggles with.
Isn't think sort of zero sum thinking a bit uncreative? I'm not sure there is any law of nature that says you must pursue one to the exclusion of the other.
How is it strictly worse?
I wonder if there is a way we place these App Store decisions into the hands of a third party. Either that or break Android away from Google and forbid them from colluding.
In order to see your screen shot of a captcha, I have to solve a captcha. :/
Imagine that this is just employing machine learning, where the training set is police reports filled out after the fact. Is this just big data being applied to threat prediction?