main branch is totally fine. In fact encouraged. I have a philosophy of main being stable anyway and making sure backwards compatibility is kept in mind when changing things. i.e: No database migrations to run by hand or what not.
main branch is totally fine. In fact encouraged. I have a philosophy of main being stable anyway and making sure backwards compatibility is kept in mind when changing things. i.e: No database migrations to run by hand or what not.
Twt Subject extension is implemented in yarnd and now apparently jenny π€£π€£ Where it strips out the subject from the displayed/rendered content. Which is what you want... But oh well haha π
Twt Subject extension is implemented in yarnd and now apparently jenny π€£π€£ Where it strips out the subject from the displayed/rendered content. Which is what you want... But oh well haha π
yarnd are stored under /path/to/data under the feeds directory. Oner per user.
yarnd are stored under /path/to/data under the feeds directory. Oner per user.
> Was there ever a reason to do that? π€
I'm not sure to be honest. I have no idea why you'd ever want to do a "nameless" @-mention.
As an aside, if we could all agree, I'd personally just say we scrap this whole fragile broken shit and bring out WebMentions and be done with it. And then mentions are always
@nick@domain and looked up, cached and can never be screwed up haha π€£
> Was there ever a reason to do that? π€
I'm not sure to be honest. I have no idea why you'd ever want to do a "nameless" @-mention.
As an aside, if we could all agree, I'd personally just say we scrap this whole fragile broken shit and bring out WebMentions and be done with it. And then mentions are always
@nick@domain and looked up, cached and can never be screwed up haha π€£
> Whatβs the motivation for deprecation?
Namely that without the mention having a label (_as such_) it becomes very hard to render it in any sane/nice way. I think we should just stick to
@<label url> personally. It makes implementations have to worry about far less edge cases.
> Whatβs the motivation for deprecation?
Namely that without the mention having a label (_as such_) it becomes very hard to render it in any sane/nice way. I think we should just stick to
@<label url> personally. It makes implementations have to worry about far less edge cases.
Makefile or something. I'm not sure what version @kat built/deployed from? π€π€ -- Also I need to release v2.0 soonβ’
Makefile or something. I'm not sure what version @kat built/deployed from? π€π€ -- Also I need to release v2.0 soonβ’
-
yarnd @prologic (me and others)-
jenny @movq-
tt @lyse-
Timeline @darch / @eapl.me and others-
twtxt-el? -- @androsFull list of supported and widely used clients can be found at https://twtxt.dev/clients.html -- which I note a few above are _actually_ missing from this page haha π€£
-
yarnd @prologic (me and others)-
jenny @movq-
tt @lyse-
Timeline @darch / @eapl.me and others-
twtxt-el? -- @androsFull list of supported and widely used clients can be found at https://twtxt.dev/clients.html -- which I note a few above are _actually_ missing from this page haha π€£
@<url> then I have to do quick a bit of dancing to figure out how to render such mentions sanely π
π
@<url> then I have to do quick a bit of dancing to figure out how to render such mentions sanely π
π
@<url> form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>.
@<url> form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>.
Congratulations! You have been admitted into the Free Tier Program!
You were approved for early access to the Free Tier Program.
Your Free Tier starts on 2025-01-08 and will end on 2026-01-08.
During that year, you will be able to launch a Free Tier instance. You can only have 1 free instance running at a time. If you shut down the instance you can relaunch it up to twice per month.
Congratulations! You have been admitted into the Free Tier Program!
You were approved for early access to the Free Tier Program.
Your Free Tier starts on 2025-01-08 and will end on 2026-01-08.
During that year, you will be able to launch a Free Tier instance. You can only have 1 free instance running at a time. If you shut down the instance you can relaunch it up to twice per month.
$ orgalorg -u root -o au.proxy -o eu.proxy -o us.proxy -C apk --no-cache -U add consul
> Parallel SSH commands runner and file synchronization tool
Good for when you have to many a small cluster of similar/identical machines.
$ orgalorg -u root -o au.proxy -o eu.proxy -o us.proxy -C apk --no-cache -U add consul
> Parallel SSH commands runner and file synchronization tool
Good for when you have to many a small cluster of similar/identical machines.
For the love of all that is good; Please stop sending emails with links to 3rd-party link tracking services that are meant to go to your own fucking god-damn services in the first place!
For the love of god! π€¦ββοΈ\
OnlyDomains GUILTY π€¬
For the love of all that is good; Please stop sending emails with links to 3rd-party link tracking services that are meant to go to your own fucking god-damn services in the first place!
For the love of god! π€¦ββοΈ\
OnlyDomains GUILTY π€¬
For the love of all that is good; Please stop sending emails with links to 3rd-party link tracking services that are meant to go to your own fucking god-damn services in the first place!
For the love of god! π€¦ββοΈ\\
OnlyDomains GUILTY π€¬
- AWS Route 53
- CSC Global
- CentralNic Reseller (formerly RRPProxy)
- DNSOVERHTTPS
- Dzynadot
- easyname
- Gandi
- HEXONET
- hosting.de
- Internet.bs
- INWX
- Namecheap
- Name.com
- OpenSRS
- OVH
- Realtime Register
- AWS Route 53
- CSC Global
- CentralNic Reseller (formerly RRPProxy)
- DNSOVERHTTPS
- Dzynadot
- easyname
- Gandi
- HEXONET
- hosting.de
- Internet.bs
- INWX
- Namecheap
- Name.com
- OpenSRS
- OVH
- Realtime Register
> EdgeGuard is a self-hosted solution that combines secure tunneling, proxying, and automation to create your own private cloud. Utilizing Wireguard for VPN, Caddy for reverse proxying, and Coraza for web application firewall, EdgeGuard allows you to securely expose your home network services (such as Gitea, Poste.io, etc.) to the Internet. With seamless automation and on-demand TLS, EdgeGuard gives you the power to manage your own cloud-like environment with the control and privacy of self-hosting.
> EdgeGuard is a self-hosted solution that combines secure tunneling, proxying, and automation to create your own private cloud. Utilizing Wireguard for VPN, Caddy for reverse proxying, and Coraza for web application firewall, EdgeGuard allows you to securely expose your home network services (such as Gitea, Poste.io, etc.) to the Internet. With seamless automation and on-demand TLS, EdgeGuard gives you the power to manage your own cloud-like environment with the control and privacy of self-hosting.