Hi, Peter the Founder of Pushin.eu here. Sorry, the website escaped containment and landed on HN before I had the chance to update the "marketing materials" aka. landing page. So, here are a few points:
*The product is stable, but still in development. That's why some of the core things like pricing, etc. are missing. BUT:*
1. Business Model: Pushin will have subscriptions for individuals and teams. Pricing is not yet decided but it'll be close to GitHub/GitLab pricing.
2. Privacy: In true German fashion, we *don't* want your private data. Pushin doesn't track anything beyond the obvious: email, password hash, username, whatever information you put on your profile.
3. Roadmap: We're currently in Beta, but everything looks good so far. We'll probably go GA beginning of 2027. I'll focus on delivering the core features first and make sure that they are polished and of good quality before moving on to the nice-to-haves.
4. I say "we" but it's really only me (Peter Ullrich, peterullrich.com) and my dog (Bella, Labrador, beige). "We" are not VC funded, but bootstrapping on bare metal Scaleway servers. My wish is for this to become a proper company soon though.
5. Tech-stack: Elixir (Phoenix + LiveView) for most parts, Rust for the Git parts, S3-compatible buckets and Postgres on Scaleway, servers are bare metal Scaleway servers running in Paris.
6. Git implementation: Just like Tangled, I've used Rust and the gitoxide libraries to build a Git implementation that's fully compatible with the canonical Git CLI, but uses S3-compatible buckets as storage instead of keeping the entire repo on disk. I'll write in-depth about this soon, but it's very much what Tangled did, just with a different storage concept.
I gotta be honest that I'm both scared but also excited that Pushin hit HN. I wish we'd be better prepared, but here we are. Many thanks to anyone who is willing to try it out!
Hey Peter, that's a very cool idea. I think (digital) sovereignty doesn't just happen, it's something we need to build and that's how we do it. It's a bit like "local first". Looking forward to using it once it launches :)
Well as soon as your pricing is available and full onboarding is done, I will be pushing for it at work. We just left bitbucket and I have everything stored locally until we find an alternative and I just found it.
In Europe people generally use “Europe” and the EU interchangeably.
I’m not sure many people would include Russia in Europe in normal speech, unless they were a geographer in which case Russia is partly “Europe” in some cases I think.
Even when the UK was part of the EU if someone in the UK said “Europe” they meant continental Europe and someone in continental Europe would be unlikely to mean the UK if they said Europe unless they were using “Europe” as a shorthand for the EU. When the UK was in the EU a United States American saying Europe would probably not not be including the UK in their mental model of Europe and, indeed [0], might not be very clear on what the UK actually is, because that’s confusing for the countries they agglomerate into “England” which might also include Ireland. A United States American saying “Europe” most likely means “Paris” and then maybe France, Italy, Spain or Greece but probably not Germany which is definitely the EU and everything that is wrong with the EU. But maybe Switzerland, because that very European.
As a European I’m not even sure where Serbia is, or if it’s even a real country [1]. I thought it was capital of Albania [2] . Or possibly a region of North Macedonia [3]
[0] only some of what I have said should be taken even part way seriously. Very little in fact
[1] Obviously being satirical here
[2,3] Also real countries, also European, but not necessarily “Europe” and definitely not EU. Yet.
> In Europe people generally use “Europe” and the EU interchangeably.
In Europe some people generally and incorrectly use "Europe" and the EU interchangeably. Europe existed far before the EU and will continue to exist after the EU finally comes to an end.
> Europe hasn't always existed as a concept, and its longevity is unknown.
Europe is the name of a continent. What reason(s) would there be to change the name of a continent?
In contrast, the EU is a trading block, set up to foster greater pan-European trading relations. It's not the only pan-European institution. For example, the Council of Europe ( https://en.wikipedia.org/wiki/Council_of_Europe ) is a separate pan-European institution, set up in 1946 which was before the EU or any of the predecessors of the EU, and amongst other projects was behind the formation of the European Court of Human Rights. I bring this up to highlight that we do not need the EU in order to have collaboration between European countries.
You haven't given any dates, but if you're talking about ancient Egypt, i.e. the Egypt before 0AD, then yes. The term "Europa" was used to refer to the continent around this time by the Greeks, and I don't see why Egyptian people wouldn't have picked up on a useful term they didn't have before.
Even if you did/did not, vernacular evolves. So at the time that you fervently hope the EU comes to its (clearly deserved, Mr Putin) end, I imagine people will be able to adapt their wrong speak and clearly incorrect thinking to ensure they adhere to the newspeak.
> at the time that you fervently hope the EU comes to its (clearly deserved, Mr Putin) end
I find it funny you think the only reason people would want the end of the EU is if they're a Russian agent. The EU has very little to do with defence. Perhaps your argument would hold more weight if talking about NATO, but even then it's not necessary for countries to be members of NATO in order to collaborate on protection when their collective security interests align.
« As a European I’m » – So what country do you hail from? I understand it's not Serbia. Just so this wild nonsense and wannabe satire can have proper geographic attribution. (Because despite there being a strong indidivual factor, the systems governing some countries do breed certain mental dispositions.)
That could change at any time. They could move to an Italy datacenter owned by a different company and that would be just fine.
But whether they're making a promise to stay in the EU specifically? Or whether they might expand to territories that aren't physically in Europe? That could matter, and the FAQ doesn't tell us.
(And yeah the line at the top says 100% EU but that's not the full picture.)
You seem to cite tangled a lot, and logically, I am wondering if you have any plan to also federalize on top of the AT protocol, so accounts could interact across the site boundary and also allow self hosting but still benefiting from pushin network? It may be hard in terms of design so I understand if you say you won't.
Yes! I’d love to provide private or at least personal firehoses to users maybe based on the same lexicons as Tangled uses so that you can sync your Pushin repo to your own Tangled knot. That’d be cool, no? Also, sign-in with your atmosphere account, and generally offering lexicon-based API output to make it easy to sync to Tangled or somewhere else
> 4. I say "we" but it's really only me (Peter Ullrich, peterullrich.com) and my dog (Bella, Labrador, beige).
I wish you the best, and I understand this might be necessary initially, but honestly I myself would never use a one man operation for anything I run in production.
It's closer to walgit as it stores the packs in S3, but it uses Postgres for locking a repo during a push instead of using the Cursor/Walgit trick of using a WAL+CAS in S3. I've evaluated CAS on the Scaleway S3 service, but writing the WAL adds 240ms to every push, a cost we don't have with Postgres where it's a fast row lock. I also evaluated whether keeping a WAL would be useful, but ultimately decided against it because we can track everything the WAL tracks through the git history + audit logs without the write cost overhead.
Congratulations! I'm hooked.
The AI slop block is what I like to learn more about. The FAQ does not include AI slop. Can you elaborate a bit on it please.
I just added a new FAQ item for that, but I'll copy it here as well:
We plan to reduce low-quality contributions through several features, some already in place and others still to come. Invite-only registration helps us discourage low-quality accounts and confirm that new members are real people. Next, we plan to introduce a vouching system, similar to Tangled's, that lets contributors build a reputation. We'll combine that reputation with other signals to assess new pull requests and issues. Contributions that appear low quality will be clearly marked and de-emphasized, while maintainers will make the final decision. We also plan to limit how many pull requests and issues a new contributor can open in repositories they don't own. This will be an ongoing effort, but the goal is simple: maintainers stay in control of their queues.
Ironic really because that was the original idea behind Git - to build a tree of trusted developers for the Linux kernel. Linus has those immediately below him that he trusts will push good quality code, and those folks do the same with their group of contributors.
> Invite-only registration helps us
If this is invite-only, then what you're doing is emulating the original strategy of Linus: only certain folks have commit rights. Extend that out to only certain folks have PR-creation rights and you're done. Maintainers select those that can contribute, these folks in-turn, select those that can contribute to the project, rinse and repeat.
Let everyone create issues and implicitly ignore these because any issue that doesn't make it passed the "acceptance level of a maintainer" will naturally be ignored and disappear. As is the case over at GH - issues naturally suffocate because no maintainer gives them air.
Perhaps have a special category "untrusted/toxic PRs" for contributors who don't belong in the tree of trust. These PRs are handled in a toxic-proof containment environment, i.e., they get particular vetting attentions by maintainers. Obviously this would be a path into the "tree of trust" for a project.
Then each project can also implicitly define what is "low quality" for their project - it's how they handle the "toxic PRs".
EDIT:
That's also why branching and forking is so cheap in Git: each sub-maintainer can maintain their own fork with it's branches before pushing up changes to the main fork. (Compare branching using RCS/CVS or Subversion to Git to get a feeling of "cheap" ;))
This can be done over at GH if a fork would be actively maintained by a sub-maintainer and every X days/weeks/months they would push the entire changes of the fork to the main repository. That would be closer to the Linux development strategy - as I understand it.
> Pushin doesn't track anything beyond the obvious: email, password hash, username, whatever information you put on your profile
This seems poorly worded or genuinely concerning. Why do you want to track my email, username or anything in my profile. What do you do with it? How do you track it?
"Track" means "store" here and we need to store it for authentication (email+password hash) and to show your public profile (e.g. https://pushin.eu/pjullrich). So, regular things, not tracking you for data mining stuff
*The product is stable, but still in development. That's why some of the core things like pricing, etc. are missing. BUT:*
1. Business Model: Pushin will have subscriptions for individuals and teams. Pricing is not yet decided but it'll be close to GitHub/GitLab pricing.
2. Privacy: In true German fashion, we *don't* want your private data. Pushin doesn't track anything beyond the obvious: email, password hash, username, whatever information you put on your profile.
3. Roadmap: We're currently in Beta, but everything looks good so far. We'll probably go GA beginning of 2027. I'll focus on delivering the core features first and make sure that they are polished and of good quality before moving on to the nice-to-haves.
4. I say "we" but it's really only me (Peter Ullrich, peterullrich.com) and my dog (Bella, Labrador, beige). "We" are not VC funded, but bootstrapping on bare metal Scaleway servers. My wish is for this to become a proper company soon though.
5. Tech-stack: Elixir (Phoenix + LiveView) for most parts, Rust for the Git parts, S3-compatible buckets and Postgres on Scaleway, servers are bare metal Scaleway servers running in Paris.
6. Git implementation: Just like Tangled, I've used Rust and the gitoxide libraries to build a Git implementation that's fully compatible with the canonical Git CLI, but uses S3-compatible buckets as storage instead of keeping the entire repo on disk. I'll write in-depth about this soon, but it's very much what Tangled did, just with a different storage concept.
I gotta be honest that I'm both scared but also excited that Pushin hit HN. I wish we'd be better prepared, but here we are. Many thanks to anyone who is willing to try it out!