Working on a little project to make Spotify recommendations better.
You get to choose the genres you're interested in, and it creates playlists from the music in your library. They get updated every day - think a better version of the Daily Mixes. You can add some advanced filters as well, if you really want to customise what music you'll get.
Neon — Ship Faster with Postgres (https://neon.tech) | Remote | Full Time
Neon is distributed team building open-source, cloud-native Postgres. We are a well-funded startup with deep knowledge of Postgres internals and decades of experience building databases. Our storage layer is written in Rust, and our cloud control plane is written in Go. We are on a mission to enable developers to “Ship faster with Postgres”.
We are hiring for a few positions:
* Software Engineer, Developer Productivity
I run a personal finance app that's built as a PWA (https://tender.run, my email is in my profile).
I would say running as a PWA has been a mixed bag. There are quite a few missing features across web platforms (for starters, background sync, full featured push notifications, haptics) that make it hard to be competitive with native apps. Every WWDC, we watch in hopes that Safari gets more PWA features, but it's a thin drip. There's a reason so many apps repackage into electron/cordova/whatever shells.
As other folks in thread have pointed out, it's probably worth thinking through why a product works particularly as a PWA vs alternative distribution methods.
If you’re looking for a new GPU cloud because of this, we’ve put all these providers in on place, console, and API so you can find a new one for your needs at https://shadeform.ai
I've been working on a local-first personal finance/expense tracker called Tender: https://tender.run
Tender runs as a PWA and uses the Automerge crdt and sqlite via wasm. The app more or less runs entirely in your browser (works offline!), though our server proxies connections to pull in plaid/splitwise data.
Feature-wise, we're targeting folks who do want to manage their expenses but not have to do fine-grained budgeting. There's tools for tracking getting paid back and a splitwise integration as well. The app is desktop-centric right now, but we're working on getting a good mobile workflow together too.
Since everything is browser-based, it was actually quite easy to get a demo sandbox environment working. You can give it a quick spin here: https://demo.tender.run
Lots of what the article talks about pertains to the difference between a 'full DE' and 'just a WM'. Gnome and KDE fall in the first category. They have a notification system, lockscreens, app launcher, etc by default. Hyprland doesn't. It puts windows on your screen and allows you to control their layout, everything beyond that, you can add yourself.
This article mentions dunst for notifications, Rofi for app launchers, Waybar for a status bar, swaylock for screen locking, ... I've been having a great time using just AGS [0]. AGS, at its core, is a framework to write all of those tools. It is based on the same technology that Gnome Shell uses, i.e. GJS. You can build up all of the widgets you want and need using Gtk and replace all of the tools I mentioned before. But be warned: AGS only provides you with the libraries you need, you'll still need to build the UI yourself. Unless you copy someone else's configuration of course ;)
Hey HN, the engineering team at Bluesky is especially excited to get to this point! We're happy to help answer questions and help anyone trying to run their own PDS host. Things should work pretty well for self-hosters right now, but we're standing by to help if there are any problems.
For anyone who's interested, there's a group of us dedicated to natural myopia reduction at reducedlens.org, which is a free and open-source fork of endmyopia. I've even started measuring my axial length to try and get better data on if this stuff actually works (only one measurement so far though, so nothing interesting yet).
The nature paper was pretty crazy. Basically because blue bends more than red (think of a prism), it also focuses a bit sooner. This phenomenon is known as longitudinal chromatic aberration, or LCA for short. This means if you're myopic, blue might be more blurry than red, and vice-versa if you're hyperopic. The researchers in the nature paper had participants watch a movie where they straight-up blurred the blue or red with software, in order to produce fake LCA signals. They found the participants axial lengths still shortened or lengthened anyway in response.
I mean, this is the company where the only security certification advertised on their website for macOS [1][2] only achieved the lowest possible level of security, EAL1.
A level only fit for products where [3]: "some confidence in correct operation is required, but the threats to security are not viewed as serious" which is one level lower than "demonstrating resistance to penetration attackers with a basic attack potential" [4]. Which is four full levels below "demonstrating resistance to penetration attackers with a moderate attack potential" [5].
Apple has never once, over multiple decades of failed attempts, demonstrated "resistance to penetration attackers with a moderate attack potential" for any product. It should be no surprise that the systems, processes, and people who lack the knowledge, ability, technology, and experience to make a system resistant to moderate attackers, despite nearly unlimited resources, have the security of their systems completely defeated by moderate attacks like small groups of skilled researchers. Apple positively, absolutely, 100%, certifies they can not. Though, it would be nice if their marketing were restricted to what their engineering can prove.
You don't need so many layers of stuff (or API keys, signups, or other nonsense).
Llama.cpp (to serve the model) + the Continue VS Code extension are enough.
The rough list of steps to do so are:
Part A: Install llama.cpp and get it to serve the model:
--------------------------------------------------------
1. Install the llama.cpp repo and run make.
2. Download the relevant model (e.g. wizardcoder-python-34b-v1.0.Q4_K_S.gguf).
3. Run the llama.cpp server (e.g., ./server -t 8 -m models/wizardcoder-python-34b-v1.0.Q4_K_S.gguf -c 16384 --mlock).
4. Run the OpenAI like API server [also included in llama.cpp] (e.g., python ./examples/server/api_like_OAI.py).
Part B: Install Continue and connect it to llama.cpp's OpenAI like API:
-----------------------------------------------------------------------
5. Install the Continue extension in VS Code.
6. In the Continue extension's sidebar, click through the tutorial and then type /config to access the configuration.
7. In the Continue configuration, add "from continuedev.src.continuedev.libs.llm.ggml import GGML" at the top of the file.
8. In the Continue configuration, replace lines 57 to 62 (or around) with:
models=Models(
default=GGML(
max_context_length=16384,
server_url="http://localhost:8081"
)
),
9. Restart VS Code, and enjoy!
You can access your local coding LLM through the Continue sidebar now.
We provide both bun and deno as typescript runtimes for windmill.dev (oss retool alternative) and we get overwhelming feedback that people are confused by the little changes required to adapt to deno and would rather just stick to the node.js mode aka bun. Now that bun is getting close to 1:1 node.js support, I predict we will see a lot more bun everywhere.
@Jarred was super responsive to help me adapt bun to our distributed cache storage, so all props to him.
I mean, ps2pdf be with you (it ships with Ghostscript), or, if you must, use a Web service[1]. PostScript was fairly common for papers before PDFTeX and while Adobe still attempted to control PDF using their patents.
That said, the System P₂ papers might be more helpful[2,3]. The System P paper[4] is indeed more about the inference algorithm and less about the motivation—perhaps the accompanying slides[5] will help some, alongside the first two papers?
I think this depends on how you interpret it. All the docs[0] say are:
> Patterns which should be version-controlled and distributed to other repositories via clone (i.e., files that all developers will want to ignore) should go into a .gitignore file.
and
> Patterns which are specific to a particular repository but which do not need to be shared with other related repositories (e.g., auxiliary files that live inside the repository but are specific to one user’s workflow) should go into the $GIT_DIR/info/exclude file.
To me it seems obvious that all developers would want to ignore .DS_Store even if only some of them would generate it. And certainly you want it distributed to other mac users when they clone. Further, it's certainly not the case that .DS_Store is specific to just one user's workflow. On all three cases therefore gitignore would be reasonably appropriate.
This is because you have forgotten to return a `Vary: Origin` header in the response. If you don’t do this, caches will presume the response is the same regardless of the Origin header in the request and so you will get the bug you describe.
> Do not fall into the trap of anthropomorphising Larry Ellison. You need to think of Larry Ellison the way you think of a lawnmower. You don't anthropomorphize your lawnmower, the lawnmower just mows the lawn, you stick your hand in there and it'll chop it off, the end. You don't think 'oh, the lawnmower hates me' -- lawnmower doesn't give a shit about you, lawnmower can't hate you. Don't anthropomorphize the lawnmower. Don't fall into that trap about Oracle. — Brian Cantrill (https://youtu.be/-zRN7XLCRhc?t=33m1s)
HAMT: Hash Array Mapped Trie. This data structure makes efficient immutable data possible. You can update a list of a million items, and keep a reference to the original list, by changing 3 or 4 references and some bytes.
This should replace copy-on-write for scripting languages. I really want to see it in a JS spec soon. There are libraries that can do it, but they add translation penalties and extra steps. I’d complain less if I could use Clojurescript professionally, because it and Clojure are built around them.
There was recently a thread about someone asking about password management solutions for an organization of 10k employees, and someone recommended 1Password, which I already find hard to believe it could ever make financial and operational sense. [0]
Now, these prices from GH can make sense if you are a team of 10-50, but I wonder what would be the point where it wouldn't take a bean-counter to say "can't we just hire someone else do that in-house, part-time? It would cost as much or less, but at least we would have a lot more control over the system and we wouldn't be at the mercy of a company that treats us as cattle."
I see on your profile page you are on Matrix. Would you mind if I add you there to chat (or add me @raphael:communick.com)? Seems like your company could have so many different cheaper and better solutions for their needs, I've been thinking for a while whether there could be a market in "open source strategy consulting".
It's a handful of commands because git-cam and git-wip referenced other little utility scripts, so hopefully I got them all. Probably it would be easy to rewrite to be standalone.
I'm on a mac, and I have ripgrep installed as "rg". Ymmv, glhf :-)
So:
"git cam" commits everything with message "nt"
"git wip" undoes all the nt commits but leaves the results staged, ready to be commited as a single properly worded commit (or play w/ what's staged and do as several commits)
You get to choose the genres you're interested in, and it creates playlists from the music in your library. They get updated every day - think a better version of the Daily Mixes. You can add some advanced filters as well, if you really want to customise what music you'll get.
https://riffradar.org/