# 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 61083
# self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=41691
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=41791
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=41591
prologic
twtxt.net
View Thread
@abucci Oh it got really bad IMO. I left the community as a result of the disgusting shit I was seeing out of the bitreich.org folks 🀯
prologic
twtxt.net
View Thread
@logout I still have no idea, but I'll believe you πŸ˜… I wouldn't even know where to start even if I wanted to 🀣
prologic
twtxt.net
View Thread
@logout I still have no idea, but I'll believe you πŸ˜… I wouldn't even know where to start even if I wanted to 🀣
prologic
twtxt.net
View Thread
@logout I still have no idea, but I'll believe you πŸ˜… I wouldn't even know where to start even if I wanted to 🀣
prologic
twtxt.net
View Thread
@logout I still have no idea, but I'll believe you πŸ˜… I wouldn't even know where to start even if I wanted to 🀣
prologic
twtxt.net
View Thread
@justamoment Yeah I'm kind of thinking that the JSON API / REST API + SSR Templating calls a "middle" layer. In other words, abstract out the actual data handling and logic with interfaces that can be used for a real response directly (content negotiated) or rendered with some HTML templates.
prologic
twtxt.net
View Thread
@justamoment Yeah I'm kind of thinking that the JSON API / REST API + SSR Templating calls a "middle" layer. In other words, abstract out the actual data handling and logic with interfaces that can be used for a real response directly (content negotiated) or rendered with some HTML templates.
prologic
twtxt.net
View Thread
@justamoment Yeah I'm kind of thinking that the JSON API / REST API + SSR Templating calls a "middle" layer. In other words, abstract out the actual data handling and logic with interfaces that can be used for a real response directly (content negotiated) or rendered with some HTML templates.
prologic
twtxt.net
View Thread
@justamoment Yeah I'm kind of thinking that the JSON API / REST API + SSR Templating calls a "middle" layer. In other words, abstract out the actual data handling and logic with interfaces that can be used for a real response directly (content negotiated) or rendered with some HTML templates.
prologic
twtxt.net
View Thread
@abucci As-is gitwt.dev 🀣
prologic
twtxt.net
View Thread
@abucci As-is gitwt.dev 🀣
prologic
twtxt.net
View Thread
@abucci As-is gitwt.dev 🀣
prologic
twtxt.net
View Thread
@abucci As-is gitwt.dev 🀣
prologic
twtxt.net
View Thread
@abucci I did the same πŸ˜…
prologic
twtxt.net
View Thread
@abucci I did the same πŸ˜…
prologic
twtxt.net
View Thread
@abucci I did the same πŸ˜…
prologic
twtxt.net
View Thread
@abucci I did the same πŸ˜…
prologic
twtxt.net
View Thread
@abucci Don't blame you 🀣
prologic
twtxt.net
View Thread
@abucci Don't blame you 🀣
prologic
twtxt.net
View Thread
@abucci Don't blame you 🀣
prologic
twtxt.net
View Thread
@abucci Don't blame you 🀣
prologic
twtxt.net
View Thread
@abucci You should see my outrage at the Gopher mailing list some years ago regarding some of the "asshole" attitude of these guys πŸ˜…
prologic
twtxt.net
View Thread
@abucci You should see my outrage at the Gopher mailing list some years ago regarding some of the "asshole" attitude of these guys πŸ˜…
prologic
twtxt.net
View Thread
@abucci You should see my outrage at the Gopher mailing list some years ago regarding some of the "asshole" attitude of these guys πŸ˜…
prologic
twtxt.net
View Thread
@abucci You should see my outrage at the Gopher mailing list some years ago regarding some of the "asshole" attitude of these guys πŸ˜…
prologic
twtxt.net
View Thread
@abucci Pronounced "git" "wit" right? πŸ˜…
prologic
twtxt.net
View Thread
@abucci Pronounced "git" "wit" right? πŸ˜…
prologic
twtxt.net
View Thread
@abucci Pronounced "git" "wit" right? πŸ˜…
prologic
twtxt.net
View Thread
@abucci Pronounced "git" "wit" right? πŸ˜…
prologic
twtxt.net
View Thread
@justamoment So, we'll build a few data models that represents data we need to store and mutate and some logic to fetch that data and perform actions on it. Then an API layer will use that and serialise as either a JSON RPC API or JSON Rest API. Another layer will call the same code to fill out template contexts and render templates. Does this sound about right? πŸ€”
prologic
twtxt.net
View Thread
@justamoment So, we'll build a few data models that represents data we need to store and mutate and some logic to fetch that data and perform actions on it. Then an API layer will use that and serialise as either a JSON RPC API or JSON Rest API. Another layer will call the same code to fill out template contexts and render templates. Does this sound about right? πŸ€”
prologic
twtxt.net
View Thread
@justamoment So, we'll build a few data models that represents data we need to store and mutate and some logic to fetch that data and perform actions on it. Then an API layer will use that and serialise as either a JSON RPC API or JSON Rest API. Another layer will call the same code to fill out template contexts and render templates. Does this sound about right? πŸ€”
prologic
twtxt.net
View Thread
@justamoment So, we'll build a few data models that represents data we need to store and mutate and some logic to fetch that data and perform actions on it. Then an API layer will use that and serialise as either a JSON RPC API or JSON Rest API. Another layer will call the same code to fill out template contexts and render templates. Does this sound about right? πŸ€”
prologic
twtxt.net
View Thread
@justamoment Yup πŸ‘Œ I'm going to experiment on someyhing a bit contrived add aee what pattern I can come up with 🀞
prologic
twtxt.net
View Thread
@justamoment Yup πŸ‘Œ I'm going to experiment on someyhing a bit contrived add aee what pattern I can come up with 🀞
prologic
twtxt.net
View Thread
@justamoment Yup πŸ‘Œ I'm going to experiment on someyhing a bit contrived add aee what pattern I can come up with 🀞
prologic
twtxt.net
View Thread
@justamoment Yup πŸ‘Œ I'm going to experiment on someyhing a bit contrived add aee what pattern I can come up with 🀞
prologic
twtxt.net
View Thread
https://github.com/dotenx/dotenx -- Hmm what the hell is this?! 😳 πŸ€”
prologic
twtxt.net
View Thread
https://github.com/dotenx/dotenx -- Hmm what the hell is this?! 😳 πŸ€”
prologic
twtxt.net
View Thread
https://github.com/dotenx/dotenx -- Hmm what the hell is this?! 😳 πŸ€”
prologic
twtxt.net
View Thread
https://github.com/dotenx/dotenx -- Hmm what the hell is this?! 😳 πŸ€”
prologic
twtxt.net
View Thread
Too bad git.social is taken πŸ˜… It would have made a great domain and project name, but you are on to something 😍
prologic
twtxt.net
View Thread
Too bad git.social is taken πŸ˜… It would have made a great domain and project name, but you are on to something 😍
prologic
twtxt.net
View Thread
Too bad git.social is taken πŸ˜… It would have made a great domain and project name, but you are on to something 😍
prologic
twtxt.net
View Thread
Too bad git.social is taken πŸ˜… It would have made a great domain and project name, but you are on to something 😍
prologic
twtxt.net
View Thread
@justamoment I love ti 😍
prologic
twtxt.net
View Thread
@justamoment I love ti 😍
prologic
twtxt.net
View Thread
@justamoment I love ti 😍
prologic
twtxt.net
View Thread
@justamoment I love ti 😍
prologic
twtxt.net
View Thread
@justamoment Yeah I have a few ideas for how to structure this, but I've never seen anyone do it, probably because these days everyone just does this React shitβ„’ 🀣 Gotta give this a try though... πŸ€”
prologic
twtxt.net
View Thread
@justamoment Yeah I have a few ideas for how to structure this, but I've never seen anyone do it, probably because these days everyone just does this React shitβ„’ 🀣 Gotta give this a try though... πŸ€”
prologic
twtxt.net
View Thread
@justamoment Yeah I have a few ideas for how to structure this, but I've never seen anyone do it, probably because these days everyone just does this React shitβ„’ 🀣 Gotta give this a try though... πŸ€”
prologic
twtxt.net
View Thread
@justamoment Yeah I have a few ideas for how to structure this, but I've never seen anyone do it, probably because these days everyone just does this React shitβ„’ 🀣 Gotta give this a try though... πŸ€”
prologic
twtxt.net
View Thread
@justamoment I'm still _thinking_ about how we can make Git + Twtxt work in a way that is a sort-of "socialised" collaboration of a Git repo's issues and reviews of patches... πŸ˜…
prologic
twtxt.net
View Thread
@justamoment I'm still _thinking_ about how we can make Git + Twtxt work in a way that is a sort-of "socialised" collaboration of a Git repo's issues and reviews of patches... πŸ˜…
prologic
twtxt.net
View Thread
@justamoment I'm still _thinking_ about how we can make Git + Twtxt work in a way that is a sort-of "socialised" collaboration of a Git repo's issues and reviews of patches... πŸ˜…
prologic
twtxt.net
View Thread
@justamoment I'm still _thinking_ about how we can make Git + Twtxt work in a way that is a sort-of "socialised" collaboration of a Git repo's issues and reviews of patches... πŸ˜…
prologic
twtxt.net
View Thread
@justamoment Yeah that's another pretty similar way of doing the same thing I guess? Basically a bunch of files in the same repo in even a separate repo right? πŸ€”
prologic
twtxt.net
View Thread
@justamoment Yeah that's another pretty similar way of doing the same thing I guess? Basically a bunch of files in the same repo in even a separate repo right? πŸ€”
prologic
twtxt.net
View Thread
@justamoment Yeah that's another pretty similar way of doing the same thing I guess? Basically a bunch of files in the same repo in even a separate repo right? πŸ€”
prologic
twtxt.net
View Thread
@justamoment Yeah that's another pretty similar way of doing the same thing I guess? Basically a bunch of files in the same repo in even a separate repo right? πŸ€”
prologic
twtxt.net
View Thread
@justamoment Can we still maintain a nice SSR (Server-side Rendered) UI though? This is something I _never_ quite managed to "get right", it would be nice to not have any Javascript (or ever little) for the UI but to still power the SSR and API with the same data structures (which is what I think you're talking about?)
prologic
twtxt.net
View Thread
@justamoment Can we still maintain a nice SSR (Server-side Rendered) UI though? This is something I _never_ quite managed to "get right", it would be nice to not have any Javascript (or ever little) for the UI but to still power the SSR and API with the same data structures (which is what I think you're talking about?)
prologic
twtxt.net
View Thread
@justamoment Can we still maintain a nice SSR (Server-side Rendered) UI though? This is something I _never_ quite managed to "get right", it would be nice to not have any Javascript (or ever little) for the UI but to still power the SSR and API with the same data structures (which is what I think you're talking about?)
prologic
twtxt.net
View Thread
@justamoment Can we still maintain a nice SSR (Server-side Rendered) UI though? This is something I _never_ quite managed to "get right", it would be nice to not have any Javascript (or ever little) for the UI but to still power the SSR and API with the same data structures (which is what I think you're talking about?)
prologic
twtxt.net
View Thread
Very cool πŸ‘Œ
prologic
twtxt.net
View Thread
Very cool πŸ‘Œ
prologic
twtxt.net
View Thread
Very cool πŸ‘Œ
prologic
twtxt.net
View Thread
Very cool πŸ‘Œ
prologic
twtxt.net
View Thread
@justamoment I _think_, at least that's the idea, and it _allegedly_ doesn't pollute the actual repo with unrelated files (I don't think) -- I still haven't been able to get it to work locally though so hoping someone will answer my comment on the issue. But yeah depending on how git-bug evolves over time we _could_ just integrate with it "somehow"
prologic
twtxt.net
View Thread
@justamoment I _think_, at least that's the idea, and it _allegedly_ doesn't pollute the actual repo with unrelated files (I don't think) -- I still haven't been able to get it to work locally though so hoping someone will answer my comment on the issue. But yeah depending on how git-bug evolves over time we _could_ just integrate with it "somehow"
prologic
twtxt.net
View Thread
@justamoment I _think_, at least that's the idea, and it _allegedly_ doesn't pollute the actual repo with unrelated files (I don't think) -- I still haven't been able to get it to work locally though so hoping someone will answer my comment on the issue. But yeah depending on how git-bug evolves over time we _could_ just integrate with it "somehow"
prologic
twtxt.net
View Thread
@justamoment I _think_, at least that's the idea, and it _allegedly_ doesn't pollute the actual repo with unrelated files (I don't think) -- I still haven't been able to get it to work locally though so hoping someone will answer my comment on the issue. But yeah depending on how git-bug evolves over time we _could_ just integrate with it "somehow"
prologic
twtxt.net
View Thread
@justamoment I guess we start with:

- An interface to manager repos
- Support for git push over SSH with key management

What already works (mostly):

- Hosting
- Cloning via git clone over HTTP/SSH

What still needs consideration/experimentation:

- Code reviews
- Issue tracking
prologic
twtxt.net
View Thread
@justamoment I guess we start with:

- An interface to manager repos
- Support for git push over SSH with key management

What already works (mostly):

- Hosting
- Cloning via git clone over HTTP/SSH

What still needs consideration/experimentation:

- Code reviews
- Issue tracking
prologic
twtxt.net
View Thread
@justamoment I guess we start with:

- An interface to manager repos
- Support for git push over SSH with key management

What already works (mostly):

- Hosting
- Cloning via git clone over HTTP/SSH

What still needs consideration/experimentation:

- Code reviews
- Issue tracking
prologic
twtxt.net
View Thread
@justamoment I guess we start with:

- An interface to manager repos
- Support for git push over SSH with key management

What already works (mostly):

- Hosting
- Cloning via git clone over HTTP/SSH

What still needs consideration/experimentation:

- Code reviews
- Issue tracking
prologic
twtxt.net
View Thread
@justamoment Some good ideas for a project name there πŸ‘Œ Hmmm πŸ€”
prologic
twtxt.net
View Thread
@justamoment Some good ideas for a project name there πŸ‘Œ Hmmm πŸ€”
prologic
twtxt.net
View Thread
@justamoment Some good ideas for a project name there πŸ‘Œ Hmmm πŸ€”
prologic
twtxt.net
View Thread
@justamoment Some good ideas for a project name there πŸ‘Œ Hmmm πŸ€”
prologic
twtxt.net
View Thread
Gah I had to reboot my cluster 🀯
prologic
twtxt.net
View Thread
Gah I had to reboot my cluster 🀯
prologic
twtxt.net
View Thread
Gah I had to reboot my cluster 🀯
prologic
twtxt.net
View Thread
Gah I had to reboot my cluster 🀯
prologic
twtxt.net
View Thread
@abucci Oh! Yes of course! 🀣 Eva πŸ˜…
prologic
twtxt.net
View Thread
@abucci Oh! Yes of course! 🀣 Eva πŸ˜…
prologic
twtxt.net
View Thread
@abucci Oh! Yes of course! 🀣 Eva πŸ˜…
prologic
twtxt.net
View Thread
@abucci Oh! Yes of course! 🀣 Eva πŸ˜…
prologic
twtxt.net
View Thread
I need some ARM64 servers in my DC 🀣 I wouldn't have to do this but for the fact that my workstation is now an ARM (Apple Silicon M1) πŸ˜…
prologic
twtxt.net
View Thread
I need some ARM64 servers in my DC 🀣 I wouldn't have to do this but for the fact that my workstation is now an ARM (Apple Silicon M1) πŸ˜…
prologic
twtxt.net
View Thread
I need some ARM64 servers in my DC 🀣 I wouldn't have to do this but for the fact that my workstation is now an ARM (Apple Silicon M1) πŸ˜…
prologic
twtxt.net
View Thread
I need some ARM64 servers in my DC 🀣 I wouldn't have to do this but for the fact that my workstation is now an ARM (Apple Silicon M1) πŸ˜…
prologic
twtxt.net
View Thread
[How to build x86 (and others!) Docker images on an M1 Mac – Jaimyn's Blog](https://blog.jaimyn.dev/how-to-build-multi-architecture-docker-images-on-an-m1-mac/) -- TL;DR:


docker buildx create --use
docker buildx build --platform linux/amd64,linux/arm64 --push -t <tag_to_push> <context_path>
prologic
twtxt.net
View Thread
[How to build x86 (and others!) Docker images on an M1 Mac – Jaimyn's Blog](https://blog.jaimyn.dev/how-to-build-multi-architecture-docker-images-on-an-m1-mac/) -- TL;DR:


docker buildx create --use
docker buildx build --platform linux/amd64,linux/arm64 --push -t <tag_to_push> <context_path>
prologic
twtxt.net
View Thread
[How to build x86 (and others!) Docker images on an M1 Mac – Jaimyn's Blog](https://blog.jaimyn.dev/how-to-build-multi-architecture-docker-images-on-an-m1-mac/) -- TL;DR:


docker buildx create --use
docker buildx build --platform linux/amd64,linux/arm64 --push -t <tag_to_push> <context_path>
prologic
twtxt.net
View Thread
[How to build x86 (and others!) Docker images on an M1 Mac – Jaimyn's Blog](https://blog.jaimyn.dev/how-to-build-multi-architecture-docker-images-on-an-m1-mac/) -- TL;DR:


docker buildx create --use
docker buildx build --platform linux/amd64,linux/arm64 --push -t <tag_to_push> <context_path>
prologic
twtxt.net
View Thread
Either that or its a family with members Paul, Sue and Mark 🀣
prologic
twtxt.net
View Thread
Either that or its a family with members Paul, Sue and Mark 🀣
prologic
twtxt.net
View Thread
Either that or its a family with members Paul, Sue and Mark 🀣