Paul_IPv6 on Nostr: npub1anhwl…hlz4h npub172qka…6lhd7 npub1fzpdy…udkks npub10kafx…fgfg4 the other ...
npub1anhwllp9m90m6rdswr9md3wlgh4fguj8wg0whektmjxltr8sr0ksfhlz4h (npub1anh…lz4h) npub172qka3k2t2m68q585femsef2p2f3x7d6czwvcz9377qem3ngvzqq56lhd7 (npub172q…lhd7) npub1fzpdyat9hwdtr5tlsg6tmwt82t5menqmccx30t7786p3exewp66q6udkks (npub1fzp…dkks) npub10kafxgmc528dkcy7cy855kyld042j6hlka4jyeutqgf4pu7zvl4qzfgfg4 (npub10ka…gfg4)
the other place OSS succeeds, other than devs as users, is infrastructure. postfix/sendmail, bind/knot/unbound, kea/dhcp, bird, etc.
there, the users are experienced admins who don't mind (much) mucking with complicated config languages.
OSS doesn't do as well with consumers, enterprise users, etc. because the support and feedback model tends to be the least funded/staffed part of an OSS project.
the other place OSS succeeds, other than devs as users, is infrastructure. postfix/sendmail, bind/knot/unbound, kea/dhcp, bird, etc.
there, the users are experienced admins who don't mind (much) mucking with complicated config languages.
OSS doesn't do as well with consumers, enterprise users, etc. because the support and feedback model tends to be the least funded/staffed part of an OSS project.