unfortunately there isn't a dashboard yet in the logged out view, but if you view the feed when logged into sprinklz you can directly see (and edit) all the params used
292 karma · joined June 27, 2024
unfortunately there isn't a dashboard yet in the logged out view, but if you view the feed when logged into sprinklz you can directly see (and edit) all the params used
I also want to make the 'Demos' text better, but I'm still working out exactly what it should say. Unfortunately if I remove '(click a box below)', people don't know they can click on it lol.
I'm thinking maybe "Try It Live (click a box below)" or maybe "Demos (click a box to try it first)", but idk its hard to get it right without adding visual noise. I agree though, and want to make it better.
See: https://sprinklz.io/demo/editThemes for an example. (on nonmobile if you want to see the on-screen editor)
We _could_ run something like https://github.com/sstraust/automagic-dark-mode , but I decided against it, because it makes for a confusing user experience. idk -- i wanted to support dark mode, but it's hard to make these tradeoffs correctly.
if not i will crawl into the deep cave for a longer debugging session
i tried signup on chrome/firefox/safari + demos and i can't manage to repro.
im assuming this is after submitting signup?
if you want to save your preferences though, we _do_ need you to sign up, so that we can save who you follow, etc. to a database.
e.g. here is a direct link to the top headlines: https://sprinklz.io/demo/headlineNews
glad you're feeling this way too!
if you are looking at your metrics, I want to be clear that this transition will not happen overnight, but it _will_ happen for this reason, so just be aware that your short-term metrics won't tell the full story
that supports building macros from source (!)
there's a detailed explanation here: https://youtu.be/Djsg33AN7CU?t=659
I'm making good progress on it though and hope to release an improved mobile experience in the next month or two.
You can still create a feed on desktop, and then view it on mobile if you sign in to the same account, but I'm in-progress of making a mobile-only experience.
I built a little mafia game a few years ago, but it was never very popular. http://gptmafia.io/
and someone i know made one too: https://talktomehuman.com
maybe the games market is just hard in general, but i dont know that ai games are super popoular even though people are building them. playing mafia against the ai feels somehow tiring, even if it is also occasionally fun
currently the calculations in this library are done with a clojure jar, so if you're interested, you might have an easier time calling that directly
on youtube: https://www.youtube.com/watch?v=dlW6YzwUZ-M on clojars: https://clojars.org/org.clojars.sstraust/deft
Today I'm releasing deft!
It took me about 6 months to really think it through all the way, and get the design just right, so it feels good to finally publish it.
TLDR of 'why deft'
The problem is that: - Clojure records use single-colon (unnamespaced) keyword access to lookup record fields - Clojure records do not allow you to define abstract classes, or things that rely on complex dispatch behavior. - Clojure records do not reload easily in the REPL, so you have to re-instantiate the object to see changes to method defs.
- Clojure maps are difficult to nail down. Even with libraries like Malli, it's hard to declare interfaces that explain "what can I do with this thing?" and "what multimethods do I need to implement?" - Defining maps with Malli schema is not as enjoyable and ergonomic as the syntax of defrecord
The library is basically just plain maps, multimethods, and malli schema, but adds macros to allow you to use the same syntax as defrecord, and to define interfaces and implementations as lists of multimethods a type must implement.
The goal is to give something that's still enjoyable to work with, but lets you really nail down the behavior when you want to (and still keeps it ergonomic and fun).
A secondary goal was to make something that is reliable and stable, and is (hopefully) easy to adopt in existing codebases.
(more detailed explanation in video and on github)
check it out!
I'm curious how you tackled that problem