- Sharing small posts
- Sharing links
- Sharing media
- Having long conversations
- Voting on topics, opinions or decisions
- RSVPing to virtual or physical events
yarnd does for Youtube/Spotify/whatever embedding. Plus anyone can participate, even if they don't really have a client that understand it, it's just text with some "syntax" afterall.
- Gin
- Echo
- Chi
yarnd UI/UX experience (_for those that use it_) and as "client" features (_not spec changes_). The two ideas are quite simple:- Voting -- a way to cast, collect a vote on a decision, topic or opinion.
- RSVP -- a way to "rsvp" to a virtual (_pr physical_) event.
Both would use "plain text" on top of the way we already use Twtxt today and clients would render an appropriate UI/UX._
https://github.com/The-Pocket/Tutorial-Codebase-Knowledge
https://github.com/The-Pocket/Tutorial-Codebase-Knowledge
https://whichyr.com/
https://whichyr.com/
https://third-bit.com/2025/04/18/a-dollar-a-minute/
# url in your feed to be https:// 😅
{
...
# Layer 4 Reverse Proxy
layer4 {
# Gopher
0.0.0.0:70 {
route {
proxy <internal_ip>:70
}
}
# IRC (TLS)
0.0.0.0:6697 {
route {
proxy <internal_ip>:6697
}
}
}
}
https://github.com/JustAman62/undercut-f1
Algo assim para seguir eleições era giro
Screenshot de um terminal bem colorido com tempos, estatísticas e mensagens de controlo de uma corrida de F1
https://github.com/PiLiDAR/PiLiDAR
https://github.com/PiLiDAR/PiLiDAR
https://www.thedailystar.net/tech-startup/news/google-building-ai-model-talk-dolphins-3875626
https://www.thedailystar.net/tech-startup/news/google-building-ai-model-talk-dolphins-3875626
http:// only and to keep hashes from breaking i added # url = http://... and now we are stock with it due to the curret specs.
http:// only and to keep hashes from breaking i added # url = http://... and now we are stock with it due to the curret specs.
http:// only and to keep hashes from breaking i added # url = http://... and now we are stock with it due to the curret specs.
http:// only and to keep hashes from breaking i added # url = http://... and now we are stock with it due to the curret specs.
https://bradmontague.substack.com/p/librarians-are-dangerous
https://bradmontague.substack.com/p/librarians-are-dangerous
/https://baldo.cat/media/photos/IMG_0154.jpeg) #catsoftwtxt
url is http:// but he actually hosts a https:// feed with redirects. so things get a bit weird 😢
MaxAgeDays configuration at the pod level, that now _some_ profiles are rather empty. This is only because well, they're a bit "inactive" so to speak 🗣️ Not sure what to do about this at the moment... Open to ideas? 💡
> My profile pic is AI modified to prevent deepfakes. I used local Stable Diffusion on my solar powered 7900XTX to average a few selfies.
That sounds like a fun thing to do. Do I have a chance of doing that on my old box from 2013 without a dedicated GPU? 😂
> My profile pic is AI modified to prevent deepfakes. I used local Stable Diffusion on my solar powered 7900XTX to average a few selfies.
That sounds like a fun thing to do. Do I have a chance of doing that on my old box from 2013 without a dedicated GPU? 😂
What the heck is going on in 86.jpg? An art installation, apparently, but, uh, I wouldn’t trust that. 😂
What the heck is going on in 86.jpg? An art installation, apparently, but, uh, I wouldn’t trust that. 😂
[Global]
Name = your.irc.server.com
Password = yourfancypassword
Listen = 0.0.0.0
Ports = 6667
AdminInfo1 = Well, me.
AdminInfo2 = Over here!
AdminEMail = forget.it@example.invalid
[Options]
Ident = no
PAM = no
[SSL]
CertFile = /etc/ssl/acme/your.irc.server.com.fullchain.pem
KeyFile = /etc/ssl/acme/private/your.irc.server.com.key
DHFile = /etc/ngircd/dhparam.pem
Ports = 6669
Start it and then you can connect on port 6667. (The SSL cert/key must be managed by an external tool, probably something like certbot or acme-client.)
I’m assuming OpenBSD here. Haven’t tried it on Linux lately, let alone Docker. 😅=
[Global]
Name = your.irc.server.com
Password = yourfancypassword
Listen = 0.0.0.0
Ports = 6667
AdminInfo1 = Well, me.
AdminInfo2 = Over here!
AdminEMail = forget.it@example.invalid
[Options]
Ident = no
PAM = no
[SSL]
CertFile = /etc/ssl/acme/your.irc.server.com.fullchain.pem
KeyFile = /etc/ssl/acme/private/your.irc.server.com.key
DHFile = /etc/ngircd/dhparam.pem
Ports = 6669
Start it and then you can connect on port 6667. (The SSL cert/key must be managed by an external tool, probably something like certbot or acme-client.)
I’m assuming OpenBSD here. Haven’t tried it on Linux lately, let alone Docker. 😅=
Information published on the internet (or anywhere, for that matter) was never guaranteed to be correct. But at least you had a “frame of reference”: “Ah, I read this information about Linux on a blog that usually posts about Windows, so this one single Linux post might not necessarily be correct.” That is completely lost with LLMs. It’s literally all mushed together. 🤷
Information published on the internet (or anywhere, for that matter) was never guaranteed to be correct. But at least you had a “frame of reference”: “Ah, I read this information about Linux on a blog that usually posts about Windows, so this one single Linux post might not necessarily be correct.” That is completely lost with LLMs. It’s literally all mushed together. 🤷