Add a is_sfw configuration option in site.cfg
Add a make_sfw function which takes 3 arguments
swf : a bool if generating Hobby or Hacker Public Radio
swf_text : the Hobby related text
nswf_text: the Hacker related text
Modify the templates to generate the Hobby or Hacker related text
Add a is_sfw configuration option in site.cfg
Add a make_sfw function which takes 3 arguments
- swf : a bool if generating Hobby or Hacker Public Radio
- swf_text : the Hobby related text
- nswf_text: the Hacker related text
Modify the templates to generate the Hobby or Hacker related text
rho_n
self-assigned this 2025-09-11 17:00:43 +00:00
Where given site="hacker" would render "${site}{k1} Public Radio" as Hacker Public Radio.
Could you please not use swf or nsfw texts. This has nothing to do with safety, and gives the wrong impression.
I would prefer to have just a variable to a hash rather than the logic on each call.
```
{
"Hacker": {
"k1": "Hacker",
"k2": "Hackers",
"k3": "Hackers"
},
"Hobby": {
"k1": "Hobby",
"k2": "Hobbyist",
"k3": "Hobby"
}
}
```
Where given `site="hacker"` would render "`${site}{k1}` Public Radio" as Hacker Public Radio.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Add a is_sfw configuration option in site.cfg
Add a make_sfw function which takes 3 arguments
Modify the templates to generate the Hobby or Hacker related text
Could you please not use swf or nsfw texts. This has nothing to do with safety, and gives the wrong impression.
I would prefer to have just a variable to a hash rather than the logic on each call.
Where given
site="hacker"would render "${site}{k1}Public Radio" as Hacker Public Radio.