Cool stuff! How did you do it?

#gm #asknostr

What did Santa bring you this year?

#asknostr #portugal #gig

Looking for some data about Uber rides in Portugal.

I'm paying 0.60 eur per valid receipt.

Constraints:

* Must have been a ride in Portugal (and completed)

* Must have been in the last 3 months (> 2025-09-01)

* Must have costed more than 10 eur

How to submit:

Fwd the trip receipt to uber.outrank950@silomails.com alongside with a lightning address or npub.

Once I validate the data I'll send you the satoshis!

Questions, just drop them here :)

#vibecoding

This month I've been trying out venice.ai

Pretty cool service. You get to try a bunch of different open source models with a pretty slim UI (not that clunky hugging chat). Kimi, GLM and even their version of Mistral's latest.

The promise is still uncensored AI and privacy focused AI; they are almost there (all models are just using other inference providers) but it's pretty good to try.

I don't think you will throw it all out afterwards. It is still a good thing to keep and prototype on as you evolve.

The main drawback I see on replit: it skews you into using their infra. But that doesn't mean you can't hire a developer (or even cursor) to change that. One can develop on replit and commit code to GitHub, which makes you free to use cursor (and also replit) for evolving and making it more robust.

But that doesn't mean you'll throw it all out. It might just mean that your workflow switches to cursor and you work together with developers on the same repo.

A second drawback I see is that replit and cursor are both in one single repo. As your feature set grows it makes it harder for the models to be fully aware of your context. Here again might you may hit a point where you want to hire someone to help you restructure and architect the code. It is not incompatible with the cursor idea i shared above.

If I were in your place I would start by

1) dual development - replit and cursor - because it creates the foundation in GitHub for you to collab with a developer. You'll start using issues, actions etc. You'll gradually turn replit into one part of your dev cycle

2) start looking for a dev that could help you structure the code and architecture.

All in all you don't need to ditch replit completely but you can grow further than it's vanilla usage

It's incredible how even though most parents agree their kids shouldn't be in social media, few would actually enforce it themselves.

Then they delegate the responsibility to the gov.

Which, naturally, always has everyone's back and it's totally not going to turn into a surveillance state 🥸

But have you tried it? Skimming through it, it looks like cursor but Googled

We need to start pushing "real" because it automatically makes non milk fake milk.

Once that is out, the question must become " do you want regular milk or raw milk?"

"do you want that with regular milk or oat milk?"

There's only one answer to that question: WITH REAL MILK

#carnivore #asknostr #gm

GM Nostr!

Something you can't find on Spotify... Damn drm and licensing deals

N.I.B - Primus & Ozzy Osbourne

https://youtu.be/U122lh0ODFU?si=wq-W86tQhwmDSgbu

That's the trade off of caching. It's not always in sync

GM Nostr!

Thursday on Satriani vibes

https://youtu.be/SINl5JY7LhI?si=l2cyhynj0Lgc_mbk

What's the name of this guy?

Those are the coolest apps to see!

And share the link! Let's see it!

I'm still trying this, so take it with a grain of salt: plug the code into GitHub and then use cursor to develop even better.

The problems I couldn't solve for yet are: multi repo development and keeping the codebase clean (replit makes a big mess out of branches and you need to clean it up manually with git. Not fun.

But I do see it as a step further. Since replit is good to start, but then starts getting nasty re implemting things left and right

The only downside is that some services treat you like a criminal for using it. But you can bypass it easily with a custom domain/subdomain.

Extra points for being super easy to create shared accounts with loved ones (like your mom's bank account).

What's the verdict?

hopefully not the same mistakes 🫡

Now I got it. For a moment I had a fiat PTSD vision from the past where zaps were getting chargebacks 😱

Hey, I've been vibe coding some stuff with replit.com, do you think I can use Shakespeare on it as well? I'm curious to see how it would review the current codebase given it's specific nostr context/knowledge

I'm keeping the code in GitHub itself

These N nodes, you created them? Or n8n has a native nostr applet? (I don't recall seeing it, neither looking for it)

Is it working?