| 23 Mar 2025 |
 @idabzo:matrix.org | I can do it for future postings | 15:50:03 |
 djacu | Do platforms besides bluesky support this? It's a really nice feature | 16:52:55 |
 Tristan Ross | In reply to @djacu:matrix.org
Do platforms besides bluesky support this? It's a really nice feature Twitter has alt, I can check Mastodon. | 17:02:56 |
| Tristan Ross | Ok, it looks like Mastodon does. | 17:03:37 |
|  connor (burnt/out) (UTC-8) changed their display name from connor (he/him) (UTC-8) to connor (he/him) (UTC-7). | 18:28:30 |
 isabel | twitter (x), bluesky and mastodon all support it but all with their own limitations | 22:22:42 |
| 25 Mar 2025 |
|  aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) changed their display name from aleksana (force me to bed after 18:00 UTC) to aleksana 🏳️⚧️ (force me to bed after 18:00 UTC). | 17:00:11 |
| 28 Mar 2025 |
 fricklerhandwerk | IdaBzo: I guess we should set up a banner or at least put something on the webpage for NixCon? https://discourse.nixos.org/t/nixcon-2025-5-7-september-in-rapperswil-jona-switzerland/62255 | 07:46:56 |
| fricklerhandwerk | It’s super important people can book travel and accommodation early to keep the cost of attendance down | 07:47:22 |
| @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 |
