[dave9527]

Right can't answer a single PM I have just gotten married and I will be on my hooneymoon from tonight onwards.

My sincerest apologies for any unanswered messages once I'm back I will do my best to update you all on what's happening.

Congratulations

 

[Ahmad313]

Right can't answer a single PM I have just gotten married and I will be on my hooneymoon from tonight onwards.

My sincerest apologies for any unanswered messages once I'm back I will do my best to update you all on what's happening.

Congratulations

 

[lbritish]

This should settle the question of Trinity vs IMR


Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\lbritish>ping trinityaudioengineering.com

Pinging trinityaudioengineering.com [23.227.38.32] with 32 bytes of data:
Reply from 23.227.38.32: bytes=32 time=70ms TTL=50
Reply from 23.227.38.32: bytes=32 time=63ms TTL=50
Reply from 23.227.38.32: bytes=32 time=64ms TTL=50
Reply from 23.227.38.32: bytes=32 time=64ms TTL=50

Ping statistics for 23.227.38.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 70ms, Average = 65ms

C:\Users\lbritish>ping imracoustics.com

Pinging imracoustics.com [23.227.38.32] with 32 bytes of data:
Reply from 23.227.38.32: bytes=32 time=70ms TTL=50
Reply from 23.227.38.32: bytes=32 time=61ms TTL=50
Reply from 23.227.38.32: bytes=32 time=68ms TTL=50
Reply from 23.227.38.32: bytes=32 time=63ms TTL=50

Ping statistics for 23.227.38.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 70ms, Average = 65ms

C:\Users\lbritish>

 

[Jackpot77]

This should settle the question of Trinity vs IMR


Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\lbritish>ping trinityaudioengineering.com

Pinging trinityaudioengineering.com [23.227.38.32] with 32 bytes of data:
Reply from 23.227.38.32: bytes=32 time=70ms TTL=50
Reply from 23.227.38.32: bytes=32 time=63ms TTL=50
Reply from 23.227.38.32: bytes=32 time=64ms TTL=50
Reply from 23.227.38.32: bytes=32 time=64ms TTL=50

Ping statistics for 23.227.38.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 70ms, Average = 65ms

C:\Users\lbritish>ping imracoustics.com

Pinging imracoustics.com [23.227.38.32] with 32 bytes of data:
Reply from 23.227.38.32: bytes=32 time=70ms TTL=50
Reply from 23.227.38.32: bytes=32 time=61ms TTL=50
Reply from 23.227.38.32: bytes=32 time=68ms TTL=50
Reply from 23.227.38.32: bytes=32 time=63ms TTL=50

Ping statistics for 23.227.38.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 70ms, Average = 65ms

C:\Users\lbritish>

Can you translate for those of us who don't work in IT?

 

[Midgetguy]

Can you translate for those of us who don't work in IT?

Point being that both web pages are hosted from the same server.

To play devil's advocate:
It could be that the server was initially Bob's and since IMR is supposed to be his own venture, it's hosted there. Trinity's site is hosted there because it also originated there; resource usage hoo-ha from the old days. It could also be that Bob is leasing server resources from Trinity Audio; even though he doesn't seem to want to deal with them anymore, he could've have negotiated a good deal through some sort of severance contract.

I'm not denying what the information IS, but given that there are various possibilities due to not knowing every single fact of the situation, I also don't want to jump to saying that there's only a single explanation.

 

[lbritish]

they (IMR and Trinity) both run on the same IP address.... an IP Address is basically the server it is running on. Some servers have more than one IP address but typically if you find more than one domain name running on the same IP address they are thus on the same server. In this case it does resolve as an address owned by shopify BUT.... shopify has over 8000 IP addresses they control. If I sign up for a shopify account today it's not going to resolve to this IP address. It will be randomly distributed to one of the other IP addresses on another server somewhere. However... if I have an existing Shopify account and I want to add another domain name on to my account what happens? They add it to the server the rest of my domains run on so that the control panel for it has all the sales consolidated in one place....so if I spring up a new subsidiary business because my old one has been totally destroyed PR-wise I can just roll it over to a new name and eventually shutdown the old name on the same account run by the parent business.

While this is not 100% guaranteed it's more like 99% unlikely to be a coincidence that Bob would start up a brand new company using Shopify and manage to be placed on the EXACT SAME SERVER his old employer runs on on Shopify when the old employer's account was created YEARS ago and according to the WHOIS details SOMEONE registered IMR on 2017-07-30. Trinity was created 2014-12-02 and it was last changed 2015-11-02 which probably happened when they moved their website to Shopify.

 

[filltos]

I second, I will be having a pair of Vyrus coming in this week from a fellow member

You mean Vyrus V1 coming? Can you post comparison between Vyrus V1 and V2?

 

[dave9527]

This should settle the question of Trinity vs IMR


Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\lbritish>ping trinityaudioengineering.com

Pinging trinityaudioengineering.com [23.227.38.32] with 32 bytes of data:
Reply from 23.227.38.32: bytes=32 time=70ms TTL=50
Reply from 23.227.38.32: bytes=32 time=63ms TTL=50
Reply from 23.227.38.32: bytes=32 time=64ms TTL=50
Reply from 23.227.38.32: bytes=32 time=64ms TTL=50

Ping statistics for 23.227.38.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 70ms, Average = 65ms

C:\Users\lbritish>ping imracoustics.com

Pinging imracoustics.com [23.227.38.32] with 32 bytes of data:
Reply from 23.227.38.32: bytes=32 time=70ms TTL=50
Reply from 23.227.38.32: bytes=32 time=61ms TTL=50
Reply from 23.227.38.32: bytes=32 time=68ms TTL=50
Reply from 23.227.38.32: bytes=32 time=63ms TTL=50

Ping statistics for 23.227.38.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 70ms, Average = 65ms

C:\Users\lbritish>

Interesting

 

[pazuzus_soup]

Anyone waiting on the Icarus I?

Has there been much news on it's production at all?

 

[paugustin]

I am waiting on Icarus I as well but I've not seen any news or even update on the specs.

 

[pazuzus_soup]

Thanks @paugustin - I realised I hadn't heard much about it since I pre-ordered, and was thinking maybe I missed some major update, or notice of it's halted production

 

[OldDude04]

The paranoia might be getting to some, they are just both using Shopify, as are many other sites, lol.





Details for 23.227.38.32
IP: 23.227.38.32
Decimal: 400762400
Hostname: 23.227.38.32
ASN: 62679
ISP: Shopify
Organization: Shopify
Services: None detected
Type: Corporate
Assignment: Static IP
Blacklist:
Continent: North America
Country: Canada

State/Region: Ontario
City: Ottawa
Latitude: 45.4166 (45° 24′ 59.76″ N)
Longitude: -75.6904 (75° 41′ 25.44″ W)
Postal Code: K2P

 

[dave9527]

Thanks @paugustin - I realised I hadn't heard much about it since I pre-ordered, and was thinking maybe I missed some major update, or notice of it's halted production

The mysterious Icarus I

 

[fpessolano]

Guys let it be, pray for delivery and decide for yourself if you want to risk 500 quids or not.

 

[Martin Howell]

Anyone waiting on the Icarus I?

Has there been much news on it's production at all?

I'm waiting on the Icarus I like you. Also waiting on the updated Air (thankfully I've received everything else I've ordered). I'm just sat here waiting, resigned to it turning up when it turns up.