sonicrocketman

I was already somewhat familiar with cursive, and I knew it was a ~more proper~ way to write in that cursive is designed to lessen strains on the hand and be easier to write at speed. Also I wanted to. ¯\_(ツ)_/¯

Hey all,

Don't be too harsh on the code. It was thrown together in an hour.

I used the method from the paper (linked on HN earlier this week) but had to tweak the code as it was both unclear what the input types should be and had a few bugs. Hopefully I didn't break it during the process.

The classifier seems to work fine and gave me seemingly reasonable results from my admittedly limited testing.

Mostly this was an exercise to teach myself about this method, though I do have a possible use case for it in the future.

Very cool to see such a classic CS problem applied to new domains. Feels like a programmer's version of pharmaceutical drug repurposing.

I've been using BBEdit since college and I love it. I was and is my primary text editor for all of my development (except Java and Swift which basically require an IDE).

Also, it's funny: I am only marginally older than BBEdit. I can't imagine running a software project for so long, let alone so successfully.

Keep up the great work BareBones!

Direct from the mouth of the other half of the team:

We used Xstate over react-router by using a parallel machine:

- One for application state - One for view state

We had to hack the innards of the events a bit to get the two machines to communicate. This allowed the view to re-render the jsonschema form at the exact right time, and not flicker on multiple state transitions.

In hindsight, graphql wasn’t as necessary as we initially thought. The important part was storing the mutation as a string as an xstate transition parameter. We used federation, so it did help us deal with multiple backends.

All database. Versions were handled by having a core machine that pulled the kiosk’s workflow from the server and ran it as a submachine. So the code on the device (core machine) could switch sub machine workflows on the fly between runs.

Sure. Check bio. Email in blog's about page.

Unfortunately no. It was proprietary.

(we pushed to open source the guts, but to no avail)

Both of us reminisce about it though. We literally retooled the fleet of devices in a weekend to adapt to COVID and it worked. We interfaced with tons of hardware and even ran a customized debian image, all powered by RPis. Truly a nerd's dream project.

The real benefit for our project was being able to statically define, and therefore export the business process the app would follow. Once it's exportable, it's validatable and configurable.

IMO the JSON was hard to read, but we had a plan to build a GUI config builder that exported the state flows.

I was one half of a team that heavily leveraged XState in 2020. We used it to build a general-purpose kiosk app (in Electron) that could be updated remotely using an Xstate configuration served by a graphene-django app. One of the most technically impressive pieces of software I've ever had the pleasure to work on. (I mostly did server/backend stuff).

The entire kiosk device could be repurposed on the fly and Xstate + JSON schema form allowed for completely customizable & swappable UI.

Shame the project died.

Sandwiches are but one part of the equation! For full context see the taxonomic definition of Sandwich (domain Catino, kingdom Cincta).

https://iifrp.org/rfc/RFC-5.html

(disclaimer, I wrote this spec)

From the Bill Text, services must include:

> (E) Historical versions of the terms of service and change logs.

This alone is a big improvement.

https://trahan.house.gov/uploadedfiles/tldr_act.pdf

Edit: adds link

I still have it installed, with the hope that one day it will get launched regularly.

If I read this correctly: if you aren't collecting the info (for ads, etc) you don't need to verify anything. A non-tracking, non-data surveillance website is fine.

Am I missing something? Services are allowed to collect the data they need to perform their essential function right? (my reading says yes)

This just says: don't collect info on children you don't need and assume people are protected unless you verify otherwise.

Just don't collect the info you don't need. Seems straight-forward to me.

Interesting post. I'm curious about adopting Swift UI myself and this is good to know.

btw, please add an RSS feed to your site. If you have one it's not discoverable via in-page links, link tags, or educated guessing.

Hey all,

Years back I created this site with a few friends as a joke, though over the years it has started to blur the lines between joke and serious endeavor.

We were upset that there seemed to be no agreed upon standard for what common food items should contain. We started with a simple set of questions: what makes something a breakfast burrito? When is a grilled cheese actually a melt? Etc. we hoped we could help answer these critical questions.

We took the design (and some CSS) for the site directly from the IETF including the top colored bar.

