Suita; just lol. But srsly, the combination of a shitcoin and referral begging is a natural fit, so it’s no wonder after all. #enshittification

Step 0: stop fucking begging me for spreading a referral disease. #enshittification

TIL that Lenovo is manufacturing a mouse (model 400) that isn’t compatible with Linux. Even if the receiver is simply plugged into a USB‑C port, it blocks the boot process. Incredible, what a shitty product. I’ve never encountered a mouse that’s unusable right out of the box. How does something like this even make it to the retail? #enshittification

@Minibits for wallet address - how is the name reserved, for how long? I mean what if user stop using the wallet (delete app), or decide to change the name. The old name is with some expiration, or can it be reused by someone later on? Or once it's created, there is no way someone can take it? (Same as with most email providers, gatekeeping the address so someone can't impersonate.) *I suppose the custom address doesn't have different rules from the generic one.

Something not working right with njump lately (maybe this started after the last CF outage). njump.me as info page is working all the time. But with a /nevent1, a lot of request ending as: Usually one simple refresh of the page finishing ok. I'm not the only one so far. @fiatjaf

idk 'AI-Powered', just why

At least Tuta does have interesting captchas View quoted note →

#rant #fcuk I needed to create an account, a semi-public one tied to another public account within legacy data silos (aka GH and alike). Which required an email address. It wasn't meant to be a super-secret anonymous or pseudonymous account, as it would be publicly exposed anyway. Decided to try Tuta to see what they offered compared to the basic ProtonMail service for this case. Not liking the Proton monopoly in the space much anyway. When created the account, Tuta put a 24-hour hold on it for manual approval. After the time elapsed, they informed me that I had to contact them with a written email to explain what I planned to use it for. Did that, and on the third day, the account started working. Tested by sending an email to it, and since didn't receive a bounce-back message about an unreachable mailbox, began using it for my intended purpose. A day later, after I had already created accounts with several other services using this Tuta email, the Tuta login screen showed me only a "Too many failed login attempts" error. After waiting about an hour, a new message popped up: "Invalid login credentials." They did it, bastards. Tuta nuked my new account, the one they manually approved, within a day of use, giving me no chance to react. God forbid they let me verify* myself with: a payment, a phone number, or another email (which I had to use anyway to migrate my accounts later on). It was my first time using Tuta, so, not knowing how they operate, I didn't set up any recovery options besides saving the recovery code. Didn't add a phone number or a secondary email. Maybe this could prevent some abuse detection, who knows. Imagine if the services I signed up for didn't let me easily change the email to a backup address. What a fuck-up. Really didn't expect this kind of rug pull. (F*ck email anyway.) *well rather validate as non bot, verify is not much a case as phone/payment/secondary mail is cheap to bypass - yet still a quite effective.

@Amber have question - can this notification be completely avoided by switching it off (the 'Service' notification) in settings and let Amber work on background? Or is it necessary to keep Amber somehow in working state. The list is still rolled out and it taking a lot of space in notification area. Have unrestricted and run on background allowed for battery.

While posting a bit here, I realized that do not know one crucial thing about Nostr. When referring to a Nostr note, should I use the ‘nostr:nevent1’ format or the ‘note1’ format? What is the difference, if any? As far as I know, ‘note1’ is a shortened version of the long string. It just happened that I have many favorite notes in the nevent1 format and completely forgot about it until looking at what I'm actually inputting into the client. #asknostr

This is some steak saving advice View quoted note →

Still @Amber is the best and only usable solution known to me (for Android) keeping nsec usable (outside of passwd manager) yet quite safe. And also not that hard to use for an average user. The ongoing problem is clients not respecting the user’s choice. For example, YakiHonne doesn’t respect the push‑notification decline and cannot let me leave the app if I do not confirm it. Sometimes there are many requests for one event. 0xChat asked me for many confirmations for a single message iirc; I have no idea what I’m signing for, so blindly confirming them all. View quoted note →

Still haven't figured out how to choose a 'good relay' and what it is even. In Amethyst, at least, there is nice description what each type of relay is good for. Except for @Citrine (many thanks @greenart7c3 ), that is by design a good relay. View quoted note →

@M¡lan this may be interesting for you View article →

This guide still holds great. Surprised how not many users (even the technically knowledgeable base of nostr) taking advantage of having npub personalized a bit. Possibly because it's not just a common knowledge. Or maybe, as NOSTR clients tend to shorten the npub, it's mainly hidden a lot. Would be great if npub1 part is ommited entirely as it doesn't carrying any meaningful info from my perspective. (This tool allowing the few last characters to be the part of the pattern, so this solves the problem a bit.) View article →

There is this https://delete.nostr.com/. Works perfectly; the notes are deleted. But the likes, boost, zaps, and alike are still present in the network. Is there a way to broadcast the kind 5 for them as well? #asknostr

Installed @0xchat. Someone with whom I would like to connect also uses this client. We both have relay.0xchat.com as DM Inbox Yet I'm getting only this: and followed by this: When the QR code generated in the next step, 'Invite Friends,' is shared with the other party and scanned, the attempt times out. What we are doing wrong?

Installed the tlp because I wanted a battery management but later found out it didn't support my HW. Sadly the tlp uninstall(?) in the process the power-profiles-daemon. At least in my case I had to install it clean to have the power menu back again. Simply systemctl enable the service nowhere to be found. C'mon, why.

Interesting, if I understand this correctly: 1) the trade-off is basically about how much time to allocate. Balancing the potential leak damage (timespan) versus nsec access frequency (how often to create epoch keys). 2) this basically gives me (or the nostr client) a temporary key to protect instead of using the nsec for each event. Have other solutions been proposed? If so, why weren't they implemented? (

Untraceable Digital Dissident

Cold Root Identity for Nostr: How Epoch Keys Fix the Hot Key Problem

Nostr identities break when a single hot key leaks. This guide shows how cold root keys, deterministic derivation, and rotating epoch subkeys creat...

View quoted note →

Have private bookmarks (in Amethyst) and would like to transfer them all into another account (under a new nsec) because they are a nice collection I don’t want to lose easy access to. Switching the account is a hassle. Is there an automated way to do this? Presumably not; I didn’t find an easy way. So is there some CLI tool I could use? #asknostr