Seems like something DOGE should have tackled early if they actually cared about making the government effecient. I guess making the lives of the disabled easier isn't flashy enough.
A paper came out about this recently: The City as an Anti-
Growth Machine.
> Logan and Molotch's “urban growth machine” remains foundational in urban theory, describing how coalitions of landowners, developers, and politicians promote urban growth to raise land values. This paper argues that under financialized capitalism, the dynamics have inverted: asset appreciation now outweighs productive investment, and urban land is increasingly treated as a speculative asset.
Lately I’ve been spending a lot of time transitioning from tech into urbanism and working on a few projects I care deeply about.
- Urbanism Now - I run https://urbanismnow.com, a weekly newsletter highlighting positive urbanism stories from around the world. It’s been exciting to see it grow and build an audience. I'm thinking of adding a jobs board soon that'll be built in astro.
- Open Library - I’ve been helping the Internet Archive migrate Open Library from web.py to FastAPI, improving performance and making the codebase easier for new contributors to work with.
- Publishing project - I’m also working on a book with Lab of Thought as the publisher, which has been a great opportunity to spend more time working with Typst.
These projects sit at the intersection of technology, cities, and knowledge sharing, exactly where I’m hoping to focus more of my time going forward.
Kinda related, does anyone have a favorite obsidian plugin for AI editing on mobile?
I wanna be able to talk to a document and iterate on it just like chatgpt with canvas but inside obsidian.
I've been digging around and haven't quite found anything to do that.
One potential challenge is I'm not sure how easy it would be to let it do tool calling to edit the document rather than spitting out the whole document each time (with risk of minor changes).
This UI is great but do you get this horrible thing where sometimes the browser is shows a white screen and you have to force stop the app? Happens all the time on the latest version for my Pixel 9a. And did on my Pixel 7 too before. It's really horrible and I can't pin down any rhythm or reason other than loosely seeming to happen more often when I'm in battery saver mode.
I don't have that on fenec and ironfox on my pixel 6a running graphene.
What I have always had with any firefox based browser on android is erratic behavior in text field. Most of the time it works well but sometimes on some commenting systems my input is duplicated/multiplicated/garbled, trying to select where you want to insert words in the middle of the sentence sometimes becomes impossible, always resetting to the beginning of the text field, etc.
On some websites it only rarely happens, on some it is much more regular. Never understod why but when I want to edit a comment I have to resort on a regular basis to copy the full comment to a note app, edit the text, and replace it in its entirety in the text field.
Super annoying but still less annoying than using a chrome based browser with no way to remove ads and have a bit of privacy control.
Linkwarden is awesome and with the singlefile extension it's pretty easy to store things you can see but the scraper gets blocked on.
One question, what's your stance on adding a way to mark articles as read or "archive" them like other apps that are branded a bit more as storing things to read later. You can technically do something similar with tags but it's a bit clunky of a UX.
Thanks! At the moment we’re focused on archiving rather than read-later workflows, but this is great feedback. I’ve already added it to the feature requests list.
Archival is one side of the coin, but consumption as-in read-later is very important as well.
I am currently evaluating Linkwarden, Wallabag, Hoarder, Linkding and each of the services has pro and cons making it hard for me to choose one. Linkwarden is AWESOME in its way to store content in multiple formats, but the read-later wfs could be improved.
Without checking again: does Linkwarden sync reading location across devices and automatically scrolls to that location on the next device? Does it tell me how „long“ an article takes to read (solely based on the length of it)? Does Linkding support marking up text and persist (mark some text yellow and see those marks somewhere or even add comments or favorite specific parts of texts).
No need to answer any of the questions, I can research myself, just putting these out there for a read-later solution I would like. Add a link on my mobile device, Linkwarden could do its magic in the backend, and I check out the content later on desktop or even on my mobile device.
> with the singlefile extension it's pretty easy to store things you can see but the scraper gets blocked on
FWIW, at least on iOS, it's possible to inject Javascript into the web site being currently displayed by Safari as a side effect of sharing a web link to an app via the share sheet.
Several "read it later" style apps use this successfully to get around paywalls (assuming you've paid yourself) and other robot blockers. Any plans for Linkwarden to do this (or does it already)?
That's cool, but also requires using the Singlefile extension (and granting it access), right?
What I like about the share sheet JS method is that it doesn't get access to most of my browsing sessions. (The shared-to app getting access to my browser session is somewhat unexpected, though.)
OpenRouter is pretty great but I think litellm does a very good job and it's not a platform middle man, just a python library. That being said, I have tried it with the deep think models.
Part of OpenRouter's appeal to me is precisely that it is a middle man. I don't want to create accounts on every provider, and juggle all the API keys myself. I suppose this increases my exposure, but I trust all these providers and proxies the same (i.e. not at all), so I'm careful about the data I give them to begin with.
Unfortunately that's ending with mandatory-BYOK from the model vendors. They're starting to require that you BYOK to force you through their arbitrary+capricious onboarding process.
Did you consider adding cron jobs or similar or just sticking to the heartbeat? I ask because the cron system on openclaw feels very complex and unreliable.
reply