Over time we’ve gotten more people involved and helped grow the ambition of the institute. This year we took on our biggest project yet: attempting to create a rules-based system to categorize all food (RFC #5).

We’d love more interest and contributions from anyone who wants to help classify food and generally help with solving the critical problems in food-related protocols.

Links:

About Us/Our Goals https://iifrp.org/about/

RFC 5: A General Taxonomy for Food https://iifrp.org/rfc/RFC-5.html

Twitter https://mobile.twitter.com/iifrporg

Edits: add links

I’ve been casually following turbolinks (now Turbo) for a while now, and I intend on using it in a future project.

Is anyone out there using turbo? Got any suggestions or tips?

Hey all,

I'm one of the (two) developers on Adventurer's Codex! We're super excited about this release. We've had DM tools for years and these new tools are a major improvement. We've made them easier to use and more usable on mobile devices.

As for the party tools, we used to have most of the functionality we're re-announcing today, but we removed them about a year ago because they were pretty unreliable. Today, they're rock-solid and ready for prime time.

We've been building Adventurer's Codex for over 5 years now and it's been a wild ride. It was one of our first web projects as developers. We've made so many mistakes over the years, but building AC has always been a great learning experience and we've garnered quite a following.

I'm free to answer any questions (technical or not).

Hey all! I make Nine9s (and other things).

As of this release, Nine9s -- an uptime monitoring service -- can no monitor a lot more than just web services. Your servers can send data to Nine9s and you can configure criteria to judge what the data sent says about your server's health.

Think of a cron job that reports disk usage. You can tell Nine9s to alert you when your disk usage percentage goes above 90%.

There's also now a native Mac App for Nine9s (along with the existing iOS/iPad app).

Here's a blog post explaining the new features:

https://brianschrader.com/archive/nine9s-gets-an-upgrade-/

And a help article that has some examples:

https://nine9s.cloud/kb/measure-quickstart

Feedback welcome!

Hmm. I will look into that. You should just be able to swipe down on the card to dismiss it.

Thanks! Adding the ability to browse around is something I’d like to do eventually. This is the MVP.

Thanks for the feedback! I intend to add a feature like that at some point. The version that’s out there now is very much an MVP.

Hey all!

I'm an indie ios/web developer and I build Hewell (pronounced the same as Huell (and a reference maybe some of you old-school PBS viewers may get).

I've wanted an app like this for a long time, but most travel guide apps have really high production values and consequently low coverage. Lots of apps can give you a bespoke experience in San Francisco, but few work well everywhere (custom voice over is expensive). Hewell bypasses all of that by leveraging the power of WikiData and Siri.

Hewell was originally dreamt up by a myself and a few friends at a happy hour ~2016, but I'd never gotten around to actually building it until last year during lockdown--which honestly wasn't a great time to launch a travel app. Now that things are opening back up and people are traveling again, hopefully Hewell will be more useful.

I know I would have loved an app like this when I was in Japan a few years back. I knew there was so much history all around me, and I probably missed a lot of it. That said I've found Hewell useful even at home. There's a lot of hidden treasures in major cities.

In the future I'd like to add a "Tour Mode" that can guide you along a route or recommend places to go while you're driving or walking.

If you like the app, please consider donating. If the app makes enough money I'd like to donate a sizable chunk of the revenue to the Wikimedia Foundation since they make Hewell possible.

Links:

Announcement Blog Post: https://brianschrader.com/archive/announcing-hewell-public-b...

My Apps: https://skyrocket.software

Thanks for catching & fixing this!

For anyone who's able to, I'd love to hear how my awful method compares with other real methods. (i.e. not accounting for some mathematical nuance, performance, etc)

This is a very cool idea. I love to see more worker-owned takes on big-tech ideas.

Thanks for pointing this out. Fixed.

I did not know this. Good solution.

(that's actually how I solved the original issue that I reference in the post, and how I got the idea for this silly solution)

Good point. I didn't think of that. I'm not sure how my CentOS servers handle this scenario, but it seemed to take up the full 8GB however I checked.

I write music for my band, but here's some of my independent stuff.

My 2020 song:

https://sonicrocketman.bandcamp.com/track/i-thought-we-were-...

I spent the summer writing pirate shanties (funnily enough, before the craze started):

https://sonicrocketman.bandcamp.com/album/tales-and-legends-...