
heyke
245 posts

heyke
@heykecode
20. cooking https://t.co/dOnZbY7uhs a GitHub repo analytics
GitHub Katılım Nisan 2024
61 Takip Edilen61 Takipçiler
Sabitlenmiş Tweet

they recommended that we do a re-launch on @Pumpfun.
it made me curious and i want to try how it works.
besides that, it would also be useful to raise more funds and keep building this project.
after what we raised with bags, we decided to make it completely open source so it’s free for everyone, at least partially.
but we plan to use the tokens as the main payment system in the app for premium features.
we hope for your support - we’re building nonstop.
CA:
9eQztaT2F3fs3R8m4V9dYgG4BNDuAj7h9d5Die97pump
GITHUB:
github.com/senjulab/gitst…
LINK:
gitstat.dev
English

Salimos 3ros en la Hackhaton de Medifé + Sanatorio Finochietto.
Diez puntos clave que nos llevamos de aprendizaje:
1) Mostrá tu business model en números, dato > relato
2) No ignores contar cómo está compuesto tu equipo, a veces 1 buen jugador es la clave para que te fondeen
3) Arrancá contando una historia de algún caso real que tenga la problemática que querés resolver, no vayas directo a contar el problema sin poner en situación a la audiencia
4) En el modelo de negocio, presentá costos relativos a lo que actualmente se está pagando, p. ej.: cuánto cuesta una cama por día en un hospital y cómo adoptando tu solución se reduciría ese costo a la mitad
5) Hacé contacto directo con tu audiencia
6) No metás papers en un pitch, meté gráficos visualmente impactantes y díficiles de discutir
7) Mostrá seguridad en lo que decís. Si no comprás vos tu idea, el resto tampoco lo va a hacer
8) Antes de pasar a hablar de costos, la propuesta de valor debe ser clara y convicente
9) Siempre tener claro cómo responder: 'si decidiera invertirte, cuánto gano?'
10) El cierre del pitch: siempre tiene que dejar con ganas de más

Español
heyke retweetledi
heyke retweetledi

we just added a coupon code
use EARLYBIRD and get $19 off on your first month
Ending in 48 hrs
go, deploy your agent
runclaw.sh

English

we introduce runclaw.sh
a much easier way to run @openclaw
on a dedicated server without having to configure anything
try it out!
any kind of feedback is welcome
English
heyke retweetledi
heyke retweetledi
heyke retweetledi
heyke retweetledi

Everyone wants OpenClaw but setup is not easy for non-technical people.
It involves npm, node.js , port configuration, telegram, environment variables. Takes hours just to get it running locally.
Use runclaw.sh
Boom

English

we’re riding the wave.
you no longer have to pay $49/month to get $15 in ai credits.
now pay 50% less and get $10 in credits.
that’s $25 a month.
try it out here:
runclaw.sh

English

Im on stream on pumpfun right now
im waiting you all make questions
join, im replying anything
pump.fun/coin/9eQztaT2F…
English

since a lot of people told me to do a stream on pumpfun, that’s exactly what i’m doing now
i’ll be live answering questions and building a feature that’s on our roadmap
here’s the stream link
pump.fun/coin/9eQztaT2F…
i’ll be waiting for you there!
English

Right now I’m super sleepy.
It’s been an incredible, very long day.
Tomorrow there are even bigger updates coming.
Remember, it’s completely open source and you can see everything we’ve cooked up.
And you know the best part?
We made it so our users can share the stats of their repositories.
So that’s exactly what I’m going to do right now:
gitstat.dev/s/senjulab/git…
NOW YOU CAN TRACK GITSTAT ON GITSTAT!
Sounds weird, lmao.
Let’s keep pushing and doing fun stuff.
English

I just wrote a blog to explain our entire repository and the tech we’re using to make GitStat truly awesome.
Check it out here:
gitstat.dev/blog/our-stack
You’ll love the read if you’re interested in what we’re using to make tracking a GitHub repository 100x easier.
we won't stop shipping
heyke@heykecode
We are building $GITSTAT. Here on our website’s blog, we explain exactly why we built it: gitstat.dev/blog/why-we-bu… This clears up a lot of questions. Now we are writing a full blog where we explain our stack. Even though it’s completely open-source on GitHub, it’s worth explaining why we used each tool. It’s 90% done. In a few minutes, I’ll announce it so everyone who wants to contribute to Gitstat can read it.
English

for this community to keep growing, resulting in growth for @gitstatdev and more activity in the $GS token,
i need everyone who follows me to join our community.
the $GS community will have content
mainly about updates on gitstat.dev
English

We are building $GITSTAT.
Here on our website’s blog, we explain exactly why we built it:
gitstat.dev/blog/why-we-bu…
This clears up a lot of questions.
Now we are writing a full blog where we explain our stack.
Even though it’s completely open-source on GitHub, it’s worth explaining why we used each tool.
It’s 90% done.
In a few minutes, I’ll announce it so everyone who wants to contribute to Gitstat can read it.
English

