home.social

Search

45 results for “typedcode”

  1. I recently found which is a 'is a fully functional terminal-based music player, library, and streaming audio server'.

    Since I could not find any possibility to stream to a PC I decided to write a web-based player to stream the music to using musikcube.
    Technology wise I use typescript and vue.

    The API is nicely documented so the player makes good progress :)

  2. It will take a while to relearn typing...

  3. Fable 4.21.0 is out 🎉

    Using `jsOptions` via TypeScript target now generate typed code, so you can enjoy your types even when doing some interop.

    It also improves FormattableString and Uri supports.

    Python also received some love with a fix when reporting errors.

    #fsharp #fablecompiler

  4. This Friday I had the privilege of giving the Zagreb #Python meetup a talk on the why, when not and how of #statictyping in Python.

    We in the Python community are given this incredible choice between writing dynamically typed code for fast prototyping or using a pretty sophisticated (IMO stronger than Java, Go or even C#) type system for bigger projects. Or anything in between.

    The situation isn't perfect, of course, but this is still pretty amazing. Most programming languages don't get this.

  5. CW: On Swisspost and Akamai filtering

    It turns out that Swisspost¹ uses Akamai to "protect" its login system called SwissID² and they redirect to

    hxxps://login.swissid.ch/idp/oauth2/authorize?scope=openid+email+phone+profile&response_type=code&redirect_uri=https%3A%2F%2Faccount.post.ch%2Fredirect%2Fid-confirmation&state=vX7TlNn7IhybofD70YM0_gLsWLzv2r3tSHFubjqvF6o&nonce=z_8pbla4cMqwQABW-Z1l5btJMHOSjZBjvMbnfIEpMII&client_id=klp-client&ui_locales=it &acr_values=loa-1&prompt=login

    and this login.swissid.ch lives behind Akamai.

    It so happens that the IP I use to connect is also a Tor _relay_ (not an exit node) and Akamai offers the possibility of blocking "all of Tor" (i.e. exits _and_ relays) as "bad people". Of course if you know anything about Tor you also know that relays are not exits and no traffic ever leaves a relay to "the Internet" but, "sekurity theatre" being what it is, they block it anyway.

    Several years ago (2013 or so?) Apple used Akamai (they still do) and support.apple.com blocked Tor relays too but, on the :birdsite:, I contacted Akamai's CSO out of desperation (aka "csoandy") who very kindly looked into it and fixed it! :flan_awe:​ (I assume by educating Apple, or so I hope).

    Well, unfortunately Andy has left Akamai and now I cannot have someone "give the talk" to the Swiss Post.

    Oh, if you happen to use SwissSign PKI solutions you have the same demented problem.

    :flan_set_fire:​

    #SwissPost #SwissSign #SwissID #Tor #Akamai
    __
    ¹ posta.ch/ (in Italian…)
    ² swissid.ch/

  6. There are over 538K SQL code blocks in docs on GitHub:

    🔎 github.com/search?q=%2F%60%60%

    We believe SQL code in docs should be runnable.

    We created #SQLCodeLenses with new #SQLBookmarks 📑 in #MarkdownSQLPro Tools 🛠️ for VS Code IDE.

    Get #SQLTools drivers to connect to data sources and run SQL queries:

    📥 marketplace.visualstudio.com/s

    Our Markdown SQL Pro Tools add new SQL code lenses to enable direct SQL code interactions.

    Subscribe to get notified when they will be released:

    💖 github.com/sponsors/RandomFrac

  7. Even though I fixed semantic mess of #elixirlang by publishing the #uptight library github.com/doma-engineering/up, I still need to interact with non-tightly-typed code sometimes.

    Sometimes, just unwrapping isn't enough or isn't ergonomic, so then I have to go back to operating with raw binaries.

    While typing those, as anyone should, I feel bad when I write `binary` and I also feel bad when I write `String.t()`. Again, as anyone should.

    After thinking about this issue for so long, I finally understood that in #elixir, both of those types should be called `uninterpreted_binary()` or `blob()`. I know it will never happen, but `String.t()` has to be deprecated.

    The reason not to use `binary()` type in Elixir is clear. When binaries are *interpreted* as Strings, there's a whole lot of semantics going on, and this interpretation is way more pushed than in #erlang. But it still happens at interpretation time, it has nothing to do with the type of an term presented. This is the reason not to use `String.t()`. So yeah, the most correct way to put it is `blob()`: an uninterpreted raw binary, that is, however, easily and automatically gets interpreted as strings.

    As a matter of fact, `String.t()` may just be the Elixir's hundred thousand dollar mistake.

  8. What's this? A phishing email that doesn't get any spelling or grammar wrong? Impressive.

    The URL included in the email has a redirect to:

    newkste66f02.s3.amazonaws.com/

    Which just has this in the HTML:

    ```
    window.location.assign("jademountains.net/s2");
    ```

    Which redirs with an appended slash:

    jademountains.net/s2/

    Which redirs to

    coinbase-v3teamapp.com/signin/

    Which isn't a legit coinbase domain -- URL registered today. Which resolves to a blank page with a single javascript payload:

    coinbase-v3teamapp.com//static

    Which appears to be a React app, which then ultimately triggers a load of this URL, which includes a list of desired OAuth scopes:

    login.coinbase.com/oauth2/auth${e.data.data.clientId}&redirect_uri=${e.data.data.redirectURI}&account=all&scope=wallet:accounts:read,wallet:accounts:update,wallet:accounts:create,wallet:accounts:delete,wallet:addresses:read,wallet:addresses:create,wallet:buys:read,wallet:buys:create,wallet:deposits:read,wallet:deposits:create,wallet:notifications:read,wallet:payment-methods:read,wallet:payment-methods:delete,wallet:payment-methods:limits,wallet:sells:read,wallet:sells:create,wallet:transactions:read,wallet:transactions:send,wallet:transactions:request,wallet:transactions:transfer,wallet:user:read,wallet:user:update,wallet:user:email,wallet:withdrawals:read,wallet:withdrawals:create,offline_access

    Which, cleaned up, is this:

    wallet:accounts:read
    wallet:accounts:update
    wallet:accounts:create
    wallet:accounts:delete
    wallet:addresses:read
    wallet:addresses:create
    wallet:buys:read
    wallet:buys:create
    wallet:deposits:read
    wallet:deposits:create
    wallet:notifications:read
    wallet:payment-methods:read
    wallet:payment-methods:delete
    wallet:payment-methods:limits
    wallet:sells:read
    wallet:sells:create
    wallet:transactions:read
    wallet:transactions:send
    wallet:transactions:request
    wallet:transactions:transfer
    wallet:user:read
    wallet:user:update
    wallet:user:email
    wallet:withdrawals:read
    wallet:withdrawals:create
    offline_access

    Which is, I'd assume, basically everything, including the ability to withdraw:

    wallet:withdrawals:read
    wallet:withdrawals:create

    Before ultimately ending up at what appears to be a coinbase-owned domain:

    login.coinbase.com/signin?clie

    ```
    $ dig -t A coinbase.com +short
    104.18.35.15
    172.64.152.241
    $ dig -t A login.coinbase.com +short
    172.64.152.241
    104.18.35.15
    ```

    The OAuth bits of the URL tell me that this must be a third-party Coinbase app. Can't find an easy way to map that client ID of

    c300bb46-07f8-4257-9760-a892c704a8b6

    back to an app page though to report it.

    What the hell. I'll bite. I don't have anything in Coinbase anymore. Let's see if I can't get the actual app and report it.

    Logging in... SMS 2-factor, Email 3rd factor.

    Aaaaaand BINGO. The third-party app is named

    "Third Party: Support"

    However, searching for that in Coinbase's app search yields... nothing. Great job, Coinbase.

    Okay, how do I go about reporting this to them? Looks like there's a chat option. Fine. Gonna use this post as my description of what's going on.

    #coinbase #phishing #web3 #web3isgoinggreat #cryptocurrency

  9. What's this? A phishing email that doesn't get any spelling or grammar wrong? Impressive.

    The URL included in the email has a redirect to:

    newkste66f02.s3.amazonaws.com/

    Which just has this in the HTML:

    ```
    window.location.assign("jademountains.net/s2");
    ```

    Which redirs with an appended slash:

    jademountains.net/s2/

    Which redirs to

    coinbase-v3teamapp.com/signin/

    Which isn't a legit coinbase domain -- URL registered today. Which resolves to a blank page with a single javascript payload:

    coinbase-v3teamapp.com//static

    Which appears to be a React app, which then ultimately triggers a load of this URL, which includes a list of desired OAuth scopes:

    login.coinbase.com/oauth2/auth${e.data.data.clientId}&redirect_uri=${e.data.data.redirectURI}&account=all&scope=wallet:accounts:read,wallet:accounts:update,wallet:accounts:create,wallet:accounts:delete,wallet:addresses:read,wallet:addresses:create,wallet:buys:read,wallet:buys:create,wallet:deposits:read,wallet:deposits:create,wallet:notifications:read,wallet:payment-methods:read,wallet:payment-methods:delete,wallet:payment-methods:limits,wallet:sells:read,wallet:sells:create,wallet:transactions:read,wallet:transactions:send,wallet:transactions:request,wallet:transactions:transfer,wallet:user:read,wallet:user:update,wallet:user:email,wallet:withdrawals:read,wallet:withdrawals:create,offline_access

    Which, cleaned up, is this:

    wallet:accounts:read
    wallet:accounts:update
    wallet:accounts:create
    wallet:accounts:delete
    wallet:addresses:read
    wallet:addresses:create
    wallet:buys:read
    wallet:buys:create
    wallet:deposits:read
    wallet:deposits:create
    wallet:notifications:read
    wallet:payment-methods:read
    wallet:payment-methods:delete
    wallet:payment-methods:limits
    wallet:sells:read
    wallet:sells:create
    wallet:transactions:read
    wallet:transactions:send
    wallet:transactions:request
    wallet:transactions:transfer
    wallet:user:read
    wallet:user:update
    wallet:user:email
    wallet:withdrawals:read
    wallet:withdrawals:create
    offline_access

    Which is, I'd assume, basically everything, including the ability to withdraw:

    wallet:withdrawals:read
    wallet:withdrawals:create

    Before ultimately ending up at what appears to be a coinbase-owned domain:

    login.coinbase.com/signin?clie

    ```
    $ dig -t A coinbase.com +short
    104.18.35.15
    172.64.152.241
    $ dig -t A login.coinbase.com +short
    172.64.152.241
    104.18.35.15
    ```

    The OAuth bits of the URL tell me that this must be a third-party Coinbase app. Can't find an easy way to map that client ID of

    c300bb46-07f8-4257-9760-a892c704a8b6

    back to an app page though to report it.

    What the hell. I'll bite. I don't have anything in Coinbase anymore. Let's see if I can't get the actual app and report it.

    Logging in... SMS 2-factor, Email 3rd factor.

    Aaaaaand BINGO. The third-party app is named

    "Third Party: Support"

    However, searching for that in Coinbase's app search yields... nothing. Great job, Coinbase.

    Okay, how do I go about reporting this to them? Looks like there's a chat option. Fine. Gonna use this post as my description of what's going on.

    #coinbase #phishing #web3 #web3isgoinggreat #cryptocurrency

  10. What's this? A phishing email that doesn't get any spelling or grammar wrong? Impressive.

    The URL included in the email has a redirect to:

    newkste66f02.s3.amazonaws.com/

    Which just has this in the HTML:

    ```
    window.location.assign("jademountains.net/s2");
    ```

    Which redirs with an appended slash:

    jademountains.net/s2/

    Which redirs to

    coinbase-v3teamapp.com/signin/

    Which isn't a legit coinbase domain -- URL registered today. Which resolves to a blank page with a single javascript payload:

    coinbase-v3teamapp.com//static

    Which appears to be a React app, which then ultimately triggers a load of this URL, which includes a list of desired OAuth scopes:

    login.coinbase.com/oauth2/auth${e.data.data.clientId}&redirect_uri=${e.data.data.redirectURI}&account=all&scope=wallet:accounts:read,wallet:accounts:update,wallet:accounts:create,wallet:accounts:delete,wallet:addresses:read,wallet:addresses:create,wallet:buys:read,wallet:buys:create,wallet:deposits:read,wallet:deposits:create,wallet:notifications:read,wallet:payment-methods:read,wallet:payment-methods:delete,wallet:payment-methods:limits,wallet:sells:read,wallet:sells:create,wallet:transactions:read,wallet:transactions:send,wallet:transactions:request,wallet:transactions:transfer,wallet:user:read,wallet:user:update,wallet:user:email,wallet:withdrawals:read,wallet:withdrawals:create,offline_access

    Which, cleaned up, is this:

    wallet:accounts:read
    wallet:accounts:update
    wallet:accounts:create
    wallet:accounts:delete
    wallet:addresses:read
    wallet:addresses:create
    wallet:buys:read
    wallet:buys:create
    wallet:deposits:read
    wallet:deposits:create
    wallet:notifications:read
    wallet:payment-methods:read
    wallet:payment-methods:delete
    wallet:payment-methods:limits
    wallet:sells:read
    wallet:sells:create
    wallet:transactions:read
    wallet:transactions:send
    wallet:transactions:request
    wallet:transactions:transfer
    wallet:user:read
    wallet:user:update
    wallet:user:email
    wallet:withdrawals:read
    wallet:withdrawals:create
    offline_access

    Which is, I'd assume, basically everything, including the ability to withdraw:

    wallet:withdrawals:read
    wallet:withdrawals:create

    Before ultimately ending up at what appears to be a coinbase-owned domain:

    login.coinbase.com/signin?clie

    ```
    $ dig -t A coinbase.com +short
    104.18.35.15
    172.64.152.241
    $ dig -t A login.coinbase.com +short
    172.64.152.241
    104.18.35.15
    ```

    The OAuth bits of the URL tell me that this must be a third-party Coinbase app. Can't find an easy way to map that client ID of

    c300bb46-07f8-4257-9760-a892c704a8b6

    back to an app page though to report it.

    What the hell. I'll bite. I don't have anything in Coinbase anymore. Let's see if I can't get the actual app and report it.

    Logging in... SMS 2-factor, Email 3rd factor.

    Aaaaaand BINGO. The third-party app is named

    "Third Party: Support"

    However, searching for that in Coinbase's app search yields... nothing. Great job, Coinbase.

    Okay, how do I go about reporting this to them? Looks like there's a chat option. Fine. Gonna use this post as my description of what's going on.

    #coinbase #phishing #web3 #web3isgoinggreat #cryptocurrency

  11. What's this? A phishing email that doesn't get any spelling or grammar wrong? Impressive.

    The URL included in the email has a redirect to:

    newkste66f02.s3.amazonaws.com/

    Which just has this in the HTML:

    ```
    window.location.assign("jademountains.net/s2");
    ```

    Which redirs with an appended slash:

    jademountains.net/s2/

    Which redirs to

    coinbase-v3teamapp.com/signin/

    Which isn't a legit coinbase domain -- URL registered today. Which resolves to a blank page with a single javascript payload:

    coinbase-v3teamapp.com//static

    Which appears to be a React app, which then ultimately triggers a load of this URL, which includes a list of desired OAuth scopes:

    login.coinbase.com/oauth2/auth${e.data.data.clientId}&redirect_uri=${e.data.data.redirectURI}&account=all&scope=wallet:accounts:read,wallet:accounts:update,wallet:accounts:create,wallet:accounts:delete,wallet:addresses:read,wallet:addresses:create,wallet:buys:read,wallet:buys:create,wallet:deposits:read,wallet:deposits:create,wallet:notifications:read,wallet:payment-methods:read,wallet:payment-methods:delete,wallet:payment-methods:limits,wallet:sells:read,wallet:sells:create,wallet:transactions:read,wallet:transactions:send,wallet:transactions:request,wallet:transactions:transfer,wallet:user:read,wallet:user:update,wallet:user:email,wallet:withdrawals:read,wallet:withdrawals:create,offline_access

    Which, cleaned up, is this:

    wallet:accounts:read
    wallet:accounts:update
    wallet:accounts:create
    wallet:accounts:delete
    wallet:addresses:read
    wallet:addresses:create
    wallet:buys:read
    wallet:buys:create
    wallet:deposits:read
    wallet:deposits:create
    wallet:notifications:read
    wallet:payment-methods:read
    wallet:payment-methods:delete
    wallet:payment-methods:limits
    wallet:sells:read
    wallet:sells:create
    wallet:transactions:read
    wallet:transactions:send
    wallet:transactions:request
    wallet:transactions:transfer
    wallet:user:read
    wallet:user:update
    wallet:user:email
    wallet:withdrawals:read
    wallet:withdrawals:create
    offline_access

    Which is, I'd assume, basically everything, including the ability to withdraw:

    wallet:withdrawals:read
    wallet:withdrawals:create

    Before ultimately ending up at what appears to be a coinbase-owned domain:

    login.coinbase.com/signin?clie

    ```
    $ dig -t A coinbase.com +short
    104.18.35.15
    172.64.152.241
    $ dig -t A login.coinbase.com +short
    172.64.152.241
    104.18.35.15
    ```

    The OAuth bits of the URL tell me that this must be a third-party Coinbase app. Can't find an easy way to map that client ID of

    c300bb46-07f8-4257-9760-a892c704a8b6

    back to an app page though to report it.

    What the hell. I'll bite. I don't have anything in Coinbase anymore. Let's see if I can't get the actual app and report it.

    Logging in... SMS 2-factor, Email 3rd factor.

    Aaaaaand BINGO. The third-party app is named

    "Third Party: Support"

    However, searching for that in Coinbase's app search yields... nothing. Great job, Coinbase.

    Okay, how do I go about reporting this to them? Looks like there's a chat option. Fine. Gonna use this post as my description of what's going on.

    #coinbase #phishing #web3 #web3isgoinggreat #cryptocurrency

  12. What's this? A phishing email that doesn't get any spelling or grammar wrong? Impressive.

    The URL included in the email has a redirect to:

    newkste66f02.s3.amazonaws.com/

    Which just has this in the HTML:

    ```
    window.location.assign("jademountains.net/s2");
    ```

    Which redirs with an appended slash:

    jademountains.net/s2/

    Which redirs to

    coinbase-v3teamapp.com/signin/

    Which isn't a legit coinbase domain -- URL registered today. Which resolves to a blank page with a single javascript payload:

    coinbase-v3teamapp.com//static

    Which appears to be a React app, which then ultimately triggers a load of this URL, which includes a list of desired OAuth scopes:

    login.coinbase.com/oauth2/auth${e.data.data.clientId}&redirect_uri=${e.data.data.redirectURI}&account=all&scope=wallet:accounts:read,wallet:accounts:update,wallet:accounts:create,wallet:accounts:delete,wallet:addresses:read,wallet:addresses:create,wallet:buys:read,wallet:buys:create,wallet:deposits:read,wallet:deposits:create,wallet:notifications:read,wallet:payment-methods:read,wallet:payment-methods:delete,wallet:payment-methods:limits,wallet:sells:read,wallet:sells:create,wallet:transactions:read,wallet:transactions:send,wallet:transactions:request,wallet:transactions:transfer,wallet:user:read,wallet:user:update,wallet:user:email,wallet:withdrawals:read,wallet:withdrawals:create,offline_access

    Which, cleaned up, is this:

    wallet:accounts:read
    wallet:accounts:update
    wallet:accounts:create
    wallet:accounts:delete
    wallet:addresses:read
    wallet:addresses:create
    wallet:buys:read
    wallet:buys:create
    wallet:deposits:read
    wallet:deposits:create
    wallet:notifications:read
    wallet:payment-methods:read
    wallet:payment-methods:delete
    wallet:payment-methods:limits
    wallet:sells:read
    wallet:sells:create
    wallet:transactions:read
    wallet:transactions:send
    wallet:transactions:request
    wallet:transactions:transfer
    wallet:user:read
    wallet:user:update
    wallet:user:email
    wallet:withdrawals:read
    wallet:withdrawals:create
    offline_access

    Which is, I'd assume, basically everything, including the ability to withdraw:

    wallet:withdrawals:read
    wallet:withdrawals:create

    Before ultimately ending up at what appears to be a coinbase-owned domain:

    login.coinbase.com/signin?clie

    ```
    $ dig -t A coinbase.com +short
    104.18.35.15
    172.64.152.241
    $ dig -t A login.coinbase.com +short
    172.64.152.241
    104.18.35.15
    ```

    The OAuth bits of the URL tell me that this must be a third-party Coinbase app. Can't find an easy way to map that client ID of

    c300bb46-07f8-4257-9760-a892c704a8b6

    back to an app page though to report it.

    What the hell. I'll bite. I don't have anything in Coinbase anymore. Let's see if I can't get the actual app and report it.

    Logging in... SMS 2-factor, Email 3rd factor.

    Aaaaaand BINGO. The third-party app is named

    "Third Party: Support"

    However, searching for that in Coinbase's app search yields... nothing. Great job, Coinbase.

    Okay, how do I go about reporting this to them? Looks like there's a chat option. Fine. Gonna use this post as my description of what's going on.

    #coinbase #phishing #web3 #web3isgoinggreat #cryptocurrency

  13. EDIT May 2: Thank everyone for sharing, this has all been taken care of!

    Could someone who speaks #Arabic, #Chinese, or #Basque help me update the jointhefediverse.net site? I'm trying to remove links to joinfirefish.org and want to make sure I do it right.

    github.com/search?q=repo%3Ajoi

    Any help would be very appreciated!

    #translation #localization #TranslationHelp #LocalizationHelp

  14. De #iPRES 2024 Programmacommissie heeft je hulp nodig! De commissie is overweldigd door het grote aantal inzendingen voor haar internationale conferentie over digitale duurzaamheid en zoekt daarom extra beoordelaars. Heb jij expertise op dit terrrein en wat tijd om te helpen? 👉 Meld je aan via auth.cern.ch/auth/realms/cern/. Alvast bedankt voor je hulp!

    Beeld via Tim Mossholder

  15. I made this !
    I made a little game where you get to write a tune and hear me play it on my cello - and it works! Really it's a static web page that has interactive elements. For anyone who does web development it is very basic, but you know, I made it. I am not a coder by training, but sure I typed code before... (*cough*) Ok, in 1983, and th
    lauraritchie.com/2024/03/12/i-
    #LifeLearning #ResonanceProject #cymatics #ChatGPT #Coding #Game #kindness #Resonance #Webpage

  16. Promoting cultural literacy through arts education to foster social inclusion ec.europa.eu/info/funding-tend ; Cultural and creative approaches for gender-responsive STEAM education ec.europa.eu/info/funding-tend; Fostering socio-economic development and job creation in rural and remote areas through cultural tourism ec.europa.eu/info/funding-tend #ArtsEducation #Inclusion #gender #STEAM #CulturalTourism #research #funding #digital

  17. There are EIGHT amazing calls in this group. Cultural heritage in transformation – facing change with confidence ec.europa.eu/info/funding-tend ; A world leading European video game innovation system ec.europa.eu/info/funding-tend ; Advanced technologies for remote monitoring of heritage monuments and artefacts ec.europa.eu/info/funding-tend ; Cultural and creative industries for a sustainable climate transition ec.europa.eu/info/funding-tend #CulturalHeritage #Heritage #VideoGames #RemoteMonitoring #ClimateEmergency

  18. What result did you come up with? Please share the output with us in the comment section. 🤔👇👇👇

    #OneTeam #TYPO3Store #TYPO3Code #TYPO3Coder #Coding #TYPO3 #T3Planet