# 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 42
# self = https://watcher.sour.is/conv/zajxjga
First test post from GTK UI!
Reply button seems to work!
Time for a new screenshot :)
So glad I switched to GTK4, so much easier to work with then FLTK.
Going out for a hike with the dog. Then I'll code a bit later today.
Want to fix the timeline refresh, and then create one timeline for each timeline, and buttons to switch between them.
Need to rework the timeline a bit, I want it to append new statuses after refresh, right now it fetches the whole timeline and just inserts it as a whole. So I'll work on that alongside the refresh functionality.
Moving my source to git today, I have just developed on a local copy until today.
I needed to move it before going too crazy with it. Starting the work on the timeline that I've mentioned.
Yesterday I ran out of time, but today I have some free time to work on things. Very pleased with the software already, I know I'll use it all the time. So today I will work on refreshing the timeline, and then fix so that it's a bit smarter then now, the class that holds the statuses will also contain the GUI elements for each status, that way I can more easily append new statuses into the timeline - instead of grabbing the whole timeline and rebuild all it's gui each time it refreshes. I know what to do - so I do not expect it to take too long to fix.
Also - I would like to know where you all like to have git hosted..
Github? Some other place? Do you mind self-hosted git servers? (I currently have my own)..
What do you all prefer? Do you mind compiling software from source if instructions are clear and easy? Or do you prefer to download a released binary and run that?
I also later on (as soon as it's in usable state) want to make flatpack, appimage as well, that is something I have not done before - but I want to set that up as well.
@stigatle My two cents worth:
- self-hosted git
- both good build instructions.+ release binaires for the lazy
- don't trust Github (or copilot) with your hard work 😅
@stigatle My two cents worth:
- self-hosted git
- both good build instructions.+ release binaires for the lazy
- don't trust Github (or copilot) with your hard work 😅
@stigatle My two cents worth:
- self-hosted git
- both good build instructions.+ release binaires for the lazy
- don't trust Github (or copilot) with your hard work 😅
@prologic I agree with you points, and I feel the same.
I currently run a gogs instance on my webserver, I'm putting my source there for now.
Currently registrations are disabled and such, I'm the only user, that is the main issue I think - people need to register to submit a change. and I do not want people to register on my own git instance either, so I have to think about it a bit.
@stigatle Just add instructions to the README.md to let folks know you only accept patches. Provide somewhere to dump them or such. Or ask folks to Twtxt you a link to their clone 🤣
@stigatle Just add instructions to the README.md to let folks know you only accept patches. Provide somewhere to dump them or such. Or ask folks to Twtxt you a link to their clone 🤣
@stigatle Just add instructions to the README.md to let folks know you only accept patches. Provide somewhere to dump them or such. Or ask folks to Twtxt you a link to their clone 🤣
@stigatle I also prefer to host my own code myself. My mates and I have a server and there we run GitLab. But I only use GitLab because it is there. It would totally suffice me to use the filesystem for a bare git repo. I don't need all this fancy UI that GitLab or any other web UI brings. For bringing it to the public, making the git repo available over a webserver would be enough for me.
It depends on the project, its dependencies and the toolchain required to build it. But generally, compiling from source is fine with me, if I have all the tools on my system anyways. If somebody offered a Debian package, that would certainly be appreciated. These days, I rarely try out new software, though.
@lyse We use gitlab daily at work. but for my own projects I use gogs. I have some scripts that I used for a gnusocial client that I maintained (before leaving gnusocial). I'll see if I can adapt that and make deb files for the yarn client - I mostly use debian \\ Trisquel my self, so I also like .deb as well.
@lyse We use gitlab daily at work. but for my own projects I use gogs. I have some scripts that I used for a gnusocial client that I maintained (before leaving gnusocial). I'll see if I can adapt that and make deb files for the yarn client - I mostly use debian \ Trisquel my self, so I also like .deb as well.
Added refresh of the timeline, currently a button that you press to do so, I will move it to a timed function shortly.. But nice to get something added tonight.
One thing I need to also fix - is the way a reply is done, I need it to add the mentions as well, so that you can reply to a person more easily, instead of just the thread.
So now it looks like this:
Progress - progress, love it when things fall into place.
If you hit 'reply' on a post it fills in the mentions as well in the status entry box.
I added all the timelines, so now you can switch between 'discover', 'timeline' and mentions from the drop down menu :)
Cool, cool, cool, @stigatle! It's coming together. I reckon a wee bit of padding in the window wouldn't hurt. :-)
@lyse Thank you! Yeah I fixed that now, short statuses got shifted, but that has been fixed. :)
@stigatle This is coming along real nice 👌
@stigatle This is coming along real nice 👌
@stigatle This is coming along real nice 👌
@prologic Yeah, good point. I will see if I can selfhost it in a good way, I'll think about it for the next days, I'll also create a subdomain on my website where I can put some info and git links and what not, nice to have a info page to link back to from the application.
@prologic it's mostly ready now I feel, got a lot done, so I'll focus on getting it out there this week, A bit busy the next days, but I'm sure I'll find time to get it uploaded and hosted on my VPS so that others can use it as well.