<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Anselm Hannemann on Medium]]></title>
        <description><![CDATA[Stories by Anselm Hannemann on Medium]]></description>
        <link>https://medium.com/@helloanselm?source=rss-695f9400a1da------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9J_WFZ6iE1MD4VltxZ15Wg.jpeg</url>
            <title>Stories by Anselm Hannemann on Medium</title>
            <link>https://medium.com/@helloanselm?source=rss-695f9400a1da------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:29:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@helloanselm/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Going Dark & Bright]]></title>
            <link>https://medium.com/colloq/going-dark-bright-8ef8df35c13b?source=rss-695f9400a1da------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ef8df35c13b</guid>
            <dc:creator><![CDATA[Anselm Hannemann]]></dc:creator>
            <pubDate>Tue, 15 Jan 2019 14:37:32 GMT</pubDate>
            <atom:updated>2019-01-16T06:03:13.010Z</atom:updated>
            <content:encoded><![CDATA[<p>Sometimes we all need a challenge. Mine was to find out how much effort it would be to support Apple’s new Dark Mode on Colloq. It turned out that it was more work than initially anticipated, but I stayed on it for a couple more hours, cleaned up code and eventually made it work. Since today, you may see various differences throughout the entire interface.</p><h4>What’s Dark Mode</h4><p>First of all I want to explain what I’m talking about. With <a href="https://www.apple.com/macos/mojave/">macOS Mojave</a>, Apple introduced a new color scheme called “dark mode”. When activated, the entire operating system switches to a dark appearance, which is quite nice for several circumstances. Some people might just prefer it over the light default mode we’re used to ever since.</p><p>When Apple announced this feature, it was only a matter of time that web developers would talk about getting some sort of query to detect the color mode and WebKit shipped a new Media Query in their <a href="https://webkit.org/blog/8475/release-notes-for-safari-technology-preview-68/">Safari Technology Preview 68</a> on October, 24th 2018.</p><h4>Prefers-color-scheme</h4><p>With the new Media Query web developers can now target light and dark mode users specifically and adapt their pages to the chosen user preference:</p><pre>body {<br>     background-color: white;<br>     color: black;<br>}<br><br>@media (prefers-color-scheme: dark) {<br>     body {<br>          background-color: black;<br>          color: white;<br>     }<br>}</pre><p>If you test this in any of the current Safari Technology Previews you can see what it does to your webpage by switching the OS theme in your settings. Quite nice, right?</p><h4>A cleanup opportunity</h4><p>When I started researching how I can support this on Colloq, I realized a few things regarding our CSS codebase. First, we wrote all color values as hex codes all the time, not variables. This now became a problem, because it would have meant to write a dark mode media query for every color occurrence in our CSS.</p><h4>CSS Custom Properties</h4><p>My first task was to convert all existing color values into Custom Properties which in this case, serve as our color variables.</p><h4>Color Palettes</h4><p>When designing for two entirely different color schemes, it doesn’t take long until you realize that your current color palette is not going to work. A nice light grey border in light mode might look very ugly in dark mode.</p><h4>Colloq is now bright and dark</h4><p>If you access Colloq with a browser and OS that supports the new Media Queries already, you will get your preferred color scheme on our website as well. Of course not everything is perfect yet, but we think it’s good enough for a first version to be pushed out to our users.</p><h4>Colloq’s Bright Scheme</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pVTFW4HoEqVmGPIlv_FIdg.png" /></figure><h4>Colloq’s Dark Scheme</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2kP4j425gBgSZQXRKopKFw.png" /></figure><p>Your feedback is always very valuable, please let us know your thoughts and how you like it. If you encounter any bugs or have difficulties with some contrasts or colors, please also let us know, so we can fix it.</p><p>Have a good day, enjoy Colloq in whichever mode you prefer and <a href="https://medium.com/events/latest">discover some new events</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ef8df35c13b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colloq/going-dark-bright-8ef8df35c13b">Going Dark &amp; Bright</a> was originally published in <a href="https://medium.com/colloq">Colloq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet the Organizers!]]></title>
            <link>https://medium.com/colloq/meet-the-organizers-10d9408e2a34?source=rss-695f9400a1da------2</link>
            <guid isPermaLink="false">https://medium.com/p/10d9408e2a34</guid>
            <dc:creator><![CDATA[Anselm Hannemann]]></dc:creator>
            <pubDate>Mon, 03 Dec 2018 09:42:30 GMT</pubDate>
            <atom:updated>2018-12-03T09:43:02.602Z</atom:updated>
            <content:encoded><![CDATA[<p>Event organisers have a tough job. They spend hundreds of hours and a lot of energy into organising an event, but are rarely known personally by the attendees. Since we’re all about connecting people, we want to give our users the possibility to get to know the people doing all the hard work to bring these conferences to life.</p><p>Our event pages now feature a new section that is entirely dedicated to the people who are organizing the event. This change allows our users to learn more about the organiser and their team, what drives and motivates them and what else they might be up to.</p><p>We also want to encourage organizers to <a href="https://medium.com/account;update">complete their public profile</a>, share more about themselves and to better connect with their audience.</p><p>We are also working on another new feature that will bring users and organizers even closer together. More on this will follow soon…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10d9408e2a34" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colloq/meet-the-organizers-10d9408e2a34">Meet the Organizers!</a> was originally published in <a href="https://medium.com/colloq">Colloq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Facing Reality: Event Cancellation]]></title>
            <link>https://medium.com/colloq/facing-reality-event-cancellation-dc1e035df1b4?source=rss-695f9400a1da------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc1e035df1b4</guid>
            <dc:creator><![CDATA[Anselm Hannemann]]></dc:creator>
            <pubDate>Fri, 30 Nov 2018 13:52:27 GMT</pubDate>
            <atom:updated>2018-11-30T13:54:15.663Z</atom:updated>
            <content:encoded><![CDATA[<p>We honestly hope that no one ever needs to cancel their event, but having experienced this situation ourselves before have to stay realistic: Sometimes things happen and events need to be cancelled. From today on, we offer the possibility to cancel your events on Colloq.</p><p>In case you need to cancel your event, we now give you a new option to cancel an event, which you are able to do, if you’re part of the organizer team. After cancelling an event, we will show a banner and other indicators that this event will not take place. Once you have cancelled your event, we will also notify all related users — those who aimed to attend it, those who follow your event and all people involved in the event organisation (your event team) — via email.</p><p>Even though unfortunate circumstances can sometimes occur, let’s look positively into the future: We’re wishing all the best to organizers and their future events!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc1e035df1b4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colloq/facing-reality-event-cancellation-dc1e035df1b4">Facing Reality: Event Cancellation</a> was originally published in <a href="https://medium.com/colloq">Colloq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our Downtime After a Spam Attack]]></title>
            <link>https://medium.com/colloq/our-downtime-after-a-spam-attack-527b41807f35?source=rss-695f9400a1da------2</link>
            <guid isPermaLink="false">https://medium.com/p/527b41807f35</guid>
            <dc:creator><![CDATA[Anselm Hannemann]]></dc:creator>
            <pubDate>Wed, 12 Sep 2018 16:52:13 GMT</pubDate>
            <atom:updated>2018-09-13T06:25:45.436Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the last weekend we have been hit by a spam attack and as a result, had to temporarily shut down our servers. Here is our detailed report to what has happened. <strong>Note: This incident was a spam attack which flooded our platform with random events and no data has been compromised, breached or leaked.</strong></p><h4>What happened</h4><p>On Saturday September 8th, around 12pm European time we discovered an unusually high amount of user signups and event creations. As it happened on a Saturday, it took us a little longer than usual to dig into the issue.</p><p>After analyzing what exactly was happening, we assumed the attack was about to get worse and there was little we could do at this time. We had to make the tough call to take our servers offline and with that, temporarily shut down out site to mitigate the problem. While this meant that no one would be able to access the site, we believe it was the best call we could make, to avoid any further issues caused by the flood of spam that came down on us. It also meant that the attacker would not have any further success in placing SEO content on our site and thus would hopefully stop.</p><h4>What it means for your data</h4><p>During this attack, nothing was exposed and no data has been leaked. The attack was not a hacker attack, but a spammer who tried to create a lot of spam content on our site. All events created during this time have been successfully identified. All current valid events and our users should now be able to use Colloq as usual.</p><p>The user accounts and events in question have been flagged as spam and will be deleted soon.</p><h4>What are we doing now</h4><p>We’ve learned a lot from this event. Even though it’s been a tough decision, we still believe that completely shutting down our service was the best option that we’ve had.</p><p>To go back online and mitigate such attacks we had to build quite some new infrastructure. From now on we are able to handle spam attacks like this one a lot better and without the need for shutting down access to our platform. We will write a separate, more technical post with more details soon, so we can share our useful learnings from this type of attack.</p><p>In the near future we will implement a way to shut down write access to our platform, while being able to serve something, instead of only showing a white, non-responding page. We will also evaluate how we could serve a separate status page that reflects our the current service availability without increasing our service costs a lot.</p><h4>Thanks for your support!</h4><p>We’re sorry for the long downtime and inconvenience. We appreciate your ongoing support and want to say thank you for being patient. This incident was exactly the kind you’d always think would never happen to you. Well, it easily can and as mentioned, we still don’t have all the answers to our questions of how to best prepare for things like this. But one thing is for sure: Despite all our previous implemented measures to avoid exactly this, a spam attack is very difficult to control or even avoid, and can happen easier than you’d think.</p><p>We hope everything works as expected again and that we’re now able to prevent spammers from affecting our service from humans, for humans. Not bots.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=527b41807f35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colloq/our-downtime-after-a-spam-attack-527b41807f35">Our Downtime After a Spam Attack</a> was originally published in <a href="https://medium.com/colloq">Colloq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[News in August]]></title>
            <link>https://medium.com/colloq/news-in-august-cd0c9133afeb?source=rss-695f9400a1da------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd0c9133afeb</guid>
            <dc:creator><![CDATA[Anselm Hannemann]]></dc:creator>
            <pubDate>Thu, 06 Sep 2018 05:00:00 GMT</pubDate>
            <atom:updated>2018-09-06T06:45:23.746Z</atom:updated>
            <content:encoded><![CDATA[<p>We’ve not stopped working after July and here are a few new things we added to our service over the past week.</p><h4>Call for Papers CSV and JSON Export</h4><p>To make talk selection easier for our Pro organizers who run their Call for Papers on Colloq, we added data export of submissions. You can now export the available data in either CSV or JSON format, for example to use it in Excel, Numbers or other software.</p><p>Note that you only get the information currently available in the web interface as well. This ensures that the Call for Papers stays anonymous and the selection is not based on any bias, even after export.</p><p>Not seeing any personal information can be a challenge for organizers so we added <a href="https://colloq.io/blog/call-for-papers-messages">Messages for Call for Papers</a> recently. This ensures you can discuss applicants’ proposals while maintaining anonymity. If a proposal has been chosen, the Colloq profile of the applicant will become available to the organizer. If you need more personal information you can then ask the speakers via our Messages feature.</p><h4>Other Changes</h4><ul><li>We now have auto-resizable &lt;textarea&gt; form fields for longer description texts. If you want to know how we did that, read our blog post on <a href="https://medium.com/blog/how-to-build-auto-resizing-textareas-with-ecmascript-6">How to build auto-resizing textareas with ECMAScript 6</a>.</li><li>You can now set a separate invoice email address, different from your account’s email address in your account under “Billing information”.</li><li>When you created an event on Safari on iOS the end dates where not really intuitive. They will now change in a way that should make more sense.</li><li>Accessing a not existing category of our blog will no longer trigger an exception and we will be able to sleep good at night again.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd0c9133afeb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colloq/news-in-august-cd0c9133afeb">News in August</a> was originally published in <a href="https://medium.com/colloq">Colloq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Auto-Resizing Textareas with ECMAScript 6]]></title>
            <link>https://medium.com/colloq/auto-resizing-textareas-with-ecmascript-6-3362d12f63b9?source=rss-695f9400a1da------2</link>
            <guid isPermaLink="false">https://medium.com/p/3362d12f63b9</guid>
            <dc:creator><![CDATA[Anselm Hannemann]]></dc:creator>
            <pubDate>Mon, 27 Aug 2018 12:24:44 GMT</pubDate>
            <atom:updated>2018-09-06T06:47:35.693Z</atom:updated>
            <content:encoded><![CDATA[<p>We recently added auto-resizing textarea elements to our service and here’s how we managed to do that with just a few lines of code in JavaScript.</p><h4>ES6 Classes</h4><p>Our complete JavaScript code is written in ECMAScript 6 Classes. We don’t use any library such as React.js, vue.js or similar but instead write plain JavaScript. Until now we don’t have the need to add a big framework and our codebase yet is very tidy due to the usage of new language features. To ensure we are compatible with older browsers, we use <a href="https://github.com/Rich-Harris/buble">Bublé</a> — a faster alternative to the Babel transpiler.</p><p>To ensure we don’t create a mixed, universal codebase but incorporate a separation of concerns — similar to what most people know from Scss partials — we use <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes">ES6 Classes</a> and then bind them in our initializing script to specific DOM selectors. It’s nothing else than most of us use every day when working with RequireJS, Browserify, AMD, UMD or similar methods, just it’s a web standard and offers much more convenience and flexibility. One nice thing — for example — is that it’s easy to extend Classes, a feature known from PHP and other languages already and very useful to extend functionality of third-party code.</p><h4>Resize A Form Field</h4><p>First of all we need to write the function that contains the logic for resizing the element when a user enters more text than the current height of the field allows:</p><pre>textareaDidChange() {<br>	this.element.style.height = &#39;auto&#39;;<br>	this.element.style.height = this.element.scrollHeight + &#39;px&#39;;<br>}</pre><p>Yes, it’s that simple. Now let’s call see how we call the function in our Class and initialize it:</p><pre>/**<br> * Auto Resizing for Textarea Elements.<br> *<br> * This automatically resizes textarea elemens when the content gets<br> * longer than the initial height of the element to ease writing for users.<br> */<br>export default class TextareaAutoResize {<br>	constructor( element ) {<br>		this.element = element;<br>		this.element.addEventListener( &#39;input&#39;, this.textareaDidChange.bind( this ) );<br><br>		this.textareaDidChange();<br>	}<br><br>	/**<br>	 * Applies the scrollHeight to the element if content exceeds, otherwise &#39;auto&#39;.<br>	 */<br>	textareaDidChange() {<br>		this.element.style.height = &#39;auto&#39;;<br>		this.element.style.height = this.element.scrollHeight + &#39;px&#39;;<br>	}<br>}</pre><p>That’s all. There’s one little detail in there: We first add the Event Listener and then call the function once afterwards. We do this to ensure the height is set properly on load as well. Think about entering a lot of text and reload the browser window. With this additional call, the height is set properly in such cases as well.</p><p>You now only need to import your module in your entry point file and bind it to a set of DOM elements:</p><pre>import TextareaAutoResize from &quot;./TextareaAutoResize.js&quot;;<br><br>document.addEventListener(&#39;DOMContentLoaded&#39;, function() {<br>	const textareaElements = document.querySelectorAll(&#39;textarea&#39;);<br>	for (const textareaElement of textareaElements) {<br>		new TextareaAutoResize( textareaElement );<br>	}<br>});</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3362d12f63b9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colloq/auto-resizing-textareas-with-ecmascript-6-3362d12f63b9">Auto-Resizing Textareas with ECMAScript 6</a> was originally published in <a href="https://medium.com/colloq">Colloq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s New in July]]></title>
            <link>https://medium.com/colloq/whats-new-in-july-2c93fa4e5aaa?source=rss-695f9400a1da------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c93fa4e5aaa</guid>
            <dc:creator><![CDATA[Anselm Hannemann]]></dc:creator>
            <pubDate>Fri, 20 Jul 2018 10:09:18 GMT</pubDate>
            <atom:updated>2018-07-20T10:09:54.593Z</atom:updated>
            <content:encoded><![CDATA[<p>We continue to work on Colloq almost every day and currently focus on some bigger updates which require a good amount of planning first. We started work on one of them and a second one will hopefully follow right after. We’re sure you’ll love the things to come. But now for what we’ve done in the past weeks:</p><h4>Noti.st Support in Coverage</h4><p>We’re happy to say that from now on we’ll recognize links from <a href="https://noti.st/">noti.st</a> in our coverage and can display these links with some more details.</p><h4>Support Availability</h4><p>We added improvements to our contact form: We all work in different timezones and realized that it sometimes might take a little longer for one of us to reply. This can happen if there is a public holiday (of which Hong Kong has a few!) or over the weekend. We wanted to make sure to let our users know in advance when this might be the case.</p><h4>Detailed Changelog</h4><p>As per our usual manner, we have updated and fixed many small things, some of which some are visible while others happened in our backend. For the rather curious of you, here’s the complete list:</p><ul><li>We added a “is-today” color for today’s date in our non-native datepicker;</li><li>We’re now opening the code of conduct link in our CfP form in a new tab, because otherwise it could cause form input to be lost;</li><li>We improved error handling for event coverage links and are not showing links with errors anymore;</li><li>The event claim box didn’t look nice on smaller screens, hence we improved its responsiveness;</li><li>We fixed a bug where unpublished events could appear in the “speaking at” section of a user profile page;</li><li>The newsletter got a little touchup and is now better legible;</li><li>Organisers and event staff are now able to update and delete coverage links;</li><li>Our homepage now displays all of today’s events, whereas this section has previously been limited to only three events for some unknown reason;</li><li>When deleting an event room, we no longer delete the sessions in this room;</li><li>The autocomplete input field got a little overhaul and the error message now appears nicely and doesn’t cause a gap anymore;</li><li>The speakerdeck coverage details got a visual touchup;</li><li>Newsletter drafts could be publicly accessed in case the slug was known;</li><li>To be able to post external articles on our blog, we added the option to add a canonical tag;</li><li>We move the ticket ID from our support email from the body to the subject line, since it somehow received a little too much attention.</li></ul><p>Thanks for reading and we hope to see you again soon. Until then, why not have a look at some <a href="https://colloq.io/events/latest">new conferences</a> or the <a href="https://colloq.io/events/latest?callforpapers=open">latest Call for Papers</a>?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c93fa4e5aaa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colloq/whats-new-in-july-2c93fa4e5aaa">What’s New in July</a> was originally published in <a href="https://medium.com/colloq">Colloq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Built to Last]]></title>
            <link>https://medium.com/@helloanselm/built-to-last-2dc0ebc55d9a?source=rss-695f9400a1da------2</link>
            <guid isPermaLink="false">https://medium.com/p/2dc0ebc55d9a</guid>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[sustainability]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Anselm Hannemann]]></dc:creator>
            <pubDate>Tue, 26 Jun 2018 08:37:00 GMT</pubDate>
            <atom:updated>2018-06-26T08:49:14.406Z</atom:updated>
            <content:encoded><![CDATA[<p>Today I read an article called “<a href="https://m.signalvnoise.com/outlasting-4dff3fb6aca7"><strong>Outlasting</strong></a>” that I could relate very much with. It inspired me to write about <strong>building a long-lasting business</strong> and <strong>patience</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KdSew3KqxYelwOD8zXFOyg.jpeg" /></figure><blockquote>You in business? What are you doing to last? Not to grow. Not to gain. Not to take. Not to win. But to last? — Jason Fried in <a href="https://m.signalvnoise.com/outlasting-4dff3fb6aca7">Outlasting</a></blockquote><p>It describes the way I build software and websites since ever — building a thing that lasts for as long as I can imagine it to last.In the past, I related this to how I create a codebase so that it lasts for years and will be reliable and readable by other people when I’m not on that project anymore. These days I think about my own company — <a href="https://colloq.io/">Colloq</a>.</p><h4>Have a Vision</h4><p>Colloq is a project right to my heart. I’ve spent countless hours already on it and with Tobias and Holger I’ve created a platform for accessing events and event content in an easier way. When we made things official and talked about how we want to do business, we all imagined the service to be available for the next decades. We didn’t want to build something and sell it to the highest bidder but to build something that makes us happy to work on for the next years and pays our bills.</p><h4>On Competition</h4><p>We often get asked whether we’re a replacement for [Service X] and while such comparisons are good for people who don’t know us yet, our goal was never to copy and replace another service.</p><blockquote>I wouldn’t advocate spending much time worrying about the competition — you really shouldn’t waste attention worrying about things you can’t control — but if it helps make the point relatable, the best way to beat the competition is to last longer than they do. — Jason Fried in <a href="https://m.signalvnoise.com/outlasting-4dff3fb6aca7">Outlasting</a></blockquote><p>For Colloq, we have a vision about what it should be and how we want to create a sustainable, ethical business that lasts. I think it’s important to have your own vision if you want to be successful and build something that lasts for long.</p><h4>Patience</h4><p>One of the hard lessons you learn when you start an online business is <em>patience</em>. In times of smartphones with (virtual) assistants for nearly everything who can give you a mostly instant reply to your questions, we have a tough time to be patient.</p><p>Most of us constantly forget that some things need time. We forget that while going to the mountains, practicing meditation and yoga but struggle to not expect instant feedback. One of these things that take time is building a business. When I opened up my first business 11 years ago, things were different but it took me three years to get to a point where the business was really and sufficiently profitable. Building an online service with three people is even harder as we need to earn money for three and not only one persons. We also need to save some money for the company itself to keep it running.</p><p>Not having thousands of paying customers after merely 7 months of is just normal. Not even the considered “most successful” companies had that. Building reputation takes time and if you’re going the hard path and market your product with honesty and real facts takes even longer. Building a quality product is difficult — from planning over crafting it to market it to customers. We can understand why some hand-crafted tools like a <a href="https://www.japanesetools.com.au/products/copy-of-tasai-shinogi-nomi-6pcs-ebony-handles">Japanese wood chisel set of 6 chisels can easily cost thousands of Dollars</a>. It takes time to produce these things, it’s a limited production and the tools need to be of excellent quality.</p><h4>The Cost Factor</h4><p>Jason Fried writes about this adequately:</p><blockquote>Whenever a startup goes out of business, the first thing I get curious about are their costs, not their revenues. If their revenues are non-existent, or barely there, then they were fucked anyway. But beyond that, the first thing I look at is their employee count. Your startup with 38 people didn’t make it? No wonder. — Jason Fried in <a href="https://m.signalvnoise.com/outlasting-4dff3fb6aca7">Outlasting</a></blockquote><p>A few weeks ago I wrote a <a href="https://colloq.io/blog/saving-costs">Colloq blog post about saving costs</a> that explains how we saved $5 per month and become more sustainable again. People ask whether we would hire more people or why we don’t use [Service Y] for that but build our own tools; What often is neglected that if you don’t have large investment, you don’t have a choice about these decisions. We simply can’t afford hiring someone else because the fund currently only pay a bit more than our technical costs we have. Our goal is not to get rich but to pay ourselves a fair and reasonable wage for the next decades. In order to do that, we not only need to acquire users who find it worth paying for our service but also need to save money wherever we can. Building our own tools is not free (time) but doesn’t affect our account’s balance.</p><p><strong>Thanks </strong><a href="https://m.signalvnoise.com/@jasonfried"><strong>Jason</strong></a><strong> for the inspiring read where I could find so many things I have in my mind affirmed by someone who is successful following these rules.</strong></p><p><em>Have an event that could get promotion or need tools that aid you organizing it? Or want to find events to go to and get inspired by their coverage? All you need is </em><a href="https://colloq.io/account;create"><em>signing up for Colloq</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2dc0ebc55d9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Easily Change Your Colloq Newsletter Subscription]]></title>
            <link>https://medium.com/colloq/easily-change-your-colloq-newsletter-subscription-5b88f90f1efe?source=rss-695f9400a1da------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b88f90f1efe</guid>
            <category><![CDATA[startup-marketing]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[newsletter]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[event-planning]]></category>
            <dc:creator><![CDATA[Anselm Hannemann]]></dc:creator>
            <pubDate>Mon, 11 Jun 2018 13:56:33 GMT</pubDate>
            <atom:updated>2018-06-11T13:59:58.609Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://colloq.io/blog/service-announcement-emails-better-search-results">Just yesterday</a> we announced improvements to our email service and today we’d like to show you a new way to manage your newsletter subscription preferences in your Colloq account.</p><p>Our newsletter is available to everyone, including people who have no Colloq account. We now make it easier for our existing users to choose whether to receive the monthly writing or not. By default, you will not receive the newsletter as want to make it our users’ choice and not ours to read the content. And while we try our best to add value to the newsletters we can understand very well that a lot of users prefer to not get another email each month.</p><h4>Account Settings</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OVXCktetceD6G1e6gkXacA.png" /></figure><p>From now on you can manage your newsletter subscription settings in <a href="https://colloq.io/account/settings">your account settings</a>. It’s as easy to opt-out as to opt-in so if you change your mind, don’t worry — we’ll let you decide and won’t force you into anything.</p><h4>Newsletter Signup</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R4xf946ByI-U9m5AH7nIPA.jpeg" /></figure><p>We also improved the look and copy of the <a href="https://colloq.io/newsletter/subscriber">generic newsletter subscription page</a> people usually land on. Instead of only providing you a blank form, we now give you hints on what content you can expect before you subscribe to it. While at it, we revamped all the little individual action pages (confirm subscription, etc) and made them look consistent and much nicer than before.</p><p><em>Like what we do here? Give </em><a href="https://colloq.io/"><em>Colloq a try today</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b88f90f1efe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colloq/easily-change-your-colloq-newsletter-subscription-5b88f90f1efe">Easily Change Your Colloq Newsletter Subscription</a> was originally published in <a href="https://medium.com/colloq">Colloq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Service Announcement Emails & Better Search Results]]></title>
            <link>https://medium.com/colloq/service-announcement-emails-better-search-results-b03d691adf1b?source=rss-695f9400a1da------2</link>
            <guid isPermaLink="false">https://medium.com/p/b03d691adf1b</guid>
            <category><![CDATA[event-planning]]></category>
            <category><![CDATA[event-management]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[events]]></category>
            <dc:creator><![CDATA[Anselm Hannemann]]></dc:creator>
            <pubDate>Wed, 06 Jun 2018 14:24:29 GMT</pubDate>
            <atom:updated>2018-06-06T14:31:28.469Z</atom:updated>
            <content:encoded><![CDATA[<p>With the latest updates we improved the search result information and we are now able to send service announcements reliably to our users. This is serves as the foundation for more upcoming features.</p><h4>Better Search Results</h4><p>We received some feeback that our search results could reveal more useful information about events. We took this chance to improve the information we show as well as the layout. With this change, search results not only look nicer, but you can now easily see the event’s date, location, coverage availability and other information directly on the search results page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UDgJ5-jMxs7q3HNpPazo3g.png" /></figure><h4>Filter Events by “Open Call for Papers”</h4><p>We added our first filter to the event lists: You can now filter for events if they have an “Open Call for Papers” and it also updates the content asynchronously. We’ll continue building similar features and filters in the upcoming weeks and months based on the technical foundation we now have for this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l1tWP2iSLZ6GR4urSu-zIg.jpeg" /></figure><h4>Service Email Announcements</h4><p>Initially we decided to not have a programmatic way of sending important service-related emails to our users. This wasn’t necessary until now, but since we want to occasionally inform users about changes and updates, we’ve built a system that makes it easier for us to send such notices to our users. To implement this feature, we built a mail queue which allows us to send emails in batches and it took us a little longer than expected. On the positive side, this allows us to build several other features that require the queue on top of it.</p><p>These announcements are completely unrelated to our newsletter, which contains regular updates to our service, feature announcements, related articles for event organizers or similar content. <a href="https://colloq.io/newsletter/subscriber">You can subscribe to our newsletter here</a>.</p><h4>Changes and Updates</h4><ul><li>The height of the logo in our newsletter layout was incorrect and now displays as inteded</li><li>We improved the space of the initially visible viewport on our homepage. This makes it easier to access the search box on the homepage</li><li>Our recent refactoring to use CSS Grid on the event coverage page lead to some weirdly spaced links. We fixed these edge-cases and have a cleaner codebase than before</li><li>A recent upgrade of our modal dependency that introduced support for the native &lt;dialog&gt; element broke the dialogs. We fixed this issue and with that improved accessibility even further</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b03d691adf1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colloq/service-announcement-emails-better-search-results-b03d691adf1b">Service Announcement Emails &amp; Better Search Results</a> was originally published in <a href="https://medium.com/colloq">Colloq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>