profile
viewpoint

antpb/gutenberg-block-demo 1

This is the gutenberg block demo for a GB presentation. used create-guten-block to initialize the block/plugin

octalmage/wib 1

WordPress in Browser (powered by WebAssembly)

anthonyburchell/gutenberg 0

Printing since 1440. Development hub for the editor focus in core. Beta plugin is available from the official WordPress repository.

antpb/gutenberg 0

Printing since 1440. Development hub for the editor focus in core. Beta plugin is available from the official WordPress repository.

antpb/hubs 0

Duck-themed multi-user virtual spaces in WebVR. Built with A-Frame.

antpb/hubs-cloud 0

Resources for self hosted Hubs Cloud instances

antpb/OscCore 0

A performance-oriented OSC library for Unity

antpb/pib 0

PHP in Browser (powered by WebAssembly)

antpb/unity-webxr-export 0

Assets for creating WebXR-enabled Unity3D projects.

issue commentmozilla/hubs-cloud

Built in Google Analytics for HC isn't working.

I figured it out! It seems after you enter the ID in the admin panel you need to initiate a new deploy from local to build with the ID accounted for 🎉

after a fresh npm run deploy after setting the admin option, things were 100% working and tracking in GA

robin-k-wilson

comment created time in 21 days

issue commentmozilla/hubs-cloud

Built in Google Analytics for HC isn't working.

Hello! I have an event tomorrow and realized I have no tracking set up 😬 . I followed the steps above but it still does not look like it's working. I see in the source this message <!-- NOTE GA tracking is disabled by default. You'll need to set the GA_TRACKING_ID build variable to enable it.

Is this what is blocking it and is there any documentation on enabling that?

robin-k-wilson

comment created time in 21 days

issue commentmozilla/hubs-cloud

Changing Primary Domain locked admin out of instance

I know a fix in my case would be destroying the instance and making a new one, but I thought I would report this as I anticipate changing a primary domain to be a frequent task for some folks.

antpb

comment created time in a month

issue openedmozilla/hubs-cloud

Changing Primary Domain locked admin out of instance

Hello! I have a Hubs Cloud instance that I changed the primary domain for and now I'm locked out of login and cannot create rooms due to CORS errors that are referencing the previous primary domain.

Previously domain recipe looked like the following: primary: hubs.broken.place internal: brokenplace.com link: bpxr.link

The new configuration is the following: primary: hubs.xpportal.io internal: brokenplace.com link: bpxr.link

The stack update changing the domain/ssl worked great, and I was able to configure/validate SES properly. Worth noting, the instance had a custom client pushed prior to the primary domain change. The below error happens when creating a new room after a successful stack update that changes primary domain:

phoenix-utils.js:184 Refused to connect to 'https://hubs.broken.place/api/v1/hubs' because it violates the document's Content Security Policy. Notice the url referenced is the old one.

The login form no longer is sending the login email however, using the npm run login command from my custom client locally was able to send the login email which upon clicking, was met with a content security error. Here's a screenshot of the sign in link error:

Screen Shot 2020-09-18 at 12 47 49 AM

This feels related to what I suspect to be cleanup issues in https://github.com/mozilla/hubs-cloud/issues/107

created time in a month

issue commentmozilla/hubs-cloud

Content Security Policy seemingly absent from new instance

oh, worth noting this is also happening on hubs.mozilla.com/spoke :O

antpb

comment created time in 2 months

issue commentmozilla/hubs-cloud

Content Security Policy seemingly absent from new instance

In another self hosted instance I have access to I noticed that in Spoke the same errors are happening so this seems across all Hub Cloud instances. Existing content seems to be okay, it's just new content that is not working. Maybe the problem is Spoke side? The common issue seems to be the proxy domain not being able to resolve.

I've seen similar reports to this issue in https://github.com/mozilla/hubs/discussions/3017 and https://github.com/mozilla/hubs-cloud/issues/110

antpb

comment created time in 2 months

issue commentmozilla/hubs-cloud

Content Security Policy seemingly absent from new instance

You can reproduce the error most clearly by going to https://hubs.broken.place/spoke and making a new scene. When you've reached the new scene, add a video element and use a youtube/vimdeo url and you'll notice that videonode fails.

antpb

comment created time in 2 months

issue commentmozilla/hubs-cloud

Content Security Policy seemingly absent from new instance

Last night I deleted the stack, removed all rogue DNS records, then made a new stack. Still seeing the same issues. The example url is now 1:1 with what deploys from an initial stack creation.

antpb

comment created time in 2 months

issue commentmozilla/hubs-cloud

Content Security Policy seemingly absent from new instance

I notice that my internal domain is not in the new stacks Cors params. Should it be? Here’s what it looks like currently

CorsOrigins https://hubs.broken.place,https://bpxr.link,https://hubs.local:8080,https://localhost:8080
antpb

comment created time in 2 months

issue openedmozilla/hubs-cloud

Content Security Policy seemingly absent from new instance

From https://github.com/mozilla/hubs/discussions/2994

After changing the admin settings for content-src and script-src I am seeing CORS errors even after deleting an instance and creating a fresh new one.

Example error below:

Refused to prefetch content from 'https://bp-hubs-main-assets.brokenplace.com/spoke/assets/js/vendors~package-kit-page~project-page-f6be3132b65e15548183.js' because it violates the following Content Security Policy directive: "default-src 'none'". Note that 'prefetch-src' was not explicitly set, so 'default-src' is used as a fallback.

Also from the discussion, prior to a fresh instance, I was seeing

Content Security Policy: The page’s settings blocked the loading of a resource at https://bp-hubs-assets.<internaldomain>.com/...

You can see the error in Spoke or in a room at the following Hubs Cloud instance: https://hubs.broken.place

created time in 2 months

more