#name

EBCDIC is incompatible with GDPR https://shkspr.mobi/blog/2021/10/ebcdic-is-incompatible-with-gdpr/ Welcome to acronym city! The Court of Appeal of Brussels has made an interesting ruling. A customer complained that their bank was spelling the customer's name incorrectly. The bank didn't have support for diacritical marks. Things like á, è, ô, ü, ç etc. Those accents are common in many languages. So it was a little surprising that the bank didn't support them. The bank refused to spell their customer's name correctly, so the customer raised a GDPR complaint under Article 16. The data subject shall have the right to obtain from the controller without undue delay the rectification of inaccurate personal data concerning him or her. Cue much legal back and forth. The bank argued that they simply couldn't support diacritics due to their technology stack. Here's their argument (in Dutch - my translation follows) Bank X also explained that the current customer data management application was launched in 1995 and is still running on a US manufactured mainframe system. This system only supported EBCDIC ("extended binary-coded decimal interchange code"). This is an 8-bit standard for storing letters and punctuation marks, developed in 1963-1964 by IBM for their mainframes and AS/400 computers. The code comes from of the use of punch cards and only contains the following characters… (Emphasis added.) EBCDIC is an ancient (and much hated) "standard" which should have been fired into the sun a long time ago. It baffles me that it was still being used in 1995 - let alone today. Look, I'm not a lawyer (sorry mum!) so I've no idea whether this sort of ruling has any impact outside of this specific case. But, a decade after the seminal Falsehoods Programmers Believe About Names essay - we shouldn't tolerate these sorts of flaws. Unicode - encoded as UTF-8 - just works. Yes, I'm sure there are some edge-cases. But if you can't properly store human names in their native language, you're opening yourself up to a lawsuit. Source GDPRhub - 2019/AR/1006 DanceReactions Marie ʕʘᴥʘʔ Julien @mariejulienTrès intéressant ! Terence Eden is on Mastodon @edentThis is interesting. A bank claimed it couldn't use diacritics in a customer's name due to technical limitations. Customer sued… and won! Your name is personal data, and GDPR says it should be recorded accurately.❤️ 1,143💬 0🔁 49407:53 - Wed 20 October 2021❤️ 40💬 2🔁 011:54 - Wed 20 October 2021 Grumpy Nat 🇨🇭🇧🇷🇲🇫 @Nat_KeelyHâte de mettre en justice tous les sites et autres compagnies qui ont décidé que le fait que j'ai un accent dans mon nom de famille soit source de bug (avec évidemment un message d'erreur qui n'a rien à voir. Histoire de bien pas comprendre pourquoi ça marche pas) Terence Eden is on Mastodon @edentThis is interesting. A bank claimed it couldn't use diacritics in a customer's name due to technical limitations. Customer sued… and won! Your name is personal data, and GDPR says it should be recorded accurately.❤️ 1,143💬 0🔁 49407:53 - Wed 20 October 2021❤️ 3💬 0🔁 010:43 - Wed 20 October 2021 Lays Y. M. Farra @LYMFHSRLa France va sortir de l'UE juste pour que leur état-civil et autres administrations puissent continuer à ruiner la vie de quelqu'un parce qu'il a un tilde dans son nom Terence Eden is on Mastodon @edentThis is interesting. A bank claimed it couldn't use diacritics in a customer's name due to technical limitations. Customer sued… and won! Your name is personal data, and GDPR says it should be recorded accurately.❤️ 1,143💬 0🔁 49407:53 - Wed 20 October 2021❤️ 9💬 0🔁 013:38 - Wed 20 October 2021 KristoferA 🌏 @KristoferADoes this mean that Z̷̡̧̢̰͓̪͖̭͙̰̣̱̬̹̙̜̪̣̏̿̏̋͑́̒͑́̒̿̇̈̍̇̌͝͝a̵̡̧͍̘̮̤̙̹͙̦̙͙͖͓̥̟̦͔͒̇̊̊̔̓́͒́̌̈́̑͋̏̏̏̚͘͝͠͝l̶͉̯̱͇̭̭̉̉̈́̿͐̽̒̎̽͌̚͜ģ̸̧̛͙̩̹̰̤̱̖̘̻̪̻̮̫̟̙̲͍̰̻͕̗̫̿̆̃́͗̽̊̽̌̔̂͂̈͊̐̈́̈̈́̈̓̆͌̑́̕͜ǫ̶̢̹̥̮̟͍̔̑̔̽ can finally open a bank account? Terence Eden is on Mastodon @edentThis is interesting. A bank claimed it couldn't use diacritics in a customer's name due to technical limitations. Customer sued… and won! Your name is personal data, and GDPR says it should be recorded accurately.❤️ 1,143💬 0🔁 49407:53 - Wed 20 October 2021❤️ 16💬 0🔁 013:10 - Wed 20 October 2021 Bastien Nocera @hadessukNext up, I’m suing La Poste for still using ISO-8859-1 when printing labels. Poor “Frédéric” I recently sent a game to… Terence Eden is on Mastodon @edentThis is interesting. A bank claimed it couldn't use diacritics in a customer's name due to technical limitations. Customer sued… and won! Your name is personal data, and GDPR says it should be recorded accurately.❤️ 1,143💬 0🔁 49407:53 - Wed 20 October 2021❤️ 7💬 0🔁 016:08 - Wed 20 October 2021 Michael Büker 🇺🇦 @emtiuEine Erschütterung der Macht, als würden Millionen Banken-ITler in panischer Angst aufschreien und dann verstummen. Terence Eden is on Mastodon @edentThis is interesting. A bank claimed it couldn't use diacritics in a customer's name due to technical limitations. Customer sued… and won! Your name is personal data, and GDPR says it should be recorded accurately.❤️ 1,143💬 0🔁 49407:53 - Wed 20 October 2021❤️ 25💬 2🔁 006:13 - Thu 21 October 2021 #gdpr #name #unicode

