For any Stardew Valley players using the Stardew Access mod, how do you drop an item you're carrying? By mistake, I managed to pick up the bed in my house, but am not sure how to drop it. I bring up the inventory with E, move to the bed, press Left Bracket until it says "Empty", then move all the way to the Drop button and press Left Bracket. At that point, I hear a descending noise, what sounds like footsteps, then I appear to be holding the item again. What am I doing wrong?

nvdaComposer share

Sensitive content

A “phonemeSource” tag in the frontend handle + PassContext. hmm. Default it to "espeak" (so nothing changes today), but allow callers to set it. Yes. Add a new optional API (non-breaking) like: nvspFrontend_setPhonemeSource(handle, "espeak") Store it in the handle state. Pass it into PassContext so every pass can check it. This way we get different types of passes for different phonemizers if we wanted, rather than making this thing so central to ESpeak. Hmm. Maybe that would make me feel better.

🗓️ 2024‑11‑08 • #Android #Privacy #Security

Here’s a quick showdown if you’re thinking of leaving proprietary Android behind:

Murena / e‑OS (Fairphone 4):

Price: €449‑€499
CPU: Snapdragon 750G (≈ 1.9 k Geekbench multi) – decent but slower
GPU: Adreno 619 (≈ 1.1 TFLOPS)
RAM/Storage: 6 / 8 GB RAM, UFS 2.1
Security: Standard verified boot, no dedicated security chip
Updates: Depends on LineageOS – often lagging behind Google’s patches
Pros: Modular, repair‑friendly, microG gives partial Play‑Services compatibility

Graphene OS on Pixal 7: (You could use any Pixal phone from the 4 up to the pixal 10 fold and Tablet)

Price: $599 (~€560)
CPU: Google Tensor G2 (≈ 3.4 k Geekbench multi) – ~2× faster than Murena
GPU: Mali‑G710 MP7 (good for everyday gaming)
RAM/Storage: 8 GB RAM, UFS 3.1
Security: Titan M2 security co‑processor + hardware‑backed keystore, verified boot, attestation
Updates: Monthly security patches, 5 years guaranteed
Pros: Strongest hardware‑rooted security on a consumer phone, pure Android stack (no Google services when using Graphene OS)
Why switch?

Better hardware trust – Titan M2 beats standard boot‑loaders.
Faster updates – stay protected without waiting for LineageOS.
Higher performance – smoother multitasking & AI tasks.
True de‑Googling – Graphene OS runs a clean, auditable Android fork.
💭 If you value privacy and solid performance, the Pixel 7 + Graphene OS is the more compelling upgrade, even at a modest price premium.

#OpenSource #grapheneos #fairphone #degoogle #dataprivacy
@grapheneos @e_foundation 🔗 grapheneos.org / e.foundation

in reply to GrapheneOS

GrapheneOS is a privacy and security hardened OS greatly improving those compared to the Android Open Source Project. /e/ is the opposite of that and is a far worse option than an iPhone for privacy and security. /e/ is not at all a safe option and it's not a legitimate a privacy project despite being marketed as one. No privacy project it telling users to use their supposedly private speech-to-text service which actually sends their sensitive speech data to OpenAI and much more.
in reply to GrapheneOS

Strong recommend reading discuss.grapheneos.org/d/24134… and the third party sources linked in there including the posts from Divested Computing, Mike Kuketz and the comparison from Eylenburg.

If you care at all about privacy and security, avoid /e/ and avoid Fairphones. Use an iPhone if you want a device with solid privacy and security without thinking about it. Don't fall for the false marketing of these phony privacy and security products. No device Murena sells is at all safe to use.

#fosdem2026 was another awesome success for the open source community this year. I had a blast showing off what all we do at BlissLabs and what all is possible for the Android community. Got to finally put a face to so many of the people I have collaborated with over the years, and I can't wait to come back!!
Special shout out to @IzzyOnDroid , @shiftphones and @bene64 for helping show what an Open and Sustainable Ecosystem for Android could look like - From Hardware to Apps. You all rocked!!

reshared this

Honestly the biggest problem with #AI coding is that it lets me build things without having to think about what I want to build. It's happened twice now where the AI coded something perfectly, only for me to realize when I had exactly what I asked for, it wasn't what I needed or really wanted. I usually realize this during the act of building, and the act of building often helps me clarify what it is that I actually want.
#AI
in reply to x0

@x0 it's interesting, Jess was telling me how "classic pitch" reminds them of the Braille & Speak, which is maybe why people asked for it back. But it's something about the way it stresses and intonates words, and then realizing that creating phonetic rules and normalizations that "fight Espeak's rules" will mean later troubles when switching to something new. I'm being pulled in two directions over it and it's a bit distraughtful. We can kind of "cheat" the system with multilingualness by using ESpeak, sure, but we're also locked into what it outputs and redefining it. Sure, we can write our own G2P layer, but then all hands off and new languages actually become harder to map out in some ways because lexicons and tables need to be added by ourselves. Ugh.
@x0