I have recently pushed out a small update to my Profanity Detector C# / .NET Library. There are no functionality changes, but I renamed some of the functionality in the library. A central feature was the ability to add words to a ‘white-list’ if you want them excluded from the main list of profanities. With the recent Black Lives Matters protests, there has been a push to remove any language from software that could cause any racial offence.
The term white-listing and black-listing is a common idiom used in software development, but the naming could be better, such as block-lists and allow-lists. In the profanity detector library, I have renamed the ‘white-list’ feature and associated documentation to ‘Allow Lists’. Nothing has functionally changed, but if you update to the latest NuGet package, you may need to update any class name references from WhiteList to AlowList.
I have also updated the branch in GitHub that the code lived in from ‘master’ to ‘main’ as I discussed in my tutorial on branch renaming in GitHub. Thank you to all the people who use the Profanity Detector in their systems. I hope you continue to get good use from the library.
In my previous article, I talked about a simple profanity detector that I opened sourced on GitHub. Since launching that code example I have had a lot of people get in touch with some suggestions for new features as they wanted to make use of the library. There were some really good suggestions, so I have implemented them all. In this post, I will walk through what was requested and what I have added to the library.
Using the Library via Nuget
The first suggestion was to have NuGet support for the library as some people don’t want to clone repositories and deal with the source directly, so I have made the compiled Profanity Detector library available.
You can include the library directly from your package manager in Visual Studio, Visual Studio for Mac, VS Core, or Rider. The documentation for using the library is available on the Profanity Detector GitHub page.
Since writing this post, I have had many great feature suggestions for the Profanity Detector. I have implemented all the suggestions I have received and written another blog post about it. You can read the 2nd post here.
On several projects that I have worked on, we have had a requirement to detect profanity in users input. This includes things like general swear words, sexual acts, racial slurs, and sexist slurs, etc. Over the years, I have built a pretty comprehensive list of these profanities used for the detection process. The list has been built from combining lists I found on the internet. The lists are allegedly used by a lot of the large social networks in their profanity detection; although I can’t verify that.
My profanity detector is on GitHub, and released under an MIT license, so it is free for anyone to use and modify. The main list of profanities can be found in the ProfanityList.cs file. If you are easily offended and a bit sensitive to language then I recommend you DO NOT open that file. It contains some pretty gross language, but to detect the language, you need to be able to define it.
I have been very busy recently making new courses for Pluralsight and I am delighted to say I have just released two of them over the past week. The first course is called, Executive Briefing: State of Blockchain. This couse is a little different to the normal content on Pluralsight in that it is a short filmed course as opposed to screen casts and demos.
The idea of this course is to teach information to tech leaders and C level execs quickly as they won’t normally have time to sit and watch long courses. My course is all about blockchain where I talk about what it is, why you would need it, potential use cases. I also run through a matrix of questions about whether a blockchai is suitable for your company and the key differences between a blockchain and a database.
This course was good fun to produce as I had to setup all the lighting and camera myself aswell as record good audio. This is much harder than you think with getting the lighting right to reduce glare from the computer screen and my glasses. I am really pleased with the results though.
Asynchronous Messaging with RabbitMQ and EasyNetQ
The second course I have released this week is a more traditional Pluralsight course called, Asynchronous Messaging with RabbitMQ and EasyNetQ. This course is about the RabbitMQ messaging platform and how to use it with the EasyNetQ client library. The course is aimed at C# developers using .NET Core or the .NET Framework, and it will get them up and running and productive very quickly as it is very demo focused.
This course works as a great companion to my other course, RabbitMQ by Example, which builds up the same sample application scenario but using the much more complicated RabbitMQ client library. If you want to compare the default client library to the EasyNetQ client library, then both courses will give you that information. If you just want to make your life easier and go straight to EasyNetQ, then this course contains everything you need.
Back in August, I had the pleasure of speaking at NDC Sydney, which I wrote about in a previous post. The videos of those talks are now both available and shown below. The first in my .NET Data Security talk about cryptography and the 2nd video is my social engineering talk.
I have been nice and busy since leaving Buying Butler and RightIndem. Along with my co-founder, we are setting up a new FinTech startup called Ladder Pay. LadderPay is an innovative payment platform that unifies Business to Business, Business to Consumer, and Consumer to Business payments into one product with an emphasis on security and compliance backed by blockchain technology. I can’t write too much about it just yet as we are still working through a lot of details, but I am very excited about it. We have 3 potential customers who will use the platform first, so we are getting things ready for that.
My main role at the moment has been developing the backend platform so I have been spending most of my time coding, which has been really nice to get back into full-time. The product is being developed in Microsofts .NET Core 2 platform and deployed onto Microsoft Azure. I will write more about this in the future, it’s a little too early to reveal too much at the moment.
I am mostly working from home on this at the moment, but we are looking for an office to work from. We have found a place we like, but are still sorting through the details. I always found working from home difficult, but since working on LadderPay, I have set up in my dining room and have a really nice setup which is nice on a sunny day as I can open the doors to the garden, so I am really enjoying this at the moment.
Whilst I am doing LadderPay during the day, I am also continuing on my Pluralsight courses in the evening. I have signed up for a new course that is all about the algorithms that are used to build up blockchain. A challenging but very interesting course. I can’t wait to share more details.
Over the last week we have been working on something quite exciting. At BuyingButler and RightIndem we pride ourselves on being a very technology focused company, and we love looking to see where we can use the latest technology to solve real problems. We have been doing just that with Microsoft new HoloLens Mixed Reality headset.
On Thursday 12th Jan 2017 we had a good friend and fellow Pluralsight author Lars Klint fly over to the UK for the NDC London conference. Before the conference he came up to Nottingham for a couple of days to work with us around some use cases for the Hololens for RightIndem. I can’t discuss what those use cases are at the moment openly, but they are quite exciting and complement one of our project modules nicely.
If you would like Lars to run a workshop for your company, you can see the details on his workshops page. I highly recommend him for the Hololens workshop or his Winning at Life workshop.
Microsoft HoloLens is the first self-contained, holographic computer, enabling you to engage with your digital content and interact with holograms in the world around you.
When wearing the headset, you still have an unrestricted view of your surroundings, but you also see holograms that are placed in the room that you can only see with the HoloLens attached. These holograms are aware of their surroundings and can be placed on walls and tables. This is achieved by the HoloLens doing spatial mapping of the environment around it. You can then interact with these holograms directly whilst walking around your environment.
The HoloLens is a Windows 10 device which is untethered, which means you do not need a cable running between the headset and a powerful computer like you do with a Virtual Reality headset like the Oculus Rift.
With Lars visiting our offices we had 2 goals to achieve over 2 days. On the first day Lars facilitated a brain storming session with myself and the rest of the companies management team. We already had some ideas of where the HoloLens could be applied, but the purpose of this session was to work through different ideas and walk away with a rough plan for a series of minimum viable products we could build. This session went very well, and everyone involved had the opportunity to try the HoloLens for a good amount of time. This was important as people need to understand what the experience feels like in order to understand the constraints posed. Off the back of the session we have an idea for 2 technical spikes we want to try and a prototype product to build with it. The cool thing is, we already have a company we are talking too about partnering with us to deliver a HoloLens solution.
The Video recording of my talk at NDC London is now available to watch on-line. This was my first major conference so it was a little scary, but I really enjoyed the experience. The room was about 2 thirds full and I got an excellent speaker rating at the end so I must have done something right.
Now that we have covered a lot of the introductory material for RabbitMQ, this part of the series will look at developing software to interact with the message broker as both a producer and a consumer. First we will take a look at the RabbitMQ client library. Then we will introduce the business scenario used for the sample applications. Before we start looking at the individual examples we will take a quick look at the common code shared between them. Then we will move onto the actual code examples themselves.
To develop software against RabbitMQ you will need to install the RabbitMQ client library for .NET. Before we look at how to install the client library, let’s take a brief look at what it is. This series will not serve as an in-depth guide to the whole client library API. You can read a more in-depth document for the client library that explains the full library from the RabbitMQ site. This section will serve as an introduction to the library and the examples in the rest of this series will help you cement your understanding further.
What is contained in the Client Library?
The RabbitMQ .NET client is an implementation of an AMQP client library for C# and other .NET languages. The client library implements the AMQP specification 0-8 and 0-9. The API is closely modeled on the AMQP protocol specification with little additional abstraction, so if you have a good understanding of the AMQP protocol, then you will find the client library easy to follow.
The core API interfaces and classes are defined in the RabbitMQ.Client namespace. The main API interfaces and classes are:
IModel : This represents an AMQP data channel and provides most of the AMQP operations.