I think it might be helpful to have them ordered by date. So the first event listed is the next upcoming event, so this would be reordered so that the Kalyani meet up is the first one listed.

One of the more special things that can come out of irl events are all the great pictures. We should make handling of lots of images and displaying them beautifully one of the core design choices of this site. 🙂

dark mode allows website visitors to switch to an eye-friendly and resource-saving design whenever they want. There are a couple of UX patterns we can use to add a dark theme to your site.

Hi there, IDK if this is the right place to open this issue, but anyway if there is a mistake please let me know

So the issue is when linking the forem account with your Dev.to account, it seems that the CSS not loading or something

I don't know if this is for the forem accounts only or for other accounts as well

As I mentioned in the comment on this post on dev.to. I would like a Global DEV Meet-Up / Hackathon Day. where local organizers set up a local event all on the same day.
Anyone got any ideas on how this could be organized? and Will the DEV team support this effort? @benhalpern?

A rather obscure bug that may be caused by something related to gatsby preloading.

To reproduce:

1. Go to https://irl.dev. Make sure you are using Chrome (may be also valid for other Blink browsers) and a desktop viewport.
2. Click on the first button
3. Click on the second button
4. Scroll up

This does not occur when you use the direct link. Nodes are still there and can be inspected with DevTools. I could not figure out the exact breakpoint, but for me it breaks at around 845px window width. Resizing the window makes it normal again.

OS/Browser:

Chromium 75.0.3770.90 (Official Build) snap, Debian 10
Also tested on latest Chrome, Windows 7.
Does not occur in Firefox.

Hey y'all,

Right now, we don't have any events in Europe that have been proposed, so this isn't an issue yet, but we should be prepared for it when it happens. If you are not familiar with the GDPR and don't want to wait for my article on it later today, it's Europe's online privacy legislation that went into effect last year. Any company that collects data on EU citizens, even if such company does not have an official presence within any of the EU member states, is legally obliged to follow the law.

It mostly comes down to compliance and transparency. We have to make note of what data we are collecting, where it is being stored, what measures are being taken to secure that data, under which conditions that data is shared with third parties, and a data protection officer needs to be elected who is legally responsible for GDPR violations and would appear in court on behalf of DEV.TO if we were ever summoned to court for a violation (you have to try pretty hard to get a violation though).

We need to have a plan in place which would allow us to notify site members of a data breach within 24 hours, providing details on the extend of data that appears to have been leaked, and what measures are being taken to minimize the damage and prevent the incident from happening again. An EU citizen can ask for a copy of all of their data stored on the site, at which point a "reasonable timeframe" is given to respond to the request, which must be provided in a "machine-readable format." As you can see, it is incredibly vague at most points.

As far as I know, we don't collect that much data from users, most of it is from posts/profiles/comments and that participation is all voluntary. If someone does not consent to having that data be collected, then they have no business hanging out on an online forum. We would need to have a data privacy statement as part of the signup process that outlines what is collected and why we need that info, and users will have the option to opt-out of collection. Because of the nature of the site, that largely comes down to them not sharing information publicly.

Some data is considered more valuable than others, specifically sexual identity, political beliefs, and health information. Many of these subjects appear on DEV.TO discussions on a fairly frequent basis; we probably just need to make a note that all participation is voluntary and no efforts are being made to mine and catalog data of that nature from posts and comments (or at least I hope not).

We would need to collect the data protection agreement for any third parties who we share data with or who store data on our behalf. Hosting providers, analytics services, e-mail marketing services, etc. Every one of those companies should have a generic DPA that they can send to us for signature which they will then countersign, which basically outlines what data they collect and how they would respond to a breach, etc.

This protections only apply to EU citizens living in EU member states, but my experience has been that attempting to create an implementation which provides EU citizens proper rights and continues to carelessly collect and distribute data on everyone else creates a headache for themselves and it is actually a lot more effort to half-ass compliance like that. Affirming privacy as a universal right and giving all members the same data protections and requiring them to opt-in to use our services is pretty in-line with open-source morals I would say.

Basically, we need:

• A staff member to act as Data Protection Officer who is willing to appear before the legal courts of the EU if a major violation occurred on the site and who is responsible for dealing with any questions or requests related to the GDPR.
• A process to collect all data related to a user in plaintext, JSON, or some other relatively platform-neutral data structure.
• A [email protected] e-mail address for questions, withdrawing consent, requesting data, etc
• A data protection strategy and breach notification policy which both get posted to the site and are available for view during the sign-up process.
• Gathering explicit consent from the user for data collection (they have to check a box or sign their initials, consent cannot be consumed unless you act against it and consent inputs cannot be prepopulated). For current users, you could add this to the profile or just send out a notice that by continuing to keep a DEV.TO account and participate on the site, you are consenting to whatever tiny amount of data collection that gets performed.
• Users should have a way to opt out of analytics reporting if possible, or info should at least be anonymized (mask part of IP address, random UUID assignment) so it is impossible to personally identify a member from the data alone.
• A way for users to request the deletion of all data currently stored about themselves in a timely manner.
• I personally found it helpful to map out every data point that was stored on company servers vs data that was sent to a third party in one form or another and ended up with a really cool dataflow graph showing where collected information is stored and what processing agreements cover its existence at that location.

Happy to provide more info or answer more questions. I am obviously not a lawyer, my only credential is that I have previously helped an employer comply with legislation. We haven't been targeted in a lawsuit yet, so I must have done something right!

This probably should have been a thing on DEV.TO for a while, but reading specifically about this site made me realize we need to comply with the GDPR.

Let me know what I can help with!