Semisol
semisol

software developer

Public Key

npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj

NIP-05 Address

[email protected]

NIP-57 Address

[email protected]

Profile Code

nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmdqydhwumn8ghj7mn0wd68yttsw43zuum9d45hxmmv9ejx2asuqshs8

Publishing to

relay.noswhere.com

nostr-pub.semisol.dev

nos.lol

Author Public Key

npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj

Show more details

Last Notes

2024-11-15 06:57:47 GMT

We need community notes for Nostr

2024-11-14 22:11:21 GMT

- reply

Okay so TL;DR
Coinkite makes blockclock mini and sells it for $400, closed source
@npub1k5f…vqg2 makes a similar DIY device that is fully open source named BTClock
They get harassed at launch by Coinkite
It goes well for a while, then Coinkite takes down their Github by claiming trademark infringement because BTClock is too similar to Blockclock

2024-11-14 20:50:44 GMT

- reply

Coinkite Inc. is the developer of the "BLOCKCLOCK," a product featuring seven electronic ink digits that provide customizable cryptocurrency and blockchain information, including cryptocurrency price, volumes, exchange rates, current coin supply, block height, and Merkle root. Coinkite Inc owns the trademark "BLOCKCLOCK" (Registration No. 7237159) in Class 9 in the United States.
The infringer BTCLOCK identifies its product as "BTCLOCK". It is defined as “a block with electronic ink displays, which can show stuff related to Bitcoin”. The use of "BTCLOCK" has strong similarities, both in name and functionality, with Coinkite’s registered trademark "BLOCKCLOCK", as follows:
1) Phonetic similarity: "BTCLOCK" and "BLOCKCLOCK" sound very similar. Both emphasize the term "CLOCK," with "BT" and "Block" being the only differences. The phonetic similarity can cause confusion, leading consumers to mistakenly believe the two products are related or come from the same business origin.
2) Visual similarity: The appearance of "BTCLOCK" and "BLOCKCLOCK" is also quite similar. "BT" and "Block" both consist of short prefixes followed by "Clock", which could easily cause confusion at first glance. In addition, the use of seven screens with electronic ink to display Bitcoin information gives the same impression in the users. The word BTCLOCK is displayed in the same exact position that it is in the BLOCKCLOCK.
3) Same functionality: Both products are aimed at a similar audience - people interested in cryptocurrency, specifically Bitcoin. Since both products appear to perform a similar function (displaying cryptocurrency prices), there is a high likelihood of confusion. Consumers might believe the two products are from the Coinkite, which is not accurate.
4) Risk of confusion: Since both devices seem to have similar functionality (displaying Bitcoin prices), this increases the chances that consumers could be confused about their origin. They may think "BTCLOCK" is a version or a rebranding of Coinkite's "BLOCKCLOCK." If "BTCLOCK" becomes associated with a different company or quality, it could dilute the distinctiveness of Coinkite's "BLOCKCLOCK".
The use of "BTCLOCK" in GitHub could be infringing Coinkite’s trademark rights.
What would be the best solution for the alleged infringement? Are there specific changes the user can make other than removal? (e.g., transfer of trademarked username to an existing company account, removal of trademarked logo or references to company)
(1) Cease and desist the use of the words BTCLOCK, BLOCKCLOCK or similar words in the following websites: https://github.com/btclock; https://btclock.github.io/web-flasher/
(2) Remove any pictures, documents, links with the words BTCLOCK, BLOCKCLOCK or similar words from the following websites: https://github.com/btclock; https://btclock.github.io/web-flasher/
(3) Suspend and/or terminate the infringer's account BTClock.

2024-11-14 20:31:45 GMT

You can still register for the beta-test of my signing card, using security certified chips. Expecting samples ready by late 2025 Q1.
It also uses a custom platform with security-by-design, compared to the development approach of most other signers.
No bullshit claims, no cutting corners, no overpriced hardware.
https://forms.office.com/r/CxzzG4Wqam #note1655…pgxy

2024-11-13 12:22:33 GMT

What HWW would you recommend?

2024-11-04 13:32:41 GMT

- reply

Yeah, I said HWWs.
Also one seedsigner can handle all keys.
What to use: your choice and threat model

2024-10-30 17:53:50 GMT

- reply

Use a client that actually cares about its users, like Coracle.

2024-10-29 21:30:09 GMT

- reply

You only get a yes or no, nothing else.

2024-10-27 20:19:01 GMT

depending on where you travel to and your country of residence, at border control, scanning your passports will automatically transfer biometric information stored on the chip of the document #note1xrm…mje7

2024-10-25 19:28:40 GMT

