@apenwarr.ca @tailscale.com some feedback – the new pricing terminology of "minutes for ephemeral resources" is poorly explained. I immediately read it as "nodes registered as ephemeral will now cost me by the minute" and was concerned, since I run all of my infra in ASGs without persistent state.
I’ve seen a few of these Artemis tracker sites pop up but the thing that’s annoying is none of them are using JPLs API to pull in real data. So I’ve created my own version that does with some sci-fi flare of course.
Check it here: lcarsworkshop.com/artemis
#nasa #artemis
Is the reason for de-normalization is for resiliency / isolation from needing a second data source? It does have some nice properties from that perspective.
Yeah, an aggregator appview would be nice - I was trying to re-use constellation for that.
I haven’t done any atproto development before, so I’m not sure if that actually makes sense. It seems a little strange since the collection lexicons are not hosted on a pds, so it’s not a canonical at-uri. Was the best I came up with though 🤷♂️
I was looking at this the other day - is there a the standard way to reference atgeo collection items so they can be indexed across apps? I was considering using a uri field with “places.atgeo.org/org.atgeo.places.{collec... so backlinks can be queried via constellation
have you seen the new supply chain vuln? don't update tubu. it's literally on heebee. they got poodee's deps. they infiltrated dippy. roll back weeno. disable scripts in ~/.gumpyrc. it's in poob. do not install poob. do not update poob. uninstall poob right now. poob has it in for you.
thrilled to get to work on this!!!!!!
Circles was right there
This is a sick visualization style
I'm going to be honest: I am a little mad that both the Rust people _and_ the Bazel people ended up being broadly correct
I love this project! I wanted to build this same thing but had not found the time.
Ah I had not seen directory branching, TIL
Have you thought about storing the full repo for foo in the same server as origin? I feel this type of subtree commit filter + rewrite could be a really interesting progression to the current “store a hash of the contents of a remote, and optionally cache it” method used by submodules / nix / etc
Developing a new hermeneutic: AI cannot create art or replicate the works of man but it can write code because code is outside the light of God
`jj rebase --simplify-parents` was the flag I didn’t know I needed
Good news everyone!
You can now analyze your own posts for semantic novelty from the famous Sichu post, ‘analyze the semantic novelty’
mino.mobi/novelty
The consequences of my most offbrand post wondering how to relate to people are left to the reader for evaluation
Three features:
- the worktree is a commit so you don’t need to git stash, just switch
- merge conflicts are first class citizens, so you don’t get “stuck” in a modal state resolving a merge conflict
- jj undo just works to revert any repo op, including creating branches / deleting things / etc
You should check out @jj-vcs.dev! Claude has gotten good enough at using it too
I was just looking for this last night
We just need to teach them ^H^H^H^H
@spacecowboy17.bsky.social turn your computer back on please 🙏
my take on the LLM burnout thing is that maybe you should take a vacation, idk. even before AI I would work really hard on something, hyper focus on it really, and then need to recharge for a while.
that’s… just, like, how people work? you can’t go 100% all the time
This is relatively new and minimal (and Linux only) but it’s in this domain
Ah I didn't realize you did it client side, that's cool! I think the second is probably the most atproto native but it does feel sort of weird to duplicate the data.
How does this handle a collaborator deleting their account? Are their operations mirrored into the project state, or do they get undone if they delete their data?
halftime show fromt eh supebowl showing a set on the field featuring a nyc bodega
This kind of smart, walkable, mixed-use urbanism is illegal to build in most American cities.
A picture showing an example output of the program on the city of Montréal and the autumn color scheme. You can see a map of the city with all the roads, trains, subways and light rail. At the bottom there the poster is titled MONTRÉAL - QUÉBEC. The latitude and longitude are also written under the title.
A picture showing an example output of the program on the city of Paris and the emerald color scheme. You can see a map of the city with all the roads, trains, subways and light rail. At the bottom there the poster is titled PARIS - FRANCE. The latitude and longitude are also written under the title.
A picture showing an example output of the program on the city of Tokyo and the japanese ink color scheme. You can see a map of the city with all the roads, trains, subways and light rail. At the bottom there the poster is titled TOKYO - JAPAN. The latitude and longitude are also written under the title.
A picture showing an example output of the program on the city of Berlin and the noir color scheme. You can see a map of the city with all the roads, trains, subways and light rail. At the bottom there the poster is titled BERLIN - GERMANY. The latitude and longitude are also written under the title.
Here is what I've been doing this past week: git.olaren.dev/Olaren/mapto...
A little python program that generates poster for cities! You might have seen stuff like this around lately, but I modified it to put an emphasis on rail infrastructure :3
I can agree that it’s sensationalist language, but I would not immediately call it bad faith.
I’m also not aware of the larger context so maybe I’m not aware of a pattern, but I think an outright dismissal just because of the commenter got a technical implementation wrong is not really warranted
