plus one, I would love to configure a folder of markdown/txt(+ eventually images and pdfs) files that this can have access to. Ideally it could RAG over them in a sensible way. Would love to help support this!
Thank you! I'd love to learn more about your use cases. Would you mind sending an email to feedback@recurse.chat or DM me on https://x.com/chxy to get the conversation started?
touchscreens don't have to be small. one of the only pie menus I can really think of in the wild is Adobe Illustrator on iPad, which is relatively interesting because its an "ipad first" app of sorts. its separate than their desktop apps, and was designed for the larger tablets, not a small phone.
the menu itself is pretty good, especially with the Apple Pencil, which you'd be using to draw on the iPad. Image editing/3d modeling software tends to need a lot of UI, and I think it makes sense for the most part. these tools are hopefully used by everyone. that means more sporadic use — if I'm only opening your app a couple times a week for a couple minutes, I probably won't remember the keybaord shortcuts. not to mention people who are unfamiliar or don't use keyboard shortcuts at all. anyways, bit of a rant since it doesn't answer your original question, but we should consider how to make our computers computable by all users.
I wandered into the comments to find or write the correct "before times" bit, and I think this covers everything I would've mentioned.
I'll add that looking back, EXT seemed to be a bit ahead of its time. Its data/table view rivals AG Grid [0] of today. If we could've just standardized on a table view by now, but alas.
I agree! I'm the creator of phonetonote [1], which tries to integrate with different tools for thought. I just started a `tft-interop` repo [2] with similar goals. We're just getting started thinking through how to make the TFT structures (edn mostly) more interoperable. I'm not personally an org-mode user, but agree it could be a good format to parse these trees in and out of. I've mostly been thinking about OPML so far. Feel free to hop into the discussions where we're sorting through these ideas — https://github.com/phonetonote/tft-interop/discussions/2
edit: in case anyone knows, I see this monitor "requires two DisplayPorts" for full 8k. Does anyone know if I can plug two display ports into a docking station, and one cord out of the docking station into my 14" m1 mbp? Ideally this would also charge the mbp. Is this possible? If I were to buy such an expensive monitor, I really only want one cord.
I'm sure you can get it to work at some lower res/refresh rate than what its designed for. But that monitor is DP 1.4 dual link because it needs more than the 32Gbit one gets out of a single DP 1.4 cable to run at 60Hz. So if your happy with 8K@30Hz and your mac can provide DP 1.4 it might work with a single cable. And from what I know of Mac's your probably out of luck except for the latest M1 models which support TB4 and the higher data rate DPs.
That said, the easiest way to get this working is probably to get one of the TB->PCIe expander chassis and plug in an external GPU and let it drive the display.
Desktop PC's/workstations still have their place, and driving multiple high resolution monitors is one of them.
PS: Been drooling over that monitor for the past couple years as an upgrade to my dell 5K's I picked up when apple released their first standalone 5k monitor and more than a few high end mac users apparently ebay'ed their dell monitors to get the apple version. Their loss, my gain... :) Hey apple, why don't you release a 8K monitor? Lol.
(PS: There are a couple other manufactures putting that panel in monitors (viewsonic for one), so its not just dell, and a bunch of 8K tv's if you want higher resolution).
thanks, "TB->PCIe expander chassis" wasn't on my radar at all! I'm holding out that apple will release something better than the Studio Display in the next 6-9 months and make some of this a bit easier.
I tried using are.na and it just didn't stick for whatever reason. Kinopio on the other hand, I wanted to use it more and more once I started. Just suited my brain better I suppose.
`Baas` as a term might be dead, but `JAMStack`, which Netlify invented [0] is alive and perhaps thriving -- it's a bit hard to say. Maybe not the same exact concept, but it seems similar.
I'm afraid this won't be useful in the real world. API consumers who continue to use legacy endpoints after being told not to are unlikely to update their code to listen to a new HTTP header. This strikes me as a great idea in theory, but unlikely to be useful to websites actually looking to deprecate endpoints.
I don’t think this is intended to be about endpoints, but rather about the resources under an endpoint. E.g., “this image will be deleted from this image-hosting service in 30 days” or “this is a link to an item in your Dropbox Trash folder, and the Trash is emptied every 48 hours” or even “this is a temporary share link and will work for 24 hours.”
Given these use-cases, I could also see the use of a version of the header that doesn’t specify when the retirement of the resource will happen, but just specifies that the resource is, by design, not going to stick around forever. E.g. the URL of a “previous version” of something, where the system only keeps around N previous versions (so as soon as someone adds enough newer versions, the version you’ve linked to will disappear.)
Another fun use-case is sticking this header on everything on a given domain (by e.g. reconfiguring your web load-balancer to emit the header.) Archive.org could then use this as a signal to automatically prioritize archiving content from the domain, before any human being realizes the service is being retired and prioritizes that archiving.
