| 28 Mar 2025 |
 @idabzo:matrix.org | My initial plan was to:
-publish on social media (I'm doing it right now).
-post an announcement here: https://nixos.org/blog/
-refine the copy here: https://nixos.org/community/teams/nixcon/ (focusing more on community impact and the rich history of previous editions).
-update the NixCon section: https://nixos.org/community/
-banners are a great idea! In general, for our webpage, avocadoom is working super hard toward implementing this feature | 07:58:17 |
| @idabzo:matrix.org | BTW, having in mind that we're thinking about bringing our newsletter back to life, I think it wouldn't be a bad idea to create a dedicated issue for NixCon—to take advantage of the tiny detail that this year we're celebrating 10 years of NixCon (if I read it correctly, the initiative started in 2015) | 08:02:26 |
| 29 Mar 2025 |
 hexa | what would it take to migrate away from netlify for pages? | 01:00:22 |
| hexa | given that we don't use it to build anything anyhow and it seems like a glorified webhoster | 01:00:47 |
| hexa | * given that we don't use it to build anything anyhow and it seems like a glorified webhosting package | 01:00:50 |
| hexa | like could we do with github pages for example? | 01:04:12 |
| hexa | because they're less hostile about hosting things at the domain apex | 01:04:31 |
| hexa | * because they're less hostile about hosting things at the domain apex | 01:05:07 |
| hexa |
GitHub Pages sites have a soft bandwidth limit of 100 GB per month.
| 01:05:41 |
| hexa | we exceed that I think | 01:05:52 |
| hexa | 
Download image.png | 01:06:34 |
 avocadoom | I think the most important points for us are staging deployments and declarative redirects | 02:23:38 |
| avocadoom | If GitHub pages is sufficient for that I'd be happy to migrate there | 02:24:14 |
| avocadoom | Or some other offering | 02:24:28 |
| hexa | I'm bloody clueless, who offers what in that terrain tbh | 02:37:52 |
 fricklerhandwerk | In reply to @hexa:lossy.network
what would it take to migrate away from netlify for pages? Yes please let’s do this | 15:04:21 |
| fricklerhandwerk | In reply to @avocadoom:avocadoom.de
I think the most important points for us are staging deployments and declarative redirects We can convert those to e.g. Caddy redirects at build time | 15:05:15 |
| fricklerhandwerk | Anything that speaks against hosting our web content on our own infra? | 15:06:12 |
| hexa | Lack of a global CDN | 16:01:58 |
| hexa | Beyond that a 5 EUR hetzner VM would do | 16:02:17 |
| hexa | * Lack of a global CDN (if that is a requirement) | 16:02:44 |
| fricklerhandwerk | In reply to @hexa:lossy.network
Lack of a global CDN (if that is a requirement) Is it a requirement? What are those numbers even? Surely we aren’t serving gigabytes of manuals | 18:09:55 |
| fricklerhandwerk | In reply to @hexa:lossy.network
Lack of a global CDN (if that is a requirement) * Is it a requirement? What are those numbers even? Surely we aren’t serving gigabytes of manuals per day | 18:10:16 |
| fricklerhandwerk | (And even if we were, finishing the split being a slightly clever with etags would probably avoid most of the problem) | 18:11:22 |
| fricklerhandwerk | * (And even if we were, finishing the page split and being slightly clever with etags would probably avoid most of the problem) | 18:11:42 |
| hexa | the question is more about the global part and less about the bandwidth | 19:20:07 |
| 1 Apr 2025 |
|  Adam Neverwas joined the room. | 22:58:02 |
| Adam Neverwas set a profile picture. | 23:15:42 |
| 5 Apr 2025 |
|  @tinybronca:sibnsk.net removed their display name underpantsgnome. | 15:53:19 |
| @tinybronca:sibnsk.net left the room. | 15:56:56 |
