I can assure you that the way we're behaving towards Spark and the warnings we apply to its name won't make any PayPal mafia happy. It's a tool and we don't force-feed it to people like others do.

We didn’t and we explain that very well to users who choose the Spark route!

Sadly not everybody knows how to deal with wallets, nodes, etc. They must be educated and I’m sure they’ll get a culture just by staying here.

Spark must be treated as a custodial wallet even if it isn’t, it’s a good way to get people started - and hopefully those people will get their node up and running with your guides.

It’s not the only self-custodial easy-af solution out there, certainly not the best and not the last we’ll introduce, but it’s a good starting point.

Hmm, it's possible that our EXIF remover was unable to process your image after it was cropped. It's one _{of the things} that can fail silently and stop an upload even before creating a node in the editor, and given that our remover is finicky about formats or quasi-corrupted files it makes sense.

On which OS did this happen?

Been checking this but with no luck. I'm sorry that I'm reaching out just now.

Here are the things I've tried:

• creating a comment with a screenshot
  • deleting the comment
    • recreating the comment with screenshot
• upload, delete and re-upload of the screenshot in the editor

But everything seems to be working smoothly. When you couldn't add the same screenshot, did you receive an error?

No, 1 sat = 1 CC.

If you zap 100 sats and the recipient can only receive CCs, they'll receive 70 CC and the remaining sats will be split across territory revenue (to the territory owner of the post) and rewards pool.

CCs are fully usable site-wide as sats and can become sats through the rewards pool.

Hi! I’m checking this out right now!

I’ll come back with questions if I’m not able to reproduce it myself ^^

Damn I almost missed this, the other guy is guerratotaI

We have an open issue about nym similarity, I'm working on UI at the moment so I'll see if there's something we can do to present nyms in a way that characters cannot be mistaken.

I felt sorry for the guy that hit me because it was genuinely a mistake, he was trying to reverse from its parking spot but didn’t see me coming from the other street. Also his car was already in a pretty bad shape.

The thing with Hertz is that you pay the damage even if they recoup everything via insurance.
So I didn’t give Hertz infos about him or his car, just a detailed story about what happened. It didn’t make sense to make him pay in addition to what I have to pay myself anyway.

edit: now, if it was my car it would've been a completely different story lol

I'm renting an awesome car at an awesome dirt cheap price, the Peugeot 208 GT. It's only been a week and I already got hit lol, leaving a not-so-little dent with scratches 💀

I truly don't know, it seems like that tasks that require more than 10 minutes are more prone to this behavior. Changing the effort level helps a little but not so much, it's like it gets convinced about a fact during reasoning and never checks it again.

The weirdest part is that fighting Opus on presented lies becomes a gaslighting game and it's really frustrating lol. Fable is much, much slower but it's less prone to lies (never happened to me thankfully) and absolutely won't fight me if I say that 1+1=2 (simplification)

everybody lies, but I mean Opus really lies all the time

Opus xhigh still lies, and in general Opus is always so protective of its lies, idk.

I used to love Opus, likewise up until 4.6

That. I just stopped using Opus once Fable came out, I don’t think it ever lied to me.
Also Sonnet feels more reliable than Opus.

Opus loves to lie

I don't know, for some reason I still prefer the Analogue 3D. But this is really cool too!

Finalizing the migration of our components to more up-to-date frameworks. I've been migrating with Claude (it's a pretty mechanical task) and, albeit really slow, it's been great and consistent.

So this week I'm working on taking apart the migrated components to humanize them, half of the line count is just historical garbage.

I was checking in bio, but the problem is that mentions in general don't accept formatting at the moment because of the way we render them.

For example this link https://stacker.news/items/1533070 is an item URL and thus eligible to be an item mention.

I can write

[`this one`](https://stacker.news/items/1533070)

and it renders as: this one
as you can see it lacks the code format that we achieve via backticks

If instead we write a normal URL

[`this one`](wikipedia.org)

it renders as: this one
formatting is preserved.

bottom line, mentions such as item mentions don't support formatting but we're going to add support soon. The problem, really, is that mentions are rendered as normal React components, they don't have the same formatting awareness that other, normal, Text nodes have.

ahhh I see, custom link formatting for item mentions is not working! This is a known issue within the editor, I previously thought we fixed this but it's clearly not the case as I had other reports like this.

I'll check this out today ^^ thanks!

seems like it works to me, what are you encountering?