# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 26
# self = https://watcher.sour.is/conv/642j7gq
Seriously I don't understand why Vim plugin systems even exist when the whole thing already has one built-in and doesn't need extra magic on your .vimrc to work
It's just as simple as cloning a plugin's repository straight into ~/.vim/pack/dist/start/ and be done with it.

Thanks for coming to my Ted talk.
@novaburst Yeah that's literally how I manage my Vim plugins too πŸ˜†
@novaburst Yeah that's literally how I manage my Vim plugins too πŸ˜†
@prologic I've been doing this, very happy https://blog.sanctum.geek.nz/series/unix-as-ide/
@prologic @novaburst @adi Another way it to have ~/.vim/ in a repo with submodules of the plugins you want, this way you can move everything in one go.
@justamoment https://git.076.ne.jp/novaburst/home/src/branch/main/.vim/pack/dist/start
mind you, even though there's no systemd on FreeBSD, i write units for use in novaburst.de1.hashbang.sh
@novaburst You're already ahead of me. πŸ’ͺπŸ˜‰

I manage them with the home-manager configuration in my NixOS setup instead, same result as submodules.
@justamoment meanwhile systemd-homed: exists
@novaburst Nice, didn't know about it 😲. I probably won't use it though, as long as I have my vim, terminal and wm config I'm good to go.

Everything that's not under git is throwaway for me and NixOS let me keep even packages in it.

I also work a lot via SSH and systemd-homed seems to not support that, but it was just a quick search I did right now, maybe it actually works.

@novaburst Do you use it?
@justamoment

> there's no systemd on FreeBSD

#2p6q6ka
@novaburst Oh, sorry didn't catch that before. 😯
@novaburst Vim plugin managers (like β€œPathogen”) predate the built-in plugin system of Vim, don’t they? πŸ€” IIRC, this feature was only introduced in Vim 8 (2016). But I have no idea why things like Pathogen *still* exist today. πŸ₯΄
@novaburst Vim plugin managers (like β€œPathogen”) predate the built-in plugin system of Vim, don’t they? πŸ€” IIRC, this feature was only introduced in Vim 8 (2016). But I have no idea why things like Pathogen *still* exist today. πŸ₯΄
@novaburst Vim plugin managers (like β€œPathogen”) predate the built-in plugin system of Vim, don’t they? πŸ€” IIRC, this feature was only introduced in Vim 8 (2016). But I have no idea why things like Pathogen *still* exist today. πŸ₯΄
@movq because these managers _still_ work. πŸ˜‰

If they have it already configured, whenever they upgrade to a newer version they won't bother migrating what is already working fine, for that reason those projects will keep holding their users and people would continue working on them.

Also, since those projects are still pretty popular even new users that are looking at how to install plugins for the first time will end up with all those 3rd party managers before even knowing the availability of a built-in option.
> I’ve been doing this, very happy https://blog.sanctum.geek.nz/series/unix-as-ide/

Meaning I don't manage plugins.
@justamoment Probably true. I just wonder: Had I made such a 3rd party plugin, would I have stopped its development once Vim 8 landed?

Ah, haha, look at that: There is a notice in Pathogen:

https://github.com/tpope/vim-pathogen

> For new users, I recommend using Vim's built-in package management instead.

And it used to look like this:

https://github.com/tpope/vim-pathogen/commit/e9fb0914dba5bdfe2feaa364dda2e9495c5620a2

Apparently, a clear deprecation warning scared people? πŸ˜…
@justamoment Probably true. I just wonder: Had I made such a 3rd party plugin, would I have stopped its development once Vim 8 landed?

Ah, haha, look at that: There is a notice in Pathogen:

https://github.com/tpope/vim-pathogen

> For new users, I recommend using Vim's built-in package management instead.

And it used to look like this:

https://github.com/tpope/vim-pathogen/commit/e9fb0914dba5bdfe2feaa364dda2e9495c5620a2

Apparently, a clear deprecation warning scared people? πŸ˜…
@justamoment Probably true. I just wonder: Had I made such a 3rd party plugin, would I have stopped its development once Vim 8 landed?

Ah, haha, look at that: There is a notice in Pathogen:

https://github.com/tpope/vim-pathogen

> For new users, I recommend using Vim's built-in package management instead.

And it used to look like this:

https://github.com/tpope/vim-pathogen/commit/e9fb0914dba5bdfe2feaa364dda2e9495c5620a2

Apparently, a clear deprecation warning scared people? πŸ˜…
@movq that's probably for new users that are still struggling with everything.

Maybe someone should go around every plugin manager and leave an issue about the deprecation, I'm curious about their reply. 😏
@justamoment Do it! πŸΏπŸ˜ˆπŸ˜‰
@justamoment Do it! πŸΏπŸ˜ˆπŸ˜‰
@justamoment Do it! πŸΏπŸ˜ˆπŸ˜‰
@movq No thanks, too much bother, I'll gladly watch if someone else try. πŸ™ƒ