(#xxxxxx) not (#xxxxxx@twtxt) 🤣
(#xxxxxx) not (#xxxxxx@twtxt) 🤣
(#xxxxxx) not (#xxxxxx@twtxt) 🤣
I have fixed the weird tags thing, I removed it from the twtxt manually, I don't think it'll affect anything? I wrote a patch for jenny (twtxt to mbox converter), and I did test it in a sense in that messsage, because jenny wasn't making RFC compliant emails and aerc in newer versions needs the emails to be compliant, else it doesn't seem to be able to do threading.
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.
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 🤣
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 🤣
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 🤣
Also PS: What's with the weird subject in your Twt? That doesn't confirm to any specs I know 😅
Also PS: What's with the weird subject in your Twt? That doesn't confirm to any specs I know 😅
Also PS: What's with the weird subject in your Twt? That doesn't confirm to any specs I know 😅
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.
I don't know if I should set it up, I know that for my personal projects
it will be sufficient, but I don't know how well it'd scale with a
pubnix-like system. I know the linux kernel uses gitolite but I don't
know, as the use by us would be completly different, it'd be more suited
to
organizations), but I also dislike not having the gitolite ui in gitea,
so I might think about making custom scripts to let you make projects
(that are outside your user namescope, but assigning you privileges, (I
think I'd need to or a) make the script directly add the projects, thus
making me
git pull the gitolite-admin repo, but I'd alredy have to dothat as I'd use sskm, or b) Having the requests come in to my mailbox
and I manually add their respective config block to gitolite's config in
the gitolite-admin )
- self-hosted git
- both good build instructions.+ release binaires for the lazy
- don't trust Github (or copilot) with your hard work 😅
- self-hosted git
- both good build instructions.+ release binaires for the lazy
- don't trust Github (or copilot) with your hard work 😅
- self-hosted git
- both good build instructions.+ release binaires for the lazy
- don't trust Github (or copilot) with your hard work 😅
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.
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.
> Generative Pre-trained Transformer 3 (GPT-3) is an autoregressive language model released in 2020 that uses deep learning to produce human-like text. Given an initial text as prompt, it will produce text that continues the prompt.
Which is even more confusing to me, mostly because it doesn't speak of a neural network at all. Basically I was (on my short-lived holiday) doing some R&D on neural networks, evolutionary algorithms and other reading 😅
> Generative Pre-trained Transformer 3 (GPT-3) is an autoregressive language model released in 2020 that uses deep learning to produce human-like text. Given an initial text as prompt, it will produce text that continues the prompt.
Which is even more confusing to me, mostly because it doesn't speak of a neural network at all. Basically I was (on my short-lived holiday) doing some R&D on neural networks, evolutionary algorithms and other reading 😅
> Generative Pre-trained Transformer 3 (GPT-3) is an autoregressive language model released in 2020 that uses deep learning to produce human-like text. Given an initial text as prompt, it will produce text that continues the prompt.
Which is even more confusing to me, mostly because it doesn't speak of a neural network at all. Basically I was (on my short-lived holiday) doing some R&D on neural networks, evolutionary algorithms and other reading 😅
- Provide out-of-band access to my infra for emergencies (needs 4G/LET connectivity)
- Provide access to internal (private) resources for teams (currently do this via Authelia)
- Provide out-of-band access to my infra for emergencies (needs 4G/LET connectivity)
- Provide access to internal (private) resources for teams (currently do this via Authelia)
- Provide out-of-band access to my infra for emergencies (needs 4G/LET connectivity)
- Provide access to internal (private) resources for teams (currently do this via Authelia)
- juanfont/headscale: An open source, self-hosted implementation of the Tailscale control server
- slackhq/nebula: A scalable overlay networking tool with a focus on performance, simplicity and security
- gravitl/netmaker: Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.
- juanfont/headscale: An open source, self-hosted implementation of the Tailscale control server
- slackhq/nebula: A scalable overlay networking tool with a focus on performance, simplicity and security
- gravitl/netmaker: Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.
- Tailscale · Best VPN Service for Secure Networks headscale/index.md at main · juanfont/headscale · GitHub
- slackhq/nebula: A scalable overlay networking tool with a focus on performance, simplicity and security
- gravitl/netmaker: Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.
- juanfont/headscale: An open source, self-hosted implementation of the Tailscale control server
- slackhq/nebula: A scalable overlay networking tool with a focus on performance, simplicity and security
- gravitl/netmaker: Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.
- Tailscale · Best VPN Service for Secure Networks headscale/index.md at main · juanfont/headscale · GitHub
- slackhq/nebula: A scalable overlay networking tool with a focus on performance, simplicity and security
- gravitl/netmaker: Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.
I notice it uses WirGuard™ and is actually written in Go 😅
I notice it uses WirGuard™ and is actually written in Go 😅
I notice it uses WirGuard™ and is actually written in Go 😅
Likely culprit, storm/water damage to the copper that's been sitting in the ground for some ~30+ years or so and never been replaced.
Thanks NBN Co 🤦♂️ #NBN~
Likely culprit, storm/water damage to the copper that's been sitting in the ground for some ~30+ years or so and never been replaced.
Thanks NBN Co 🤦♂️ #NBN~
Likely culprit, storm/water damage to the copper that's been sitting in the ground for some ~30+ years or so and never been replaced.
Thanks NBN Co 🤦♂️ #NBN~
#running
#running
#running
#running
#running
#running
#running
#running