or can they? :) #note189n…tzfq

2024-10-22 21:28:54 GMT

promoting your project (esp. for monetary gain) should not become your primary project
a lot of things in bitcoin have gone wrong because of that: HWWs, shitty grant funding schemes, podcasts, confs #note1z0q…md58

2024-10-18 21:52:36 GMT

- reply

not the issue, it was I installed a new package
since I didn’t update for a while it pulled in newer versions of its dependencies, while other packages were left outdated

2024-10-18 21:52:03 GMT

- reply

good point
except that is considerably better than “throw shit at a wall until it sticks” approach that some HWW manufacturers take
though they also do not know how an SE should be properly used

2024-10-18 13:34:53 GMT

THE HWW REVOLUTION IS HERE
A DEVICE YOU CAN ACTUALLY TRUST WITHOUT INSECURE SE’s LIKE THE ATECC608B MEANT FOR A SMART LIGHT BULB
AND MADE TO BE ACTUALLY SECURE
REGISTER NOW FOR EARLY ACCESS #note1gwv…rq0h

2024-10-17 21:13:19 GMT

- reply

Uh.. kind + pubkey is an ID lol

2024-10-17 20:30:41 GMT

Please fill this short survey if you can related to my in development signer, and renote for visibility.
You can also register for testing for early access + a free signer (only shipping) in what I expect to be late 2025 Q1.
https://forms.office.com/r/CxzzG4Wqam

2024-10-17 20:13:52 GMT

and then we manage to pollute the earth’s orbit and make space junk even worse #note15nu…h6tv

2024-10-17 17:38:51 GMT

- reply

Which ones would you like to know about?
But if it has “Bitcoin only” in its marketing, it 99% of the time falls under these categories.

2024-10-15 21:27:21 GMT

While developing an HWW, I have started to realize that 90% have no idea what they are actually doing and they think that adding a secure element is a silver bullet to all security issues

2024-10-15 15:08:06 GMT

- reply

No. It’s some ordinals shenanigans. I should have checked the address histories more

2024-10-15 15:07:17 GMT

- reply

Yeah it is a node sweeping multiple anchors at once I think

2024-10-15 14:26:04 GMT

- reply

LN node anchors (?)

2024-10-14 14:20:21 GMT

- reply

That is bad for onboarding. Or efficiency.
Why spin up a relay per community if they trust a friend and they have a relay already running?

2024-10-14 14:12:09 GMT

- reply

You either have a server running Debian and manually configure everything, or you don’t run a node. It’s that simple.
If you can’t do that then you will lose funds

2024-10-14 14:10:28 GMT

- reply

Communities are needed but not when they centralize onto individual relays and everyone has to pay just to start one because they can’t use an existing relay by a friend or a public one

2024-10-14 14:03:03 GMT

- reply

Nostr devs are too dumb. And who cares, everyone can pay for a relaybto host.

2024-10-14 01:35:16 GMT

- reply

Didn’t check that

2024-10-14 01:30:49 GMT

- reply

Actually if you hate manually going to their profile on Twitter to verify, there is a spec to link profiles on different platforms to Nostr and even PGP keys

2024-10-14 01:09:05 GMT

- reply

That does not matter
We are verifying that their Nostr identity is linked to a known good identity (their twitter handle with a lot of followers)

2024-10-14 00:59:34 GMT

- reply

If you can’t verify then don’t say shit I guess
The end result will be nostr getting a reputation for fake and scam accounts

2024-10-14 00:58:59 GMT

- reply

Nitter

2024-10-14 00:30:49 GMT

it is funny watching people trust and not verify
is it really that hard to check for a tweet or something? #note1wdc…cnxj

2024-10-13 23:44:14 GMT

- reply

read the name of the account you are replying to

2024-10-13 18:23:52 GMT

- reply

Yeah because no one has implemented forward secrecy yet.
And gift wraps are shit and don’t work.

2024-10-13 18:09:42 GMT

- reply

DM username

2024-10-13 18:09:30 GMT

- reply

so what? you need some amount of limited access for ecash too

2024-10-13 17:53:31 GMT

- reply

No the UX sucks
Matrix or Signal?

2024-10-13 17:52:17 GMT

- reply

Can redo it if needed, I have a way of doing it about 80x faster than my previous algorithm.
Do you use Telegram so I can DM you there?

2024-10-13 17:50:26 GMT

- reply

Yes and people want to slap it onto everything just because they can
This reminds me of something…. Shitcoins

2024-10-13 17:47:22 GMT

- reply

tbh, one relay per community means people have to pay to start a community, even when using public relays
communities must be encrypted, private relay or not, the hosting service can get compromised, etc

