<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Stijn de Ligt</title>
    <description>The latest articles on DEV Community by Stijn de Ligt (@tealover418).</description>
    <link>https://dev.to/tealover418</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F708037%2F3d5d5cb3-c2be-4d09-9f58-71e3d63e2ff9.jpg</url>
      <title>DEV Community: Stijn de Ligt</title>
      <link>https://dev.to/tealover418</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tealover418"/>
    <language>en</language>
    <item>
      <title>How to ask for payment when finding security issues in a big website</title>
      <dc:creator>Stijn de Ligt</dc:creator>
      <pubDate>Sun, 05 Jun 2022 12:29:38 +0000</pubDate>
      <link>https://dev.to/tealover418/how-to-ask-for-payment-when-finding-security-issues-in-a-big-website-2738</link>
      <guid>https://dev.to/tealover418/how-to-ask-for-payment-when-finding-security-issues-in-a-big-website-2738</guid>
      <description>&lt;p&gt;Recently I discovered two medium size security hacks in an international platform that ironically enough specializes in security by means of phishing prevention.&lt;/p&gt;

&lt;p&gt;These issues allowed me to have insight in their internal db and graphql structure and insert data that should not be there. With these hacks I could theoretically make the platform useless for some of their paying clients, but obviously I am not going to do that.&lt;/p&gt;

&lt;p&gt;I'd like to point these out to them, but am not intending to go unpaid. How would you contact the people behind this platform with my intentions? It's important not to come off as threatening (I really mean no harm), and not to reveal the source of the issues right away.&lt;/p&gt;

&lt;p&gt;As you might guess I have no knowledge about anything like this. If you think this is a bad idea to begin with feel free to share your thoughts as well!&lt;/p&gt;

</description>
      <category>security</category>
      <category>help</category>
      <category>freelance</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Improve your iframe UX with React LoadingIframes</title>
      <dc:creator>Stijn de Ligt</dc:creator>
      <pubDate>Sun, 29 May 2022 19:55:14 +0000</pubDate>
      <link>https://dev.to/tealover418/improve-your-iframe-ux-with-react-loadingiframes-16j6</link>
      <guid>https://dev.to/tealover418/improve-your-iframe-ux-with-react-loadingiframes-16j6</guid>
      <description>&lt;p&gt;Iframes can take a long time to load depending on the source. While your user is waiting it's preferable to give feedback on what is happening with their page, and why they are staring at a blank screen.&lt;/p&gt;

&lt;p&gt;Using &lt;a href="https://github.com/tea-lover-418/react-loading-iframe" rel="noopener noreferrer"&gt;react-loading-iframe&lt;/a&gt; you can show a skeleton that is displayed until the content of the iframe is ready. &lt;/p&gt;

&lt;p&gt;Install using &lt;code&gt;npm i react-loading-iframe&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Then include on your react components the following way:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;import LoadingIframe from 'react-loading-iframe';

const Skeleton = () =&amp;gt; {
  return &amp;lt;div&amp;gt;Cool loading screen&amp;lt;/div&amp;gt;;
};

export const BasicExample = () =&amp;gt; {
  return (
    &amp;lt;LoadingIframe
      skeleton={&amp;lt;Skeleton /&amp;gt;}
      src="https://google.com"
      className="your-class"
      frameBorder={0}
    /&amp;gt;
  );
};
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Any suggestions on this are welcome as this is my first open source repository! Please give it a try.&lt;/p&gt;

</description>
      <category>react</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
