Hi !

# Introducing wet and libGwit

I have been developping wet, a minimal gwit client, for a month or so.
I started it as a development target for libgwit, a python lib for Gwit.

=> https://framagit.org/matograine/wet/
=> https://framagit.org/matograine/libgwit/

With wet, you can :
- browse gwit sites
- list your local sites, and the introduced sites
- display details about sites

## Development state

It is not stable yet, not packaged, but it implements the spec.

Tests are far from perfect :
- Based on real gwit sites that may change
- Most notably, the rewrite algorithm has not been tested.
- No unit test, only global tests (but I don't plan to enhance this part)

So, I still have to create some gwit sites for testing purpose.
This will certainly be useful for other client's developers.

Libgwit, on its side, has no automated testing at all, nor packaging. So 
it is clearly not ready to be used as a lib in other projects.

## Plans

I plan to :

- package wet and publish on PyPi
- add some more features (see FEATURES.md)
- package libGwit and publish on PyPi
- write unit tests for libGwit

Once this is done :

- use wet to write a gwit plugin for Dillo web browser
- use libgwit to implement gwit support for Offpunk

=> https://dillo-browser.github.io/#plugins plugins for dillo
=> https://offpunk.net/

## Contributions ?

I will be happy to receive bug reports.



Thanks for reading,

Matograine

matograine (2025-02-15 08:56:40 +0100) wrote:

> Hi !
> 
> # Introducing wet and libGwit
> 
> I have been developping wet, a minimal gwit client, for a month or so.
> I started it as a development target for libgwit, a python lib for Gwit.
> 
> => https://framagit.org/matograine/wet/
> => https://framagit.org/matograine/libgwit/
> 
> With wet, you can :
> - browse gwit sites
> - list your local sites, and the introduced sites
> - display details about sites
> 
> ## Development state
> 
> It is not stable yet, not packaged, but it implements the spec. […]

Hi matograine!  Wow, I'm so happy to read this… the very first fuctional gwit
client! 🎉  And, according to docs, it's quite complete and it looks
user-friendly too.

My congratulations and deep thanks for putting the effort into making gwit
something that people can actually use! 🙏  I'll give it a try when I have
some time and report back, and I'll add links in the project page ASAP.

----

And now for the surreal part…  I was just about to release another gwit client
which I've been (very slowly) developing during the last months.  It's not as
advanced as wet (by far!), nor as user friendly, as its purpose is to test
example commands in the spec, maybe act as a reference implementation, and
have really minimal dependencies: <https://git.sr.ht/~ivilata/gwish>

I'll do the formal introduction later in another thread (I don't want to
hijack wet's introduction), but it'd be nice to coordinate to keep them
compatible when useful (e.g. so that they can share mirrored sites).

Thanks again and congrats!

-- 
Ivan Vilata i Balaguer -- https://elvil.net/

Ivan Vilata i Balaguer (2025-02-15 21:37:52 +0100) wrote:

> matograine (2025-02-15 08:56:40 +0100) wrote:
> 
> > I have been developping wet, a minimal gwit client, for a month or so.
> > I started it as a development target for libgwit, a python lib for Gwit.
> 
> And now for the surreal part…  I was just about to release another gwit client
> which I've been (very slowly) developing during the last months. […]
> 
> I'll do the formal introduction later in another thread (I don't want to
> hijack wet's introduction), but it'd be nice to coordinate to keep them
> compatible when useful (e.g. so that they can share mirrored sites).

gwish was storing sites as `$XDG_DATA_HOME/gwit/0x<SITE-ID>.git`, I changed
that to `…/gwit/sites/0x<SITE-ID>.git` so that gwish doesn't clutter the
`gwit` directory, and both Wet and gwish place sites in the same place.
Reusing each other's mirrors may be more involved since Wet uses Git working
trees and gwish bare repos, but I've checked that the arrangement at least
doesn't cause failures (e.g. when listing mirrored sites).

Cheers!

-- 
Ivan Vilata i Balaguer -- https://elvil.net/

Hi !

> gwish was storing sites as `$XDG_DATA_HOME/gwit/0x<SITE-ID>.git`, I changed
> that to `…/gwit/sites/0x<SITE-ID>.git` so that gwish doesn't clutter the
> `gwit` directory, and both Wet and gwish place sites in the same place.

Thanks !

> Reusing each other's mirrors may be more involved since Wet uses Git working
> trees and gwish bare repos, but I've checked that the arrangement at least
> doesn't cause failures (e.g. when listing mirrored sites).

I have to learn more about bare repos.

Anyway, I have written tests for wet (still not for the rewrite algo) 
and fixed some bugs along the way.

I created a repo containing test sites, that will be useful for other 
developers. Naturally, there is a gwit site to present these ;-) :

=> 
gwit://0x5b5a404b647a24c78f1a8efb2186a7ed03a08821#??https://framagit.org/matograine/gwit-tests.git

You may want to test gwish on these.

Sincerely,

Matograine

matograine (2025-03-08 10:16:51 +0100) wrote:

> Anyway, I have written tests for wet (still not for the rewrite algo) and
> fixed some bugs along the way.
> 
> I created a repo containing test sites, that will be useful for other
> developers. Naturally, there is a gwit site to present these ;-) :
> 
> => gwit://0x5b5a404b647a24c78f1a8efb2186a7ed03a08821#??https://framagit.org/matograine/gwit-tests.git
> 
> You may want to test gwish on these.

Hi Matograine, this is a very useful effort, thanks a lot!  I'll tell you if I
come up with additional interesting scenarios to add there.

For the moment `gwish check` seems to handle the different sites correctly! 🙂

Cheers,

-- 
Ivan Vilata i Balaguer -- https://elvil.net/