{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreih6dgo5itmpa6msfgouzxcbrixr73s5e72kqhge67obmdxhywj5cy",
    "uri": "at://did:plc:26wbisnofuprnxip3e62v5t2/app.bsky.feed.post/3mnzoyxyam5b2"
  },
  "path": "/t/support-to-more-new-sim-cards/2621#post_2",
  "publishedAt": "2026-06-11T11:57:51.000Z",
  "site": "https://discourse.osmocom.org",
  "textContent": "> What is the barrier for supporting new SIM cards?\n\nPrimarily someone writing the code and continuously / actively maintaining the code.\n\nAFAICT (and of course I’m biased), sysmocom is the only card vendor that has ever understood the value of open source tooling for SIM/USIM/ISIM/UICC cards. 99% of the pySim development and ongoing maintenance, documentation, etc. has been funded by sysmocom. And that despite the fact that 95% of said functionality is just generic, vendor-independent code implementing ETSI, 3GPP, GSMA, GlobalPlatform and other specifications.\n\nsysmocom is doing this out of the strong belief in open source software, and also in the belief that many users will recognize this enormous investment in open source SIM card tooling and buy our products to continue allowing us to cross-subsidize this development from revenue generated by card sales.\n\nSo _at the absolute very least_ I would expect that any other vendor caring about pySim support would at least actively submit and maintain code related to their cards, plus ideally also shoulder part of the burden of maintaining and further improving pySim in general.",
  "title": "Support to more/new SIM cards"
}