2024-10-13 17:39:45 GMT

- reply

Yes and so why not use LN? Why ecash?

2024-10-13 17:37:03 GMT

- reply

You haven’t read the last part of my post

2024-10-13 17:34:48 GMT

There is so much data on nostr left to be analyzed

2024-10-13 17:31:46 GMT

We are going back to centralization with relay = communities

2024-10-13 17:28:59 GMT

the problem is that you can’t mint ecash without being connected to the internet, and you can’t connect to the internet without paying
also using ecash is utterly stupid for this as not everything supports it compared to LN, and you have to use a “preferred mint” etc and any mint conversion mechanism already uses, you guessed it, LN #note1sld…lwj2

2024-10-13 13:37:06 GMT

- reply

bitcoin core USED to do nondeterministic

2024-10-13 11:37:24 GMT

- reply

To test this there also should be a “fuck them both” option

2024-10-12 22:46:22 GMT

the only way to make a secure hardware wallet is by not being able to leak what you don’t know
:) #note1e5e…qske

2024-10-12 22:32:26 GMT

preventing side channel attacks is really fucking hard

2024-10-12 22:10:36 GMT

- reply

That is caused by the transaction system used by ZFS: all writes are committed in 5 second transactions, and before that the blocks reserved for the write and the original blocks for CoW are both “used”
This is kind of the shittier part of the FS, as it means sync writes run twice: one to the ZIL, and then to the actual disk.

2024-10-12 20:14:06 GMT

- reply

inkjets are arguably the dumbest printers that could exist: a motor to move the paper, a motor to move the print heads, the ink itself, print heads that just spray ink droplets, and some sponge to hold waste ink for cleaning
it’s all the extra bloat on top
and the software that means that the printer either clogs after no use, or it keeps dumping shitloads of ink every day as “maintenance”
you can dump a ml or two of ink through the heads every few days and it’ll never clog or accumulate air while powered

2024-10-12 19:09:22 GMT

- reply

I own an epson ecotank that is decent, and have the software for resetting the waste pad counters if need be (they are on sketchy websites, but it works and you can run them on a VM with USB passthrough and no internet only)

2024-10-12 19:05:46 GMT

- reply

also nothing can beat laser in water durability, pages per minute and reliability for low volume use

2024-10-12 19:04:37 GMT

modern inkjet printers are the work of the devil
yes, inkjets arguably have their place in high resolution printing, especially for color images
that doesn’t mean shit if the printer keeps clogging instead of using the bare minimum amount of ink every few days to prevent clogs when unused, having the problem of non user serviceable waste ink sponges + print heads for tank printers, expensive af cartridges, and DRM on those
something composed of a dumb print head, two motors, a paper feeder and a sponge apparently has to be so fucked

2024-10-12 18:55:32 GMT

- reply

I like ZFS but I cannot deny it feels very out of place
It tries to integrate block device abstractions and the filesystem into one layer.

2024-10-12 18:48:10 GMT

- reply

Yes, that is the only option. You must add the relay used by the NWC server I believe

2024-10-12 17:48:23 GMT

And yet they still fall for bullshit propaganda from HWW manufacturers, are delusional about the state of Bitcoin and Nostr, and keep bitching about stuff they don’t know about. #note1mh7…8vc5

2024-10-12 09:56:12 GMT

- reply

Cancel your credit card

2024-10-11 15:08:31 GMT

- reply

still has latency, considering USB is still polling based

2024-10-11 14:54:59 GMT

- reply

no one cares, they just want to complain
nostr nests had no relation to nostr for a year+

2024-10-11 14:53:14 GMT

- reply

on Pi’s this actually negatively impacts performance and SD card longevity

2024-10-11 14:03:38 GMT

- reply

the in other words part is wrong

2024-10-11 13:30:40 GMT

- reply

They charge additional fees as a credit card provider to merchants.
Then they take most of it and give you pennies.

2024-10-10 13:19:02 GMT

- reply

WoT is pointless for resumes

2024-10-09 22:02:35 GMT

- reply

I love it for being explicit when you ignore and when you handle (with no other option) and hate it for being repetitive

2024-10-09 21:40:46 GMT

- reply

fuck. s/n nil/n err/

2024-10-09 21:40:20 GMT

- reply

if err != nil {
return nil
}

2024-10-09 17:03:39 GMT

it will be bad when a client’s domain gets compromised and nsecs leaked via an attack
so people will switch to web based signer apps
then they will be compromised
the only way out is a proper hardware signer, a proper remote signer or a browser extension

2024-10-09 16:53:32 GMT

