Yes, this is what the first issue on tangled states:
> This repository is currently acting only as a GitHub mirror with a (relatively distant in time) aspiration to become primary remote.
> So please do not create issues/pulls here as all contributions are expected to go through GitHub at the moment (also consider contributing there). In case of a future full migration, I hope to be able to fully import all issues/pulls from GitHub to preserve easily searchable history.
I'm glad if it works for people, but I gotta give credit to AI for basically finally solving the text editor for me; as someone who knows a little vim but also spends a lot of time in CUA-land.
Micro did it for me. I even just gave it the ability to save and quit with :wq! just out of habit.
justauserid 6 hours ago [-]
Since I started using my own domain at bsky I kinda like this platform. I never have to even worry about the "username" which used to be a major source of concern especially if someone had already picked my favourite ones :)
But Tangled, or any git platform (even free ones), feel a bit off as they don't allow private repos at all. This is a very conflicting aspect of some open and privacy promoting platforms. I am sure they have their reasons but that doesn't make it hard to reconcile wiht it.
nerdypepper 6 hours ago [-]
this is actively in development!
hoppp 12 hours ago [-]
First time I hear about tangled and I love it. Really nice to see new git hosting solutions appear.
nicce 9 hours ago [-]
Wait until you hear it is VC funded as well
GCUMstlyHarmls 8 hours ago [-]
That does bum me out. I played around with Tangled before their recent 1.0/site redesign and it felt a bit locked up. I could run the "knot" to host my (public only) content but not the viewer. I think this story has improved now, I hope so.
I do think there is maybe some better outcome where the forge is explicitly started as a decentralized space, the lock-in is inherently not "built in" for later value extraction and I have no issue with VC wanting to make their money back via enterprise support, ci, etc if the 80% use case of view/share/follow is actually distributed and free as in freedom.
jonny2811 6 hours ago [-]
look at https://codeberg.org/ if you havent already, it is from a non profit in germany. it's a gitea fork and also available under forgejo to selfhost. i run it locally on my pi and it's fast and low memory footprint
GCUMstlyHarmls 4 hours ago [-]
I do run forgejo for my own private stuff, it's great IMO. But I would like to put public work on a decentralised network.
There are also gitgrasp.com, radicle.dev and gitworkshop.dev but I honestly don't think they'll ever manage to gain mainstream traction because they don't "just have a website" you can use.
What I like about those is they embed the issues etc inside the repo, but maybe that's ultimately unimportant if the underlying protocol (ie: Atproto) supports sharing issues and prs as "first class objects".
I'm not sure how viable it is, maybe Tangled can spark the idea in more people then we can get ~~`bazaar`~~ `byzantine` that provides an alternative implementation, still on Atproto using the same objects.
My knee-jerk reaction is that I assume Tangled could lock data down by preventing (non-cat-and-mouse scraped) data being shared between other systems by requiring that requests for "issue comments" must come via "at.tangled.dev" signed by "users verified by at.tangled.dev", maybe that's not possible and it really is open.
I dont mean to shit on tangled, it looks good, sounds good, I do like the project, I just worry its trading one globomegacorp for not-globomegacorp, that will eventually be bought by globomegacorp, vs maybe the chance here to actually hard-reset into a real p2p system.
DotNetCorePowa 16 hours ago [-]
"Mini.nvim"...
I am looking at my vim config with my 4 plugins.
What's "mini" about your "45+ independent Lua modules" ?
eikenberry 16 hours ago [-]
I think the mini part is that each is fully independent and you can pick and choose which to use individually. I currently use 4 mini.* plugins out of the 10 plugins I use and am happy with what they do.
canelonesdeverd 16 hours ago [-]
I'd say its more about the size/scope of each plugin rather than the number, and that you can use the whole thing like an nvim distro or pick and choose what you like and bring them to your own config
disperso 4 hours ago [-]
The way I read it, it's not that your whole configuration/setup is minimalistic when using this plugin in whole, or some of its parts, but it's rather than each plugin, separately, is reasonably small and self-contained, not aiming to cover absolutely every feature.
By using mini.nvim, I've been able to reduce significantly the number of separate plugins here and there, for example, because the plugins are either sufficient for me, or are reasonably easy to extend in your own config.
It's a great plugin/set of plugins overall. I would not read too much into the name, though.
sigbottle 14 hours ago [-]
A side note is that nvim does incorporate things upstream natively.
I believe "gcc", a la tpope, is now default part of nvim (not as a plugin just as a thing).
Also treesitter.
hiyer 13 hours ago [-]
Even package management is built natively into nvim now (and nvim's implementation is supposedly inspired by mini's).
ckolkey 4 hours ago [-]
Same author iirc
justinhj 16 hours ago [-]
Not everyone needs the same 4 plugins as you and this is a very nice set of plugins, each parsimoniously designed to have minimal configuration needed. The whole repo is a few megabytes.
The author is a neovim core contributor and I find his approach to plugins very compelling.
JustChandradev 5 hours ago [-]
[flagged]
nicolasdanelon 16 hours ago [-]
Isn't Codeberg against mirrors?
arcanemachiner 16 hours ago [-]
They appear to support "push" mirroring, but not "pull" mirroring. This appears to be a technical restriction, not an ideological one:
> Why can't I mirror repositories from other code-hosting websites?
> Mirrors that pull content from other code hosting services were problematic for Codeberg. They ended up consuming a vast amount of resources (traffic, disk space) over time, as users that were experimenting with Codeberg would not delete those mirrors when leaving.
> If you need a mirror, you can create manual mirrors by adding multiple remotes to your local repository and using git push --mirror.
Obviously you can't restrict literally just putting the code somewhere else if it's open source, you're allowed to do that by the license. It's just whether Codeberg allows the scraping, which seems reasonable to disallow.
slopinthebag 16 hours ago [-]
it looks like it's hosted on github and now tangled?
j16sdiz 12 hours ago [-]
> These modules improve your text editing experience. Start with 'mini.ai', ...
> mini.ai | Extend and create a/i textobjects
what a fun name.
GCUMstlyHarmls 8 hours ago [-]
It's "around/inside" for curious non-vim users. As in insert-around-this-word or select-inside-quotes.
ivanjermakov 5 hours ago [-]
:h object-select
behnamoh 15 hours ago [-]
Why? And does tangled support CI/CD like GH Actions?
OuterVale 15 hours ago [-]
Yeah, Tangled supports CI/CD. It has this lovely concept of 'Spindles' which lets you host it all yourself.
> * https://github.com/nvim-mini/mini.nvim (main)
* https://tangled.org/nvim-mini.org/mini.nvim (mirror)
* https://codeberg.org/nvim-mini/mini.nvim (mirror)
> This repository is currently acting only as a GitHub mirror with a (relatively distant in time) aspiration to become primary remote.
> So please do not create issues/pulls here as all contributions are expected to go through GitHub at the moment (also consider contributing there). In case of a future full migration, I hope to be able to fully import all issues/pulls from GitHub to preserve easily searchable history.
> Thanks!
https://tangled.org/nvim-mini.org/mini.nvim/issues/1
Micro did it for me. I even just gave it the ability to save and quit with :wq! just out of habit.
But Tangled, or any git platform (even free ones), feel a bit off as they don't allow private repos at all. This is a very conflicting aspect of some open and privacy promoting platforms. I am sure they have their reasons but that doesn't make it hard to reconcile wiht it.
I do think there is maybe some better outcome where the forge is explicitly started as a decentralized space, the lock-in is inherently not "built in" for later value extraction and I have no issue with VC wanting to make their money back via enterprise support, ci, etc if the 80% use case of view/share/follow is actually distributed and free as in freedom.
There are also gitgrasp.com, radicle.dev and gitworkshop.dev but I honestly don't think they'll ever manage to gain mainstream traction because they don't "just have a website" you can use.
What I like about those is they embed the issues etc inside the repo, but maybe that's ultimately unimportant if the underlying protocol (ie: Atproto) supports sharing issues and prs as "first class objects".
I'm not sure how viable it is, maybe Tangled can spark the idea in more people then we can get ~~`bazaar`~~ `byzantine` that provides an alternative implementation, still on Atproto using the same objects.
My knee-jerk reaction is that I assume Tangled could lock data down by preventing (non-cat-and-mouse scraped) data being shared between other systems by requiring that requests for "issue comments" must come via "at.tangled.dev" signed by "users verified by at.tangled.dev", maybe that's not possible and it really is open.
I dont mean to shit on tangled, it looks good, sounds good, I do like the project, I just worry its trading one globomegacorp for not-globomegacorp, that will eventually be bought by globomegacorp, vs maybe the chance here to actually hard-reset into a real p2p system.
I am looking at my vim config with my 4 plugins.
What's "mini" about your "45+ independent Lua modules" ?
By using mini.nvim, I've been able to reduce significantly the number of separate plugins here and there, for example, because the plugins are either sufficient for me, or are reasonably easy to extend in your own config.
It's a great plugin/set of plugins overall. I would not read too much into the name, though.
I believe "gcc", a la tpope, is now default part of nvim (not as a plugin just as a thing).
Also treesitter.
> Why can't I mirror repositories from other code-hosting websites?
> Mirrors that pull content from other code hosting services were problematic for Codeberg. They ended up consuming a vast amount of resources (traffic, disk space) over time, as users that were experimenting with Codeberg would not delete those mirrors when leaving.
> If you need a mirror, you can create manual mirrors by adding multiple remotes to your local repository and using git push --mirror.
Source: https://docs.codeberg.org/getting-started/faq/
> mini.ai | Extend and create a/i textobjects
what a fun name.
https://tangled.org/docs/spindles/