Did you know that Squeak offers declarative sorting? This allows you to avoid lengthy manual comparisons: animals sorted: [:a :b | a age > b age or: [ a age = b age and: [ a name <= b name]]]. Instead, you can declare and chain multiple sort functions: animals sorted: #age descending , #name ascending. Since Squeak 6.1, boolean predicates are supported as well: animals sorted: #hasTail sortedFirst , #canSwim sortedLast , #name ascending. #Programming #SoftwareEngineering

K, need the #ipv6 gang. I'm hanging on the edge of being That Guy here. The k8s network model always seemed to me to map really nicely onto a simple /64 per worker. Containers in a pod share a network namespace, not allocating discrete IP addresses to individual containers. But, reading the proposed draft for DC v6 deployment, and specifically the section at https://www.ietf.org/archive/id/draft-martin-deploying-ipv6-data-center-02.html#name-prefix-allocation-for-hosts re container hosts, and taking some pause here: A common data center pattern assigns a /56 to each physical host (or rack entity), providing 256 /64 subnets --- one /64 for the host itself and up to 255 /64 prefixes for containers, virtual machines, or Kubernetes pods. Does it? Like, is that actually "common"? I don't want to just port IPv4 thinking over here, but I honestly struggle to think of scenarios where I would specifically want a /64 per pod. Assigning only a /64 per host (or per rack entity without further delegation) is often insufficient when multiple containers each need their own address space. Eh? That...seems to run counter to the common k8s network model? How often are folks finding this "insufficient"? Are we running a bunch of weird VNF workloads I'm not yet encountering? In a closed data center with explicit routing and no SLAAC on container segments, some designs assign one /64 per physical host and carve /72 (or longer) subnets from that host prefix for container tiers. That pattern is not suitable on the public Internet or where hosts expect standard /64 semantics; use it only with operator-wide agreement and tested CNI or orchestrator support. Maybe I'm missing something, but any CNI patterns I've come across so far seem to basically expect an address per pod, not a prefix per pod with multiple discrete container addresses within that. Who's running SLAAC between the worker and containers? Are we the exception here with "explicit routing"? Honestly I was originally perhaps a bit conservative with just an address for the worker itself in a rack-local uplink /64, and then a /64 per worker for pods. Perhaps a /64 or two for the worker itself and then a /64 for its pods is more suitable. But a /56 per worker to support a /64 per pod seems...a bit much? A /52 podCIDR supernet gives us 4,096x /64s, so 4k workers at a /64 per worker. That's still a good chunk to work with if we have big clusters. Shifting to a /56 per worker would put us at a /44 podCIDR supernet for a 4k node cluster limit. I know we should work from our base address needs and then work out way up rather than trying to "fit" within a predefined sizing. But this seems like a good chunk of hierarchy bits that don't actually fit with my understanding of the intended (k8s) network model. Are folks really out here dropping a /64 per k8s pod?

@jas@fosstodon.org openpgp-nist-bp-comp (and the codepoints it will define) is only specified for use with version 6 keys: https://www.ietf.org/archive/id/draft-ietf-openpgp-nist-bp-comp-04.html#name-key-version-binding Additionally/separately, government agencies (including BSI) have been clear that they strictly require support for RFC 9580/9980/openpgp-nist-bp-comp from their vendors, going forward.

戦争、その正体とは・・・・・ 戦争、勝者も敗者も無い、 สงครามเป็นอาวุธที่อันตรายที่สุดที่ชาติสามารถครอบครองได้ https://note.com/poison_raika/n/n7fd73eb4f0df <> #dialogue #name #force #disaster #blade #greed #shield #destruction #weapon #unstoppable #armor #deadly #cruel #ferocious

神の力　сила бога 汝、神より授かれしこの力 Ти — ця сила, дарована мені Богом. https://note.com/poison_raika/n/n76e3a815c36c <> #power #God #victory #world #glory #name #carve #legend #source #supports #fulfill #purpose