Go is the way for backend.
Kotlin when you need it.
C will stick around forever for some use cases because it is very close to machine code. #note15u7…ylv8

2024-10-09 16:51:22 GMT

- reply

Verify performance?

2024-10-09 14:28:18 GMT

- reply

I think not being burnt out is more important
There’s moderation work, and clients also want features, then you need to make sure it runs stably, etc.

2024-10-09 13:12:30 GMT

- reply

did you hear about static or dynamic analysis? 😆

2024-10-09 05:43:14 GMT

- reply

to be able to have AI scan vulnerabilities means that it needs to be able to build a map of the application logic, how every small detail interacts and how these may combine into an exploit chain
that is not possible with a text predictor

2024-10-09 05:34:03 GMT

- reply

nostr.build already has file search, along with filtering my category and folders

2024-10-08 20:56:32 GMT

- reply

Why use a HWW then?
You need to store the seed backups somewhere, may as well use SeedSigner with the seeds

2024-10-08 20:37:39 GMT

- reply

yes, they have, the SE2 used by CC Mk4 is broken (source: Coinkite), and SE1 also has been broken (source: a talk by the Ledger Donjon team)

2024-10-08 20:26:25 GMT

- reply

Plug it in, authorize the client, then you can manually approve from the app or auto approve certain kinds.
A hardware screen is not necessary for this use case. Manually verifying for every AUTH event or reaction is going to make the UX shit.

2024-10-08 20:18:14 GMT

- reply

both SEs are vulnerable to laser fault injection and lack basic protections that has existed in any credit card for the last 15 years

2024-10-08 20:17:09 GMT

- reply

yes, the only case it could work with unnecessary complexity is where you use a remote signer, each client maintains state locally, and you remove a client
in this case you can also do the following which is easier: rotate the secret used for encryption

2024-10-08 19:06:09 GMT

- reply

actually, wrong term
I meant forward security
post compromise security is interesting, but it is not applicable in nostr

2024-10-08 18:58:56 GMT

- reply

NIP-04 and the likes work (not that they are good, especially gift wraps) but they have no post compromise security

2024-10-08 18:55:36 GMT

- reply

both of them are IoT grade shit (and at least one lacks any CC certification) that don’t have the same basic protections as any credit card within the last 15 years

2024-10-08 18:54:34 GMT

- reply

both of them have viable laser fault injection attacks meaning you only need the expensive (probably $300k max) equipment, but that’s nothing as you can reuse it for as many wallets as you prefer

2024-10-08 18:50:38 GMT

The idea that an HWW’s security hinges on the secure element only is insane

2024-10-08 17:28:58 GMT

the devs say “go make a better one yourself” because they are too incompetent to do that themselves

2024-10-08 17:27:28 GMT

- reply

didn’t get the pgp key + email yet though
or signal

2024-10-08 17:27:02 GMT

they are too busy making the 37th ecash wallet that looks like it was named by an immature idiot to fix real issues #note1wzx…spmg

2024-10-08 15:44:40 GMT

- reply

security is a layered approach
one of them is having a secure element
there’s more that I will publish later :)

2024-10-08 15:41:14 GMT

Shredding a credit card does not make it unusable

2024-10-08 15:25:28 GMT

- reply

localhost websockets

2024-10-08 15:25:11 GMT

- reply

That is what I mentioned in my post as not a shitty ESP32

2024-10-08 15:12:48 GMT

- reply

Unfortunately the culture of quantity over quality exists here

2024-10-08 15:01:07 GMT

Welcome to Nostr
Fast paced low quality half working projects are incentivized more than quality products that take months to build #note1jma…uagf

2024-10-08 14:15:55 GMT

- reply

Memory bandwidth contention manifests itself as a drop in performance across all cores after some threshold :)

2024-10-08 12:18:31 GMT

The benefit of a proper hardware solution is that:
- unlike nsecBunker, nsec.app and browser extensions, the impact of malware is limited
- unlike nsec.app your keys cannot be stolen by the app developer with a silent update
- unlike other “hardware” nostr signers, it doesn’t store keys in an easily dumpable ESP32 #note140n…uhlv

2024-10-08 12:00:44 GMT

- reply

Electric car fires are the worst.

2024-10-08 08:03:02 GMT

- reply

we do not need that either
it also supports negotiation
you set a list of protocols to request, server sends a protocol picked or none as a response

2024-10-08 08:00:23 GMT

- reply

websockets already support a protocol header

2024-10-08 07:35:10 GMT

- reply

We can have a version field also.
Version 1: just normal Nostr events, signed as usual
Version 2: fields can now contain non-UTF8 content, new signing scheme