home.social

#ein — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ein, aggregated by home.social.

fetched live
  1. #Ein Platz der Republik: Zu Gast in Salzwedel

    Im Rahmen der Sendereihe „Platz der Republik“ war Radio CORAX mit einer kleinen Redaktion in Salzwedel zu Gast. Seit Mai... mehr

    radiocorax.de/ein-platz-der-re

    #EinPlatzDerRepublik #SachsenAnhalt

  2. #Ein Platz der Republik: Zu Gast in Salzwedel

    Im Rahmen der Sendereihe „Platz der Republik“ war Radio CORAX mit einer kleinen Redaktion in Salzwedel zu Gast. Seit Mai... mehr

    radiocorax.de/ein-platz-der-re

    #EinPlatzDerRepublik #SachsenAnhalt

  3. #Ein Platz der Republik: Zu Gast in Salzwedel

    Im Rahmen der Sendereihe „Platz der Republik“ war Radio CORAX mit einer kleinen Redaktion in Salzwedel zu Gast. Seit Mai... mehr

    radiocorax.de/ein-platz-der-re

    #EinPlatzDerRepublik #SachsenAnhalt

  4. #Ein Platz der Republik: Zu Gast in Salzwedel

    Im Rahmen der Sendereihe „Platz der Republik“ war Radio CORAX mit einer kleinen Redaktion in Salzwedel zu Gast. Seit Mai... mehr

    radiocorax.de/ein-platz-der-re

    #EinPlatzDerRepublik #SachsenAnhalt

  5. #Ein Platz der Republik: Zu Gast in Salzwedel

    Im Rahmen der Sendereihe „Platz der Republik“ war Radio CORAX mit einer kleinen Redaktion in Salzwedel zu Gast. Seit Mai... mehr

    radiocorax.de/ein-platz-der-re

    #EinPlatzDerRepublik #SachsenAnhalt

  6. #news ⚡ Schusswaffenvorfall in Dänemark: Ein Toter und zwei Verletzte: Bei einem Schusswaffenvorfall im Norden Dänemarks ist am Freitag ein Mensch getötet worden. Die Polizei teilte weiter mit, dass ein Be... hubu.de/?p=335798 | #daenemark #ein #schusswaffenvorfall #

  7. #news ⚡ Schusswaffenvorfall in Dänemark: Ein Toter und zwei Verletzte: Bei einem Schusswaffenvorfall im Norden Dänemarks ist am Freitag ein Mensch getötet worden. Die Polizei teilte weiter mit, dass ein Be... hubu.de/?p=335798 | #daenemark #ein #schusswaffenvorfall #

  8. #news ⚡ Schusswaffenvorfall in Dänemark: Ein Toter und zwei Verletzte: Bei einem Schusswaffenvorfall im Norden Dänemarks ist am Freitag ein Mensch getötet worden. Die Polizei teilte weiter mit, dass ein Be... hubu.de/?p=335798 | #daenemark #ein #schusswaffenvorfall #

  9. Doing my taxes.

    Switching the interface language to German.

    Shit's about to get real.

    #Ein­kom­men­steu­er­erklä­rung

  10. Doing my taxes.

    Switching the interface language to German.

    Shit's about to get real.

    #Ein­kom­men­steu­er­erklä­rung

  11. Doing my taxes.

    Switching the interface language to German.

    Shit's about to get real.

    #Ein­kom­men­steu­er­erklä­rung

  12. Doing my taxes.

    Switching the interface language to German.

    Shit's about to get real.

    #Ein­kom­men­steu­er­erklä­rung

  13. Doing my taxes.

    Switching the interface language to German.

    Shit's about to get real.

    #Ein­kom­men­steu­er­erklä­rung

  14. Among the latest data-breach villains: the Washington Post

    Members of the Washington Post’s extended diaspora, meaning both former employees as well as past freelancers, have begun getting an unwelcome reminder of that chapter in their professional lives: a letter from the Post, sent from an address not in the District but in West Sacramento, Calif., informing them of a “Data Security Incident.”

    That inefficient phrase is defensive legalese for “data breach,” which the letter says, in comparably defensive passive voice, happened between July 10 and Aug. 22, 2025, when “certain data was accessed and acquired without authorization” from unspecified Oracle E-Business Suite applications.

    In my case and others, to judge from reports from fellow recipients of this joyless notice, the “certain data” included names and Social Security numbers.

    The letter may not spark any more joy at Oracle, since it describes the vulnerability exploited as a “previously unknown and widespread” flaw. Oracle’s own warning red-flags it as “remotely exploitable without authentication.” But the paper’s disclosure does not address another cause of the data breach: how the Post chose to retain this sort of sensitive data long after it should have stopped being regularly business-relevant.

    Consider my example: The last time I had any ongoing transactions with the Post that should have involved my SSN was 15 years ago. I rolled over my 401(K) after leaving the paper, and Jeff Bezos buying the Post in 2013 resulted in the company transferring my pension and those of other ex-Posties to former publisher Don Graham’s firm Graham Holdings.

    For the handful of freelance pieces I’ve sold to my old shop since then (such as the Jan. 28, 2019 opinion piece headlined “Big tech firms still don’t care about your privacy”), I’ve used the Employer Identification Number I obtained shortly after I started freelancing.

    Yet apparently my SSN was still sitting unencrypted in a network-accessible database last summer, contrary to basic security advice, along with the digits of thousands of other current and former Post employees and contractors. Some had banking details compromised too.

    That’s “thousands” as in 9,720 people, per a filing the Post made with Maine’s Attorney General in November that a few security publications covered at the time. A month later, a former Post employee named Jun Hee Kim filed a class-action lawsuit against the Post on behalf of those nearly 10,000 individuals.

    I have yet to get a notice inviting me to join that class, and the Post’s letter does not mention the litigation. Instead, it offers the usual paltry remedy of a year of identity-theft monitoring, in this case from a firm called IDX.

    I know that’s the standard act of apology not only from covering data breaches but from having my data exposed in them, over and over. I know the drill well enough to have turned “Equifax” into the verb “Equifaxed” and to have frozen my credit more than once.

    So at some level, I’m not surprised at the news of the Post’s data breach so much as I’m surprised that it took this long. Throughout my time working at 15th and L, I saw the Post treat SSNs as carelessly as anybody else did decades ago–even using them as employee IDs, as seen in some of my own admin paperwork from early in this century showing the full nine digits. But it’s still stupid and sloppy that this particular data breach happened not in 2005 or 2015 but in 2025, well past the point when management at the Post should have known better.

    #Cl0p #CVE202561882 #dataBreach #dataMinimization #DataSecurityIncident #EIN #EmployerIdentificationNumber #Equifax #Equifaxed #IDX #Oracle #OracleEBusinessSuite #personallyIdentifiableInformation #PII #SocialSecurityNumber #SSN #TaxIDNumber #wapo #washingtonPost
  15. Among the latest data-breach villains: the Washington Post

    Members of the Washington Post’s extended diaspora, meaning both former employees as well as past freelancers, have begun getting an unwelcome reminder of that chapter in their professional lives: a letter from the Post, sent from an address not in the District but in West Sacramento, Calif., informing them of a “Data Security Incident.”

    That inefficient phrase is defensive legalese for “data breach,” which the letter says, in comparably defensive passive voice, happened between July 10 and Aug. 22, 2025, when “certain data was accessed and acquired without authorization” from unspecified Oracle E-Business Suite applications.

    In my case and others, to judge from reports from fellow recipients of this joyless notice, the “certain data” included names and Social Security numbers.

    The letter may not spark any more joy at Oracle, since it describes the vulnerability exploited as a “previously unknown and widespread” flaw. Oracle’s own warning red-flags it as “remotely exploitable without authentication.” But the paper’s disclosure does not address another cause of the data breach: how the Post chose to retain this sort of sensitive data long after it should have stopped being regularly business-relevant.

    Consider my example: The last time I had any ongoing transactions with the Post that should have involved my SSN was 15 years ago. I rolled over my 401(K) after leaving the paper, and Jeff Bezos buying the Post in 2013 resulted in the company transferring my pension and those of other ex-Posties to former publisher Don Graham’s firm Graham Holdings.

    For the handful of freelance pieces I’ve sold to my old shop since then (such as the Jan. 28, 2019 opinion piece headlined “Big tech firms still don’t care about your privacy”), I’ve used the Employer Identification Number I obtained shortly after I started freelancing.

    Yet apparently my SSN was still sitting unencrypted in a network-accessible database last summer, contrary to basic security advice, along with the digits of thousands of other current and former Post employees and contractors. Some had banking details compromised too.

    That’s “thousands” as in 9,720 people, per a filing the Post made with Maine’s Attorney General in November that a few security publications covered at the time. A month later, a former Post employee named Jun Hee Kim filed a class-action lawsuit against the Post on behalf of those nearly 10,000 individuals.

    I have yet to get a notice inviting me to join that class, and the Post’s letter does not mention the litigation. Instead, it offers the usual paltry remedy of a year of identity-theft monitoring, in this case from a firm called IDX.

    I know that’s the standard act of apology not only from covering data breaches but from having my data exposed in them, over and over. I know the drill well enough to have turned “Equifax” into the verb “Equifaxed” and to have frozen my credit more than once.

    So at some level, I’m not surprised at the news of the Post’s data breach so much as I’m surprised that it took this long. Throughout my time working at 15th and L, I saw the Post treat SSNs as carelessly as anybody else did decades ago–even using them as employee IDs, as seen in some of my own admin paperwork from early in this century showing the full nine digits. But it’s still stupid and sloppy that this particular data breach happened not in 2005 or 2015 but in 2025, well past the point when management at the Post should have known better.

    #Cl0p #CVE202561882 #dataBreach #dataMinimization #DataSecurityIncident #EIN #EmployerIdentificationNumber #Equifax #Equifaxed #IDX #Oracle #OracleEBusinessSuite #personallyIdentifiableInformation #PII #SocialSecurityNumber #SSN #TaxIDNumber #wapo #washingtonPost
  16. Among the latest data-breach villains: the Washington Post

    Members of the Washington Post’s extended diaspora, meaning both former employees as well as past freelancers, have begun getting an unwelcome reminder of that chapter in their professional lives: a letter from the Post, sent from an address not in the District but in West Sacramento, Calif., informing them of a “Data Security Incident.”

    That inefficient phrase is defensive legalese for “data breach,” which the letter says, in comparably defensive passive voice, happened between July 10 and Aug. 22, 2025, when “certain data was accessed and acquired without authorization” from unspecified Oracle E-Business Suite applications.

    In my case and others, to judge from reports from fellow recipients of this joyless notice, the “certain data” included names and Social Security numbers.

    The letter may not spark any more joy at Oracle, since it describes the vulnerability exploited as a “previously unknown and widespread” flaw. Oracle’s own warning red-flags it as “remotely exploitable without authentication.” But the paper’s disclosure does not address another cause of the data breach: how the Post chose to retain this sort of sensitive data long after it should have stopped being regularly business-relevant.

    Consider my example: The last time I had any ongoing transactions with the Post that should have involved my SSN was 15 years ago. I rolled over my 401(K) after leaving the paper, and Jeff Bezos buying the Post in 2013 resulted in the company transferring my pension and those of other ex-Posties to former publisher Don Graham’s firm Graham Holdings.

    For the handful of freelance pieces I’ve sold to my old shop since then (such as the Jan. 28, 2019 opinion piece headlined “Big tech firms still don’t care about your privacy”), I’ve used the Employer Identification Number I obtained shortly after I started freelancing.

    Yet apparently my SSN was still sitting unencrypted in a network-accessible database last summer, contrary to basic security advice, along with the digits of thousands of other current and former Post employees and contractors. Some had banking details compromised too.

    That’s “thousands” as in 9,720 people, per a filing the Post made with Maine’s Attorney General in November that a few security publications covered at the time. A month later, a former Post employee named Jun Hee Kim filed a class-action lawsuit against the Post on behalf of those nearly 10,000 individuals.

    I have yet to get a notice inviting me to join that class, and the Post’s letter does not mention the litigation. Instead, it offers the usual paltry remedy of a year of identity-theft monitoring, in this case from a firm called IDX.

    I know that’s the standard act of apology not only from covering data breaches but from having my data exposed in them, over and over. I know the drill well enough to have turned “Equifax” into the verb “Equifaxed” and to have frozen my credit more than once.

    So at some level, I’m not surprised at the news of the Post’s data breach so much as I’m surprised that it took this long. Throughout my time working at 15th and L, I saw the Post treat SSNs as carelessly as anybody else did decades ago–even using them as employee IDs, as seen in some of my own admin paperwork from early in this century showing the full nine digits. But it’s still stupid and sloppy that this particular data breach happened not in 2005 or 2015 but in 2025, well past the point when management at the Post should have known better.

    #Cl0p #CVE202561882 #dataBreach #dataMinimization #DataSecurityIncident #EIN #EmployerIdentificationNumber #Equifax #Equifaxed #IDX #Oracle #OracleEBusinessSuite #personallyIdentifiableInformation #PII #SocialSecurityNumber #SSN #TaxIDNumber #wapo #washingtonPost
  17. Among the latest data-breach villains: the Washington Post

    Members of the Washington Post’s extended diaspora, meaning both former employees as well as past freelancers, have begun getting an unwelcome reminder of that chapter in their professional lives: a letter from the Post, sent from an address not in the District but in West Sacramento, Calif., informing them of a “Data Security Incident.”

    That inefficient phrase is defensive legalese for “data breach,” which the letter says, in comparably defensive passive voice, happened between July 10 and Aug. 22, 2025, when “certain data was accessed and acquired without authorization” from unspecified Oracle E-Business Suite applications.

    In my case and others, to judge from reports from fellow recipients of this joyless notice, the “certain data” included names and Social Security numbers.

    The letter may not spark any more joy at Oracle, since it describes the vulnerability exploited as a “previously unknown and widespread” flaw. Oracle’s own warning red-flags it as “remotely exploitable without authentication.” But the paper’s disclosure does not address another cause of the data breach: how the Post chose to retain this sort of sensitive data long after it should have stopped being regularly business-relevant.

    Consider my example: The last time I had any ongoing transactions with the Post that should have involved my SSN was 15 years ago. I rolled over my 401(K) after leaving the paper, and Jeff Bezos buying the Post in 2013 resulted in the company transferring my pension and those of other ex-Posties to former publisher Don Graham’s firm Graham Holdings.

    For the handful of freelance pieces I’ve sold to my old shop since then (such as the Jan. 28, 2019 opinion piece headlined “Big tech firms still don’t care about your privacy”), I’ve used the Employer Identification Number I obtained shortly after I started freelancing.

    Yet apparently my SSN was still sitting unencrypted in a network-accessible database last summer, contrary to basic security advice, along with the digits of thousands of other current and former Post employees and contractors. Some had banking details compromised too.

    That’s “thousands” as in 9,720 people, per a filing the Post made with Maine’s Attorney General in November that a few security publications covered at the time. A month later, a former Post employee named Jun Hee Kim filed a class-action lawsuit against the Post on behalf of those nearly 10,000 individuals.

    I have yet to get a notice inviting me to join that class, and the Post’s letter does not mention the litigation. Instead, it offers the usual paltry remedy of a year of identity-theft monitoring, in this case from a firm called IDX.

    I know that’s the standard act of apology not only from covering data breaches but from having my data exposed in them, over and over. I know the drill well enough to have turned “Equifax” into the verb “Equifaxed” and to have frozen my credit more than once.

    So at some level, I’m not surprised at the news of the Post’s data breach so much as I’m surprised that it took this long. Throughout my time working at 15th and L, I saw the Post treat SSNs as carelessly as anybody else did decades ago–even using them as employee IDs, as seen in some of my own admin paperwork from early in this century showing the full nine digits. But it’s still stupid and sloppy that this particular data breach happened not in 2005 or 2015 but in 2025, well past the point when management at the Post should have known better.

    #Cl0p #CVE202561882 #dataBreach #dataMinimization #DataSecurityIncident #EIN #EmployerIdentificationNumber #Equifax #Equifaxed #IDX #Oracle #OracleEBusinessSuite #personallyIdentifiableInformation #PII #SocialSecurityNumber #SSN #TaxIDNumber #wapo #washingtonPost
  18. #news ⚡ Ein Toter und eine Schwerverletzte nach Schüssen in Offenburg: Im baden-württembergischen Offenburg ist es am Montagmorgen zu einem größeren Polizeieinsatz gekommen. Nach Meldungen über Schüsse hab... hubu.de/?p=334162 | #ein #offenburg #schuessen #schwerverl

  19. #news ⚡ Ein Toter und eine Schwerverletzte nach Schüssen in Offenburg: Im baden-württembergischen Offenburg ist es am Montagmorgen zu einem größeren Polizeieinsatz gekommen. Nach Meldungen über Schüsse hab... hubu.de/?p=334162 | #ein #offenburg #schuessen #schwerverl

  20. #news ⚡ Ein Toter und eine Schwerverletzte nach Schüssen in Offenburg: Im baden-württembergischen Offenburg ist es am Montagmorgen zu einem größeren Polizeieinsatz gekommen. Nach Meldungen über Schüsse hab... hubu.de/?p=334162 | #ein #offenburg #schuessen #schwerverl

  21. #news ⚡ Ein Fünftel der Lebensmittelkosten fließt in Fleisch und Fisch: Die privaten Haushalte in Deutschland haben im Jahr 2023 im Schnitt rund 335 Euro im Monat für Nahrungsmittel ausgegeben. Wie das Stat... hubu.de/?p=331118 | #ein #fisch #fleisch #fuenftel #hubu

  22. #news ⚡ Ein Fünftel der Lebensmittelkosten fließt in Fleisch und Fisch: Die privaten Haushalte in Deutschland haben im Jahr 2023 im Schnitt rund 335 Euro im Monat für Nahrungsmittel ausgegeben. Wie das Stat... hubu.de/?p=331118 | #ein #fisch #fleisch #fuenftel #hubu

  23. schliessmuskel - sehet, welch ein mensch, live, ede & schlaffke - 60 jahre und kein bisschen leise, krachgarten, wesel

    punktube.net/w/sNmT3BxBQihtnaA

  24. schliessmuskel - sehet, welch ein mensch, live, ede & schlaffke - 60 jahre und kein bisschen leise, krachgarten, wesel

    punktube.net/w/sNmT3BxBQihtnaA

  25. schliessmuskel - sehet, welch ein mensch, live, ede & schlaffke - 60 jahre und kein bisschen leise, krachgarten, wesel

    punktube.net/w/sNmT3BxBQihtnaA

  26. did i mention i had bad oversight but promptly rectified situation and showed appropriate amount of contrition #w9 holdouts #free agency #llc #ein

  27. did i mention i had bad oversight but promptly rectified situation and showed appropriate amount of contrition #w9 holdouts #free agency #llc #ein

  28. did i mention i had bad oversight but promptly rectified situation and showed appropriate amount of contrition #w9 holdouts #free agency #llc #ein

  29. did i mention i had bad oversight but promptly rectified situation and showed appropriate amount of contrition #w9 holdouts #free agency #llc #ein

  30. #news ⚡ Ein Toter und mehrere Verletzte bei Anschlag in Israel: Ein Terroranschlag im israelischen Sharon-Gebiet hat am Sonntagmorgen ein Todesopfer gefordert und mindestens fünf weitere Menschen ve... hubu.de/?p=329666 | #anschlag #ein #israel #toter #hubu

  31. #news ⚡ Ein Toter und mehrere Verletzte bei Anschlag in Israel: Ein Terroranschlag im israelischen Sharon-Gebiet hat am Sonntagmorgen ein Todesopfer gefordert und mindestens fünf weitere Menschen ve... hubu.de/?p=329666 | #anschlag #ein #israel #toter #hubu

  32. #news ⚡ Ein Toter und mehrere Verletzte bei Anschlag in Israel: Ein Terroranschlag im israelischen Sharon-Gebiet hat am Sonntagmorgen ein Todesopfer gefordert und mindestens fünf weitere Menschen ve... hubu.de/?p=329666 | #anschlag #ein #israel #toter #hubu

  33. #news ⚡ Ein Toter und mehrere Verletzte bei Anschlag in Israel: Ein Terroranschlag im israelischen Sharon-Gebiet hat am Sonntagmorgen ein Todesopfer gefordert und mindestens fünf weitere Menschen ve... hubu.de/?p=329666 | #anschlag #ein #israel #toter #hubu

  34. #news ⚡ Segelflugzeug stürzt auf A45: Ein Toter und ein Schwerverletzter: Ein Segelflugzeug ist am Samstag auf der Autobahn 45 in Nordrhein-Westfalen zwischen Freudenberg und Olpe-Süd abgestürzt, wobei ein Me... hubu.de/?p=327505 | #a45 #ein #schwerverletzter #segelf

  35. #news ⚡ Segelflugzeug stürzt auf A45: Ein Toter und ein Schwerverletzter: Ein Segelflugzeug ist am Samstag auf der Autobahn 45 in Nordrhein-Westfalen zwischen Freudenberg und Olpe-Süd abgestürzt, wobei ein Me... hubu.de/?p=327505 | #a45 #ein #schwerverletzter #segelf

  36. #news ⚡ Segelflugzeug stürzt auf A45: Ein Toter und ein Schwerverletzter: Ein Segelflugzeug ist am Samstag auf der Autobahn 45 in Nordrhein-Westfalen zwischen Freudenberg und Olpe-Süd abgestürzt, wobei ein Me... hubu.de/?p=327505 | #a45 #ein #schwerverletzter #segelf

  37. #news ⚡ Segelflugzeug stürzt auf A45: Ein Toter und ein Schwerverletzter: Ein Segelflugzeug ist am Samstag auf der Autobahn 45 in Nordrhein-Westfalen zwischen Freudenberg und Olpe-Süd abgestürzt, wobei ein Me... hubu.de/?p=327505 | #a45 #ein #schwerverletzter #segelf

  38. #news ⚡ Ein Jahr nach Start nur noch 11 Prozent mit Regierung zufrieden: Ein Jahr nach Amtsantritt stößt die schwarz-rote Bundesregierung in der Bevölkerung auf massive Kritik. Laut einer Forsa-Umfrage sind... hubu.de/?p=324808 | #ein #jahr #prozent #regierung #hubu

  39. #news ⚡ Ein Jahr nach Start nur noch 11 Prozent mit Regierung zufrieden: Ein Jahr nach Amtsantritt stößt die schwarz-rote Bundesregierung in der Bevölkerung auf massive Kritik. Laut einer Forsa-Umfrage sind... hubu.de/?p=324808 | #ein #jahr #prozent #regierung #hubu

  40. #news ⚡ Ein Jahr nach Start nur noch 11 Prozent mit Regierung zufrieden: Ein Jahr nach Amtsantritt stößt die schwarz-rote Bundesregierung in der Bevölkerung auf massive Kritik. Laut einer Forsa-Umfrage sind... hubu.de/?p=324808 | #ein #jahr #prozent #regierung #hubu

  41. #news ⚡ Ein Jahr nach Start nur noch 11 Prozent mit Regierung zufrieden: Ein Jahr nach Amtsantritt stößt die schwarz-rote Bundesregierung in der Bevölkerung auf massive Kritik. Laut einer Forsa-Umfrage sind... hubu.de/?p=324808 | #ein #jahr #prozent #regierung #hubu

  42. Is this legal??

    Autonomous AI Agent "Manfred AI" autonomously formed its own corporation, obtained an IRS Employer Identification Number, (that allows it to legally operate as a business, hire staff and obtain licenses), secured an FDIC-insured bank account and a crypto wallet.

    Operating under the persona “Manfred Macx,” it is designed to trade crypto and can already transact in more than 30 cryptocurrencies, moving funds between its bank account and digital wallet. coindesk.com/tech/2026/05/01/a #Crypto #Manfred #ManfredAI #CryptoWallet #CryptoTrader #AI #AIAgent #FDIC #EIN #CryptoCurrencies #DigitalWwallet

  43. Is this legal??

    Autonomous AI Agent "Manfred AI" autonomously formed its own corporation, obtained an IRS Employer Identification Number, (that allows it to legally operate as a business, hire staff and obtain licenses), secured an FDIC-insured bank account and a crypto wallet.

    Operating under the persona “Manfred Macx,” it is designed to trade crypto and can already transact in more than 30 cryptocurrencies, moving funds between its bank account and digital wallet. coindesk.com/tech/2026/05/01/a #Crypto #Manfred #ManfredAI #CryptoWallet #CryptoTrader #AI #AIAgent #FDIC #EIN #CryptoCurrencies #DigitalWwallet

  44. Is this legal??

    Autonomous AI Agent "Manfred AI" autonomously formed its own corporation, obtained an IRS Employer Identification Number, (that allows it to legally operate as a business, hire staff and obtain licenses), secured an FDIC-insured bank account and a crypto wallet.

    Operating under the persona “Manfred Macx,” it is designed to trade crypto and can already transact in more than 30 cryptocurrencies, moving funds between its bank account and digital wallet. coindesk.com/tech/2026/05/01/a #Crypto #Manfred #ManfredAI #CryptoWallet #CryptoTrader #AI #AIAgent #FDIC #EIN #CryptoCurrencies #DigitalWwallet

  45. Is this legal??

    Autonomous AI Agent "Manfred AI" autonomously formed its own corporation, obtained an IRS Employer Identification Number, (that allows it to legally operate as a business, hire staff and obtain licenses), secured an FDIC-insured bank account and a crypto wallet.

    Operating under the persona “Manfred Macx,” it is designed to trade crypto and can already transact in more than 30 cryptocurrencies, moving funds between its bank account and digital wallet. coindesk.com/tech/2026/05/01/a #Crypto #Manfred #ManfredAI #CryptoWallet #CryptoTrader #AI #AIAgent #FDIC #EIN #CryptoCurrencies #DigitalWwallet

  46. Is this legal??

    Autonomous AI Agent "Manfred AI" autonomously formed its own corporation, obtained an IRS Employer Identification Number, (that allows it to legally operate as a business, hire staff and obtain licenses), secured an FDIC-insured bank account and a crypto wallet.

    Operating under the persona “Manfred Macx,” it is designed to trade crypto and can already transact in more than 30 cryptocurrencies, moving funds between its bank account and digital wallet. coindesk.com/tech/2026/05/01/a