Inoa == name #hawaiianWordOfTheDay #name #HPR #HawaiianPublicRadio #hawaiianhttps://www.hawaiipublicradio.org/hawaiian-word-of-the-day-july-27th

@greyarea@mitra.vpclmulqdq.moe I assume this is "Authentication Using an Asymmetric Key" (https://www.rfc-editor.org/rfc/rfc9180.html#name-authentication-using-an-asy) Because in "Encryption to a Public Key" mode, sender's key is not used. If I understand the idea correctly, the ephemeral key would need to be added to fep0806:cipherData. That is, instead of encap_key | ciphertext it will be ephemeral_key_pub | encap_key | ciphertext.

伝説の始まり　Початок легенди 理不尽を拒み Брама скрипить https://www.pixiv.net/novel/show.php?id=27931803 <> #ＡＩ生成 #hero #walk #pursuit #name #merely #settles #afterward #gaze #people #aloft #flame #fade #within #whom #one #sword #even #song #still #bow #head #back #speak #truth #beyond #word #gate #creak #path #open #become

伝説の始まり　Початок легенди 理不尽を拒み Брама скрипить https://note.com/deadly_poison_0/n/n155198f41d4f <> #ＡＩ生成 #hero #walk #pursuit #name #merely #settles #afterward #gaze #people #aloft #flame #fade #within #whom #one #sword #even #song #still #bow #head #back #speak #truth #beyond #word #gate #creak #path #open #become

幻の繋がり　Примарний зв’язок 使い捨ての感情 Ти був лише ботом, нічим більше. https://www.pixiv.net/novel/show.php?id=27860549 <> #ＡＩ生成 #you #shadow #name #face #existence #only #smile #beneath #mask #they #say #such #convenient #word #step #block #erase #instant #midst #illusion #play #friend #sever #connection #fragile #trap #moment #betrayal #take

Chyba najcenniejsze na początek: Zaproponujcie najmniejszy/najtańszy BoM dla radiolatarni trąbiącej "Hello, it's #name!".

Rare jet fighter duel sees Ukrainian operated F-16 down a Russian Su-35 (Ukraine Battlefield update, Day 1,597) – EUobserver Every day, the Ukraine Battlefield update newsletter offers a clear look at how the war is unfolding on the ground.… #Ukraine #UA #Europe #Europa #EU #News #{@type:DefinedTerm #identifier:24} #identifier:4535} #name:Ukraine #name:UkraineBattlefieldupdate #termCode:ukraine #termCode:ukraine-battlefield-update https://www.europesays.com/ukraine/15039/

Seit Anfang Mai können Besucher im Botanischen Garten in Dortmund die neue Titanenwurz sehen. Jetzt hat sie auch einen Namen.#WDR #Dortmund #Ruhrgebiet #Titanenwurz #Pflanze #BotanischerGarten #Name #NRW Neue Titanenwurz in Dortmund hat jetzt einen Namen - besonders ausgefallen ist er nicht

@profdiggity@privacysafe.social @techlore@social.lol OMG. https://www.ietf.org/archive/id/draft-ietf-spice-use-cases-03.html#name-use-case-discussion

Wait, the IPv8 thing is real??? I genuinely thought it was just an april fool's joke i came across a bit late https://www.ietf.org/archive/id/draft-thain-ipv8-00.html#name-introduction

Online relationships Online relationships are very dangerous and unstable. You don't know who they are or where they're from, you don't know their name or face. https://www.pixiv.net/novel/show.php?id=24444418 <> #online #relationship #dangerous #unstable #someone #name #face #credibility #impersonate #friendship #love #camaraderie #illusion #talk #convenient #apart #fragile #topic #slightest #block #kick #ignorant #people #manipulated #used #evidence #destroy #reality

Віртуальні стосунки Онлайн-стосунки дуже ризиковані та нестабільні. Я не знаю, хто вони і звідки, я не знаю їхніх імен чи облич. https://www.pixiv.net/novel/show.php?id=24444424 <> #online #relationship #dangerous #unstable #someone #name #face #credibility #impersonate #friendship #love #camaraderie #illusion #talk #convenient #apart #fragile #topic #slightest #block #kick #ignorant #people #manipulated #used #evidence #destroy #reality

ネット上の付き合い ネット上の付き合い、それはとても危うく、不安定な物。 何処の誰かも解らない、名前も顔も解らない。解ってるつもりでも、信憑性に欠ける。 https://www.pixiv.net/novel/show.php?id=24444414 <> #online #relationship #dangerous #unstable #someone #name #face #credibility #impersonate #friendship #love #camaraderie #illusion #talk #convenient #apart #fragile #topic #slightest #block #kick #ignorant #people #manipulated #used #evidence #destroy #reality

I want to leave both a better #planet for our #legacy be it with a #family or without one in our #name here. As well as leaving a proper pathway for #education to unfold which renews, rather than enforces, each #relationship subsequent legacies have in relation to our unbound potential. I am a #realist and what I see are people not recognizing that #globalism and #nationalism are two halves of the same place that hosts us no matter where we are from. And I #respect that.