I bought the InkPalm a while back, and the Palma recently. (Note: I have a "thing" when it comes to e-Ink devices and so tend to just pull the trigger on new interesting ones when they come out.)
They're superficially similar, but the InkPalm feels like a very limited device by comparison. No Play Store, slower refresh, much older Android build, and a mostly-Chinese localized UI with partial English translation.
If you really just need a basic e-reader that can handle MOBI and ePub files and are willing to put up with a somewhat frustrating experience, the InkPalm is fine. OTOH, if you spend a lot of time reading long-form text but also want to occasionally run other apps -- Termux in particular is a pretty great tool to have on a small e-Ink device when paired with a small BT keyboard -- the Palma is meaningfully better.
The official unemployment rate is calculated by the Bureau of Labor Statistics by surveying a representative sample of US households, not a literal count of people "on the job hunt": https://www.bls.gov/cps/cps_htgm.htm
So while you should expect the numbers to broadly track together, there can and will be some variance month-over-month in the impact and durability of new jobs' contribution to the overall level of employment.
Because the benefits of side loading on iOS are so massive that everyone will use it i.e. you can use private APIs, bypass Apple's privacy controls, implement device tracking, harvest data e.g. contacts.
It's going to be a huge transfer of power and wealth back to the likes of Meta, Epic etc
I’m happy with the one that doesn’t allow crypto crap.
Also free speech is a practical impossibility. Standard email is a free as it gets and it turns out nobody wants that because if you have completely free speech your inbox gets spammed into oblivion. Everyone draws the line somewhere.
People really like to use the slippery slope argument to mean "I took the most expansive interpretation of what someone did throwing away all context and came up with the worst possible thing they could do with that."
That's because if a bad actor was given the opportunity to make a lot of money doing the worst possible thing they could do with something someone will do that thing eventually 100% of the time, no exceptions. This isn't even an "Only siths deal in absolutes" scenario either.
There are plenty of people in the world who will do anything in this world for money, power, wealth, and control over people and they don't care who they hurt in the process of achieving that goal.
And? A bad actor that has power by fiat over you doesn't need a slippery slope to do bad things, they can just go and do them.
Case in point - Reddit's enshittification. Spez has decided that Reddit will now be a walled garden, and all you can do is take it or leave it.
Slippery slope arguments provide exactly zero guidance for as to when it is reasonable to stop going down the slope, which is what makes them utterly useless.
I replied to this comment and I'm sufficiently happy with my explanation. What's disagreeable about my statement in the context of answering the parent's question?
> People really like to use the slippery slope argument to mean "I took the most expansive interpretation of what someone did throwing away all context and came up with the worst possible thing they could do with that."
The point where you don't go down the slope is when you recognize it and you don't know what is at the end of it's long tail. The guidance is built in.
"We can't have police, this will lead to a slippery slope that will lead to a 1984 police state."
"We can't not have police, this will lead to a slippery slope that will lead to Mad Max anarchy and roaming bands of killers and warlords riding in really awesome-looking semis."
That's the entire problem with the slippery slope! Two entirely conflicting, equally compelling arguments can be construed with it, starting from the same simple question - "Should there be police? Yes/No?"
Just because the bottom of a slippery slope looks awful, or can't be seen isn't a reason to do, or not do something - because I can construct a million awful slippery slopes for any action you do, or not do.
A slippery slope argument eliminates all nuance from a question, and provides no guidance for answering it well. That's exactly what makes it a logical fallacy.
> Just because the bottom of a slippery slope looks awful, or can't be seen isn't a reason to do, or not do something - because I can construct a million awful slippery slopes for any action you do, or not do.
Who said anything about using a slippery slope for the _only_ justification to do or not do anything?
You said "Slippery slope arguments provide exactly zero guidance for as to when it is reasonable to stop going down the slope, which is what makes them utterly useless" and I disagree that they're utterly useless. Sure, it doesn't provide guidance. Why does it need to? As you go down the slippery slope you learn about the possibilities you should consider. You also learn about the possibilities you can ignore. It's a risk assessment tool and it's incredibly useful.
I'm not sure how you can deny that putting all the chips on the table, thinking about, and debating all the possibilities has no benefit when you're assessing an idea or an action to take. There's nothing wrong with _considering_ possibilities and going down the slippery slope. It's often a very useful exercise.
There's a thing some people seem to be unable to understand, and it's that... coming after bad things can be good, actually.
The thing about the "first they came" poem is that attacking the socialists, trade unionists and jews is already bad. There's a reason it doesn't start with "first they came for the murderers, but I didn't say anything because I wasn't a murderer".
The poem urges us to stand up against injustice even if it doesn't affect us directly. The poem doesn't argue that all slopes are slippery.
> There's a thing some people seem to be unable to understand, and it's that... coming after bad things can be good, actually.
Going after bad things can be good, but going after a developer who wants to be tipped in crypto isn't a bad thing. Apple being able to take down an app because it allows the user to monetarily reward a developer in the way the dev chooses *is* a bad thing.
> allows the user to monetarily reward a developer in the way the dev chooses is a bad thing
I honestly don't believe anyone can argue this in good faith. First off it's not user->developer but user->user and second "the way the dev [or user] chooses" is just silly. At the end of the day people want fiat currencies, Bitcoin (or any other crypto) in this case is clearly meant as a way to bypass the app store cut. It's not because "they really wanted bitcoin", no, they wanted a loophole. We can argue about if Apple/Google deserve 30% but pretending people actually want crypto for any reason other than avoid rules/regulations is silly.
> We can argue about if Apple/Google deserve 30% but pretending people actually want crypto for any reason other than avoid rules/regulations is silly.
> I have a PornHub subscription that uses bitcoin. There's nothing speculative about it and it's completely legitimate. I've also used to to purchase indie games instead of giving Steam/Google/Apple/Epic a cut. I'm looking for a Spotify alternative and this seems to fit the bill and I'd give OP some bitcoin to check it out.
> Just because viable usecases don't exist today isn't proof that they'll never exist and isn't a reason to stop development. If we gave up on hard problems because we didn't solve them in 15 years we wouldn't have the AI we have today.
Can you please explain to me how my use of crypto is avoiding rules/regulations? I don't wish to be silly or have pretend intentions.
Is there a rule that says all developers have to put their games on Steam or Epic and accept local currency that I'm trying to avoid? Is there a rule that says developers can't sell their games for apples? What rules/regulations would a developer avoid by accepting apples as payment for their work?
Now extend this to people who are creating videos and want to create their an iOS app that will allow them to accept apples as payment. What makes crypto special?
Apple's 30% cut is not a real rule, I'm sorry. It doesn't bring any good in the world and it doesn't help anybody except Apple. Apple and Apple's supporters care about the rule but that doesn't make it a valid rule or something the rest of us have to sit back and accept. Using crypto to avoid Apple's fees isn't hurting anybody except the poor old multi-trillion dollar company named Apple. If you want to talk about people pretending let's talk about how many people pretend like Apple is a good guy or how people pretend like Apple cares about them on an individual level. It's as delusional as walking into a strip club and walking out thinking the stripper you paid $300 for a lap dance for loves you and wants to see you again because they care about you on an individual level.
It's also fully within someone's rights to put their foot down and fight Apple on this. There's nothing wrong with that and the US legal system allows for it. You can be a bully and tell people to pick up their ball and go somewhere else when they're in "your park" but one day someone is gonna punch you in the mouth and tell you to sod off when they see you let everyone else play there with different rules. Apple is going to lose their 30% cut in the very near future, they know it, and they're terrified.
If you wanna argue that going after cryptocurrency is a bad thing, make that argument. Don't just use the poem to make a lazy slippery slope argument.
And apparently, this isn't even about cryptocurrency but Apple's normal 30% tax. If that's true, then it means that the lazy slippery slope argument is even less applicable.
It's absolutely wild to me to see someone take a poem about the genocide of millions of people and apply it to an app being banned from a digital store over cryptocurrency tipping.
You’re saying that Bitcoin is “crypto crap”, or just talking in general?
And regarding the “free speech” topic, you’re saying that’s ok not finding new censorship resistant solution because essentially censorship is ok?
Just asking to better understand the underlying knowledge on the topic before putting myself into this valley of tears.
> if you have completely free speech your inbox gets spammed into oblivion.
Don't know for your provider, but on Gmail, I click on Spam and there are all there. It's not censorship, it's sorting. I usually go see them once a month, just in case something got badly sorted (it's also quite entertaining to see the scams attempts).
In what world is it censorship to choose to read something or not too? It may be censorship for sure that something is blocked (and still can be argued upon), but choosing not to read crap is not censorship, just like choosing not to read every scientific papers in the world is not censorship…
Since it sounds like very few folks in this thread have actually fired up Spin and built a thing, I thought I might offer a few observations based on my experience working on a little app over the last 2-3 weeks.
First, the good stuff:
- As a Rust developer, the SDK tooling is really good. I went from running the installer to generating a templated app to dropping in my own app logic in about 15 minutes.
- Local development iteration is also very fast and low-friction. Building everything as small WASM components means you effectively get hot module reloading for free, without needing to shim in a bunch of extra dev-mode-only code loading logic (with all the inherent incompatibilities and heisenbugs)
- The component reuse model feels a lot easier for me to reason than interminable chains of Express middleware (YMMV, of course)
- You get actual static (WASM) binaries, which can be as small as your compiler makes them. I'm normally pretty thrilled to get a production app container down to <100MB, and the app I've been working on, even without really paying any attention to my dependency graph, is around 2MB. Storage may be cheap, but pulling ~GBs of new container layers for a given release or deployment isn't free or instantaneous.
There are some less-great things:
- The "outbound" DB adapters are _very_ bare-bones. You only have access to a small list of datatypes, and you can't really layer higher-level libraries on top b/c the APIs aren't compatible with standard backend drivers. (Furthermore, if you want to use e.g. MongoDB, Clickhouse, Dynamo, etc., etc.: sorry, I hope you have some sort of HTTP adapter lying around ready to use.)
- WIT (WebAssembly Interface Types) is a cool _emerging_ standard, but like a lot of WAS* community stuff it's still in a fractured "draft" state, and many of the actual interfaces exposed in Spin are unique to their runtime. (This also means that _extending_ something like the PG bindings requires a ton of indirection code spelunking; I gave up trying to add a few new native types after realizing I would also have to support them for MySQL and every other backend DB.)
- The development environment, while relatively complete and usable on its own, doesn't really play nice with Nix or other high-level dev environment tooling. (There are literally invocations of `rustup` inside the top-level `build.rs` for the project, so good luck providing your own paths for e.g. `rustc`.)
On balance, I'm enjoying the experience thus far and starting to think about more thing-ish was to apply the tools. I'm also looking forward to trying out more of the self-hosted infrastructure stack. I'm not opposed to paying for managed hosting, but I do occasionally build things that need to run in "offline" or air-gapped environments, so being able to bring up a full hosting environment is pretty clutch.
If you have Node apps running in Lambda and are happy with the architecture, cost, and operating model: great! You've done good work and/or are very lucky and there's no need for you to rip everything out and start over.
Heck, even if you're curious about WASM and want to try some experiments with (say) fast Rust crypto libraries or embedded database engines w/o the risk of flaky native code crashing your V8 runtime: again, you can just run WASM from a Node worker thread and keep cruisin'.
For those of us who _don't_ have a huge investment in Node, have hard requirements around e.g. memory usage, cold start times, or even just plain old _cost_ (which can become a major factor when you consider the AWS lock-in) that Lambda doesn't meet really benefit from another option.
Your good fortune in finding a stack that works well doesn't mean that folks who have different needs or constraints are dumb, ignorant, or lazy.
As an aside, I think you also might be underestimating the depth of experience and knowledge of the Fermyon crew when it comes to containers, cloud runtimes, and serverless development. This is substantially the same team that built Helm, and a lot of other Kubernetes and cloud-native ecosystem projects along the way.
Neon at least has open-sourced their core offering, which provides a migration path for folks who make bigger bets on their platform. So yeah, there's every possibility they'll go away at some point, but unlike a lot of SaaS offerings, it's all Postgres over the wire and under the hood, so you have plenty of migration options (OSS, another managed Postgres vendor, Aurora, Cloud SQL, etc.)
Neon CEO here. Definitely. Of course Neon storage is a distributed system and you need to know how to run it. But a) we can help b) Percona is a trusted partner of us that can support self hosting for you.
...because they're constantly being raked over the coals for being "biased", "liberal", and (now, conveniently thanks to Musk in large part): "state-controlled" perhaps?
If news events depict one side of the political spectrum unfavorably, "balanced" reporting plays directly into the agenda of that side. Truthful reporting of the news shouldn't always mean "all sides have valid arguments," and yet that is what our current media climate demands.
Sony, Nikon, and Canon already offer this for select "pro" cameras, specifically for law enforcement use.
Having unforgeable signatures on every image-capture device just in case some output file could be submitted as evidence in a civil case would be a privacy and safety _nightmare_, OTOH.
ZeroTier lets you build modern, secure multi-point virtualized networks of almost any type. From robust peer-to-peer networking to multi-cloud mesh infrastructure, we enable global connectivity with the simplicity of a local network. We have millions of active users with hundreds of millions of devices connected to their own private mesh networks.
We're looking for data/analytics and UI engineers who want to work at the intersection of networking, security, and usability, helping an amazing community of open source and commercial users. You'll be joining a fully-distributed team of ~12 (total; six in eng) with backgrounds in Linux networking, cloud ops, cryptography, and cross-platform product development and delivery.
I'm the head of engineering + hiring manager so if you have questions about the company, product, or roles, feel free to reach out directly: lennon.day.reynolds@zerotier.com
(We unfortunately can't sponsor visas or hire internationally at this point, so these are US-only positions.)
They're superficially similar, but the InkPalm feels like a very limited device by comparison. No Play Store, slower refresh, much older Android build, and a mostly-Chinese localized UI with partial English translation.
If you really just need a basic e-reader that can handle MOBI and ePub files and are willing to put up with a somewhat frustrating experience, the InkPalm is fine. OTOH, if you spend a lot of time reading long-form text but also want to occasionally run other apps -- Termux in particular is a pretty great tool to have on a small e-Ink device when paired with a small BT keyboard -- the Palma is meaningfully better.