How can I hotlink an mp3 in Google Drive with a URL ending in .mp3?

I would like to obtain a link to an mp3 hosted in Google Drive that has the format filename.mp3, so I can link to it from sites that provide in-line audio players when linking to mp3 files.

I have searched the web and different SE sites, but the closest thing to a solution I have found is obtaining a direct download link for the file or advice on hosting it elsewhere. However, for (future) convenience I would prefer to host and link directly from / to Google Drive.

Can anyone provide some insight or point out why this might not work?

Can a bulette ignore the rule about ending a turn in occupied space after using deadly leap?

The bulette can use it’s deadly leap ability to jump onto it’s targets and possibly knock them prone if they fail their saving throw. But having done so it will be sharing the same space as them. The rules state you can’t willingly end your turn in the same space as another creature but I can’t see a good reason why a bulette would try to move away assuming they still have movement left.

Question: WordPress URL estensions ending with “/” or “.php”?


I am planning to move an offline .PHP static site to WordPress. I will do my best to keep my old .php URLs, but… a problem has arisen:

What extensions are WordPress pages? .PHP?

Because most of the time when browsing blogs, I see no extension, but merely "/" at the end of the URL.

Example – my current static .PHP pages look like this:

But blogs, which I read all lack the .php/.htm extension:


Question: WordPress URL estensions ending with "/" or ".php"?

Post URL ending with feed

I am getting report from Moz under “Top Pages On This Site”‎category/home-decor/feed/‎‎category/pest-control/feed/‎‎best-pest-control-tips/feed/‎

What does it mean? Why I am getting this? Should I do something on this? If so, what to do?

I am technically zero.

Scrub The Web ending by June 18, 2017

Feel sorry and sad to see getting close one more search engine

You can view this message on Scrub The Web:
Announcement! After more than 21 years on-line, Scrub The Web will officially shut down on June 18, 2017.
All gone: DMOZ Directory, Yahoo Directory, Alltheweb, Altavista, and now ScrubTheWeb.

Who do you think is to blame social media and phone app where people don't search for the resource anymore or those search engines and directories…

Scrub The Web ending by June 18, 2017

Ending up with too many services in DDD

I’m working on a project at the moment and I’m using this project to try and apply DDD. However, there are parts of my implementation that I just can’t get my head around or don’t feel right. I’ll try to describe how I currently have my application setup;

In my domain layer, I have my aggregates, value objects and a service class for each bounded context. As an example, I have a bounded context ‘Account’ with the following;

Account – account aggregate root

Profile – value object

EmailAddress – value object

AccountValidator – validates an accounts state

ProfileValidator – validates a profiles state

AccountRepository – interface describing the methods available on the repository

AccountService – at the minute this has a single method createNewAccount(), it accepts a number of primitive values and creates the account and returns it. Before creating the account it first checks to make sure the selected username doesn’t already exist. If the username exists, it throws an Exception. (Should this rule be in the domain service?)

In my application layer I have;

AccountRepositoryImp – an implementation of the accountRepository in the domain class, this is a standard Spring Data interface that implements accountRepository.

AccountFacade – basically, another account service that provides methods such as findById(), findByUsername(), createNewAccount(), sendVerificationEmail(), verifyAccount.

AccountController – standard Spring controller that handles all account related actions

I have a number of questions/issues with my approach;

  1. I have two service classes for each bounded content, one for the domain and one for the application, and while I understand the domain service class should be used only to apply behaviour or business rules that can’t be done on the aggregate itself (i.e. need db access), I’m struggling to determine what’s an application rule and what’s a business rule. For example, an account cannot be created if the username is already in use, I’ve put this in my domain service, but I’m starting to wonder if it should belong in the createNewAccount() method in the application service. Another rule, “An account can only be deleted by an admin or the account hold themselves”, is this application or business?
  2. As I add more and more methods to my application service, it’s going to grow pretty big. This leads me to thinking about implementing CQRS and having a class/method for each command/query. This breaks things down and makes it easier to manage, but I can’t help but feel this will bring a lot of duplication to it. For example, In the AccountRepository I can retrieve an account by it’s username, and if the account doesn’t exist it returns null. Rather than returning null, I wrote a getByUsername() method in the application service so that it throws an exception if the account doesn’t exist, rather than a null. This means I can use this method from other methods and I don’t need to duplicate throwing the exception. I feel like if I use CQRS, I’m still going to have to keep the application service so it can hold methods that are used by multiple commands/queries to reduce duplicate. I’ll end up with yet another layer controller -> command/query -> applicationservice -> domainservice it feels like I’m making the application more complicated than it needs to be
  3. If I use CQRS, is the command/query or controller responsible for building ViewModels? I’m inclined to thing the command/query can build them, as they’ll be use case based and can be re-used if I was to add REST endpoints to the system in the future. If I allowed the controller to make multiple command/queries and build the ViewModel, then if I implement REST at a later date, I’ll have to duplicate that code.
  4. Rules – as mentioned above I’m struggling to assign rules to the application or domain. I’ll list a few rules below and if I could have some pointer on where they might belong, it would be useful to train my brain;

    • An account cannot be created without an email, username, firstname and lastname (I’ve put this on the domain)
    • An account cannot be created if the username is in use (I’ve put it on the domain)
    • A user cannot comment on a project if they are not a project member.
    • A comment cannot be left on a closed project
    • Only the project owner can edit/manage/administer the project

I do apologise if this question is a little unstructured and my thoughts do appear a bit random. I’ve been so used to using an anemic model that I’ve got so many thoughts in my head that I can’t structure (hence the question).