Tag Archives: status

Weekly roundup: GLEAM

Post Syndicated from Eevee original https://eev.ee/dev/2019/08/04/weekly-roundup-gleam/

Hello. I don’t know how I am! But I did some stuff.

  • fox flux: Workin’ on a new walk animation.

  • gleam: After years of saying I should totally do so, I finally started making a little editor for the Floraverse web VN engine. I’ve been gradually teaching it to load and play back the existing VNs (from scratch, because the old code is Quite Bad), and it’s finally hitting the point where it’s possible to make something from scratch. Sort of. I mean, there’s no saving or loading or exporting, and a bunch of stuff is broken, but you know. Getting there. Maybe I’ll even make a VN myself.

  • art: I started doing daily comics again and then forgot after day 1.

GLEAM has basically taken up my whole week; turns out that while client-side web stuff has improved dramatically, writing an editor is still an incredible pain in the ass. Getting somewhere, though.

Oh, and that marks the end of my journal! Cool, I guess. I don’t tend to fill up notebooks very often.

Weekly roundup: Recharging

Post Syndicated from Eevee original https://eev.ee/dev/2019/07/28/weekly-roundup-recharging/

Hello. I’m kinda up and down but recovering, I think.

  • art: I drew a bunch of porn, most of which is on my porn gallery (warning: porn). I even wrote some stuff, which will never see the light of day.

    I also finished putting all my 2015 art on my clean gallery, if you want to see the arc of my art journey, which slowed considerably after the first couple years. Kinda bummed about that.

  • irl: We have done so many fucking errands you have no idea.

  • gleam: I put together another Floraverse VN, but more importantly (to me anyway?), I’ve actually made some inroads on making a little editor for these things. It’s not entirely functional yet — did you know that drag-and-drop is a huge pain in the ass — but it resembles something and I’m making swift progress. Hallelujah.

  • fox flux: I gathered up like a dozen pages of dense notes and kinda consolidated them into one place, which is nice.

    I also, accidentally, uh, okay funny story, I was taking notes on paper and I doodled Lexy pulling a lever, and later I tried to sprite it based on her current sprite, and I didn’t like it a lot, so I pixel-traced over the drawing instead, and it was way better, and this led me on a journey that ended up with a completely different sprite design. It’s a thousand times better in every possible way, but I’ve also invented a massive pile of work for myself, because now I have to redesign a dozen variants of her and redraw like 200 sprite frames. It kind of feels like I’m back to square one and have accomplished nothing at all on this game, in fact! But fuck me it’s so much better

Next week marks a fun milestone. I’m now on the very last page of the book I’ve been using to jot this stuff down, one week per page. It spans almost four years. I should probably find another one real quick.

Weekly roundup: Vacay

Post Syndicated from Eevee original https://eev.ee/dev/2019/07/16/weekly-roundup-vacay/

I’m burnt out. I just can’t get into anything. And I’ve been dealing with a huge stack of accumulated errands from last month. And it’s fucking hot in here and that just pisses me off all the time???

So I’m trying to step back and chill and draw and hang out with folks and whatever. Sorry. I don’t know why I’m apologizing.

  • fox flux: Added some sparkles to a key.

  • mario maker: Made Star Anise’s Dream Land (5TQJG0MNG), a happy-go-lucky level inspired by my cat, and Koopa Valley (463-9CJPVG), an attempt at some standard friendly SMW-like fare. Also made half of like six other levels, but I’m having trouble even finishing those.

  • art: I’ve been drawing, just, a bunch of porn. It’s nice to be getting back into that. Drawing, I mean, not porn. But porn too.

See you next week.

Weekly roundup: Let’s try that again

Post Syndicated from Eevee original https://eev.ee/dev/2019/07/02/weekly-roundup-lets-try-that-again/

Hello, hello! It’s been a while. June ended up being an avalanche of errands and personal problems that neatly segued into each other, over and over. Good times! I think everything’s settled down now, but who knows.

Anyway, that gives us three weeks to catch up on:

  • fox flux: Finished and committed a bunch of half-implemented ideas in an attempt to get git clean for once (still more to go though); took a crack at porting sound effects from MilkyTracker and sfxr to Sunvox, which was much harder than expected; experimented with a nighttime palette; drew some new vastly improved swimming sprites from scratch.

    Did some work on the camera, which has always been pretty lazy. (I’ve improved it a lot since that recording, so don’t judge it too harshly.) Started on a redone menu, which should be a great improvement over the demo’s menu which was just “resume” and “quit”. Redrew the base dialogue portraits, and they look fantastic, but apparently I never tweeted about that, but you can see it in the next link!

    After spending all this time on miscellaneous mechanics and other bits and pieces, I decided it was finally time to get a basic gameplay loop going — enter a level, get some stuff, leave the level. The results are extremely rough, but I’ve made a start! It’s turning into a game! Which is weird because it was already a game once!

  • secret game engine thing: Not a lot, but I’ve cleared some design roadblocks that were seriously getting in the way.

  • art: Some doodles. Also I drew some beautiful gift art for my and Ash’s Metapodth anniversary.

  • alice’s day off: Wrote some stuff! It’s a miracle.

Currently attempting to get my ass back in gear, with moderate success.

Weekly roundup: Ironically stable

Post Syndicated from Eevee original https://eev.ee/dev/2019/06/12/weekly-roundup-ironically-stable/

I remain on a fox flux kick. Keep trying to do other stuff as well and then not doing that? Hm.

  • fox flux: Documented the hell out of all my rewritten collision code, removed some old hacks, put some methods on a new type that was an ad-hoc table before, and fixed a final remaining edge case in a satisfying way. Did kinda start writing about all this but didn’t finish it yet.

    Then I fixed all the stuff I’d broken about pushing in the process, and cleaned it up somewhat.

    Water is gradually improving but still kinda rough.

    Also added some experimental candy? Candy is pretty good.

    I did some more overhauling of the palette; I’m really really liking how it’s coming out.

    And also a preposterous amount of brainstorming. Like I’ve got half a dozen sheets of paper with tiny 8pt notes crammed on them. This ought to be a fun game.

Welp, back to that, then.

Weekly roundup: Exactly at the top

Post Syndicated from Eevee original https://eev.ee/dev/2019/06/05/weekly-roundup-exactly-at-the-top/

Hello! I’ve been a little preoccupied with meatspace things again, but here is some digital stuff.

  • fox flux: I have been a busy little beaver. I consolidated 1D and 2D motion, made ground adherence more conservative about how far it tries to drop you, and totally overhauled climbing to not incredibly suck. But who cares about any of that.

    What I really did is spend like a solid week overhauling collision detection. Finally, after years of wanting it, I have overlap resolution and nearly zero-cost contact detection! Which means that if objects overlap by some horrible twist of fate, instead of freely clipping through each other, they’re now free to move apart but not closer together. It’s god damn magic. Also I now know exactly where you’re touching objects which will probably come in handy for like, critters that walk back and forth on a platform without walking off it? Or something? I forget exactly why I wanted that but hey it’s nice.

    As an added bonus, I can finally fix climbing off the top of ladders — instead of hopping off the top and then landing, you stop at exactly the top, which is incredibly satisfying.

    I will almost certainly be wringing a blog post out of all this.

  • art: I worked more on that animation and then kinda forgot about it. Hm. Also some doodling or whatever?

    I drew a little… comic? Series of panels? I drew a thing about a ground adherence bug I ran into, and also a general explanation of ground adherence. It’s on Twitter, though it seems worth preserving elsewhere, once I figure out where that is.

  • gleam: I finally made some kind of real start on an editor for the little Flora VNs I put together. It doesn’t do a lot yet, but it has some UI, which is backwards from how I usually make these things, so that’s promising.

  • stream: Ash streamed some Spyro while I commentated, and then I streamed some Hat in Time while they commentated, and that was all great.

I am juggling too many things but I extremely want to get them all moving so I guess I’ll get back to it!

Weekly roundup: Pushing it

Post Syndicated from Eevee original https://eev.ee/dev/2019/05/15/weekly-roundup-pushing-it/

I remember saying something about balancing my time better, and that did not happen.

  • fox flux: I basically spent the whole week working on push physics. It was tough going at first, but I finally got it working correctly which feels like a goddamn Christmas miracle.

    I probably did some sprite work in there somewhere too, to let my brain cool down a bit.

    I’m excited about this game, ah! There’s a ton of work to go but I’m actually starting to see some mechanics come together.

  • stream: Ash and I played a ridiculous adventure game for a bit. Hm, maybe we should finish that. It’ll be on YouTube, uh, eventually.

Not so much this week; I ended up nocturnal and that threw me entirely for a loop. Back to waking with the sun now and feeling pretty good, so, fingers crossed.

Weekly roundup: In flux 2

Post Syndicated from Eevee original https://eev.ee/dev/2019/05/05/weekly-roundup-in-flux-2/

  • fox flux: I’m not sure what happened but I mostly did fox flux this week! It’s kind of a huge mess at the moment — I have a thousand lines of uncommitted changes from a dozen different half-finished experimental ideas, which makes starting on a new idea a bit daunting. So I spent some time finishing up and committing about half of that stuff, and then… um… started a few new half-finished experimental ideas. I am good at software development.

    I got a bit lost in the weeds trying to make the physics of pushing blocks work a bit better, which I’d still like to do, but I think it might require completely rethinking how pushing works (mainly in order to avoid a two-pixel gap in some situations, sigh, but that kinda thing’s important to me) and also redoing how friction and whatnot works. I can’t wait.

    Also been finishing up some visual effects I started ages ago but didn’t quite figure out, filling in some missing pixel art (which I think I got a little better + faster at), and fleshing out mechanics + trying out some new ones. It turns out, if you think your game needs more mechanics, a good place to start is to implement the existing ones so you can run around and play with them freely and see what new stuff comes to mind. Who knew?

  • art: I painted a picture. Not porn, for once! I’m definitely gonna do this more often; it was quicker and easier than I expected, and came out better too.

I missed working on fox flux and am glad to be doing it again, but I’ve clearly gotta balance my time across other stuff a bit better, too.

Weekly roundup: Bit of this, bit of that

Post Syndicated from Eevee original https://eev.ee/dev/2019/04/29/weekly-roundup-bit-of-this-bit-of-that/

I don’t have a cool theme or pun this week!

  • irl: I did a whole bunch of errands, aggressively slashed my tab/email count, and went hiking. Very exciting for you, I know.

  • secret thing: I taught it to animate tiles and movement, and tried this out with a conveyor belt, which instantly threw a wrench in my whole plan. Hm, well, I’ll figure it out. I wrote about the concept for $4 patrons (who will also be getting a bunch of beta builds when this is usable), if you’re interested.

  • cherry kisses: I have like four logic bugs reported by several different people, and they all feel related, but they’re also completely impossible. Like there is no way any of these could’ve happened. Except they did. And I have no goddamn idea how. I’ve spent like a day and a half wrestling with this and have barely made progress so far, but I would really like to make the game not randomly crash for folks.

    At least it autosaves, I guess.

  • art: I drew more things and I increasingly like them! I don’t know what happened, but I hit a point where I’m aggressively attacking all kinds of small details that I don’t do quite right — details that, formerly, I’d just glaze over because it was hard enough getting the general pose right. So that’s good.

    Still working on categorizing old SFW art, too. There’s just a whole lot of it.

  • fox flux: I picked this back up, but didn’t actually make tangible progress until Sunday, but I’m listing it anyway to pad this list out a bit.

  • streaming: Ash played through Doom II totally blind, while I provided commentary, which I guess doesn’t make it totally blind. Anyway we have a whole playlist of this nonsense now.

I’m juggling half a dozen things and am generally excited about all of them! It’s a nice way to feel.

Weekly roundup: Back to normal

Post Syndicated from Eevee original https://eev.ee/dev/2019/04/22/weekly-roundup-back-to-normal/

As I said before, I was occupied for a bit, but now I should finally be able to get back to doing these weekly! I did manage to get a few things done over the past three weeks:

  • flora: Finished up and published a Luneko species sheet! Happy April Fool.

    That’s Anise. Anise is the April fool, and also he’s happy.

  • blog: I wrote about how the particle wipe generator works, in lurid detail! I think it’s an interesting little read, even if you have no use for the tool itself.

    I also spent a lot of time backfilling old art on my (clean) art gallery. It’s not updated quite yet; there’s a lot to go to, shockingly so, and I haven’t even made it through year one yet. Honestly, I’m kind of embarrassed by how much my output declined over time.

  • art: Speaking of, I’m back to drawing regularly, instead of just saying I wish I were drawing regularly! I think I’ve actually been drawing pretty regularly for like two weeks now. Most of it is porn. I should probably draw some not-porn, too. It’s just, you know, porn is a lot of fun to draw.

  • secret thing: I laid some groundwork for the little game engine I’m writing and haven’t really talked about yet. More on that, including maybe even a name, once I feel like I have some kinda proof of concept.

  • sudoku thing: I taught it about extra regions so now it can be used to play hyper sudoku? I don’t know why I’m even making this. It’s kind of unusable until I add undo/redo and puzzle generation, and both of those are effort. I guess I’ll see if my spite is strong enough to power me through both.

  • streaming: Ash and I played video games on the internet while high and you can watch it if you really want to for some reason.

Hey, that’s not too bad a haul, considering I didn’t even have time to work for most of the month! Got some good stuff going on, glad to see I’m up to speed again at last.

Weekly roundup: Cherry Kisses

Post Syndicated from Eevee original https://eev.ee/dev/2019/04/01/weekly-roundup-cherry-kisses/

Hello hello! I finally finished that game I was working on, so now I might actually be back to some sort of normal dev schedule.

Except I’m gonna be kinda occupied for the next week or so. So.

  • cherry kisses: Hey hey I finished making Cherry Kisses, which is super duper NSFW! It’s probably the most well-designed and polished thing I/we have released, though. Whoops! I gotta stop accidentally making sex games.

    There’s some little niceties in there. Maybe I should, like, write about it sometime.

    Also attempted to get it to work on Android, which… is… non-trivial, despite LÖVE being “able” to target Android.

  • particle wipe generator: Cherry Kisses includes a cool heart transition between scenes, which took a surprising amount of effort to create, so I packaged up the code and put some dials and knobs on it. Now you can use the particle wipe generator to make your own particley transitions! Also hosted locally.

    Maybe I should, like, write about how this works sometime. Can’t wait for someone to tell me how I could’ve done it a thousand times more easily.

  • irl: We did some spring cleaning! Very exciting for anyone who doesn’t live here, I know. Our bedroom is no longer half-full of half-unpacked boxes, which is pretty nice.

  • sudoku: I occasionally waste time with a nice sudoku app, which has a free ad-supported version and a paid version. It has a sequel now, which is even better, but which only comes free with ads. I am incensed by this so I started writing my own JS player out of spite. Unclear whether my spite will last long enough to produce something usable.

Pretty happy to be back to makin’ things! I love that I could spin off some throwaway helper code into a little gamedev tool, and I’d definitely like to do more of that sort of thing in the future.

Weekly roundup: Strawberry Jam 3

Post Syndicated from Eevee original https://eev.ee/dev/2019/03/07/weekly-roundup-strawberry-jam-3/

Another double feature. Surprise, basically all I’ve been doing is working on a jam game. Should be back to normal once I get this out the door.

  • art: I doodled, like, once, but then was lost in gamedev all day every day.

  • cerise: I finally, like, planned out the progression of the game, and sat down to write it. Prose is harder for me than you’d think, and there’ve been a number of interruptions over the past month, so it’s taking a little while. I’m nearly done and am pretty happy with what I have so far, though.

    Actually, reading my notes here, I’m amazed how much of the game was done in only the last two weeks of February! I didn’t even have the passage of time working yet, and that’s the most fundamental part of the game.

    I did also cobble together a thing for generating particle wipes, which I think is pretty cool; I’ll probably write about it and release a web version in the near future.

Should be done in a day or two, but I’ve been saying that for a week, so who knows.

Weekly roundup: Off to a good start

Post Syndicated from Eevee original https://eev.ee/dev/2019/02/18/weekly-roundup-off-to-a-good-start/

I already missed a week! But I was mostly working on a jam game so that’s not too surprising.

  • art: Trying to keep up a semi-regular drawing schedule, with mixed success. I’m still working on my character lineup painting, though I’ve hit a few awkward spots that are proving difficult to fix. Sketched some stuff a few times. Drew Lexy with a sword.

  • music: I made part of a song, which was originally going to be for the Strawberry Jam game, and then I forgot about it, whoops. And now I will very much not have time to do music. It was coming out pretty okay, though, which is encouraging!

  • alice’s day off: Hey, remember this? Our wildly explicit VN for last year’s Strawberry Jam, which we intended to finish a few months later, and then, didn’t? Still working on it! I wrote out rough drafts for a couple more routes. This’ll probably become my main priority after this month, so I can actually get another thing done and off my plate.

  • cerise: Spent a lot of time on engine work (some of it not even necessary) and probably not enough on the game itself, and now I only have ten days left oops. Parallax layers are now actors, Tiled support is cleaned up a lot, sprites support four angles (or really, an arbitrary number of angles), physics were updated for top-down mode, and I finally implemented raycasting for realsies. Cleaned up dialogue code a lot, again, and put together basic dialogue UI.

    Fixing raycasting was a fun little problem, and free top-down movement offered an interesting little vector puzzle. Maybe I’ll write about those sometime.

    I also spent a little time porting some of my other LÖVE games to use my updated engine code, which also means they should run on LÖVE 11. I’m not finished yet, but once the month is over, I’d like to get updated releases out. It’ll only really matter for Linux users, since the Windows and Mac downloads include their own copy of the LÖVE runtime, but I’m a Linux user, so.

I better, uh, go get to work on this game.

Weekly roundup: Spectacular return

Post Syndicated from Eevee original https://eev.ee/dev/2019/02/05/weekly-roundup-spectacular-return/

Hey! Miss these? Great! I’m doing them again and no one can stop me.

  • art: I spent half the week rendering. Something, something, joke about rendering and EEVEE. No but really, I found out I’m kind of okay at this and set out to paint a whole lineup of all my Floraverse characters, which turned out to be really hard and time-consuming, but anyway here’s Lexy and slightly weirder Lexy and Cerise. Only, like, seven more to go.

    Hm. If only I’d constructed some sort of art website to put this kind of work on. If… only.

  • fox flux: This game keeps plodding along. I added a little blowing-a-kiss mechanic a while ago, and I finally gave it a real animation, which I then spruced up a bit more after recording that GIF. Also been cleaning up a big mess of half-finished features I left for myself, including particle effects for— well, that would spoil it!

  • strawberry jam: I’m running Strawberry Jam 3, the low-pressure month-long horny game jam! I haven’t gotten very far on my game yet, but most of the work is going to be upfront planning (I hope), so that’s not too worrisome. I just started writing code today, and hopefully will have some kinda rough skeleton done by the 25% point on Friday.

    This is gonna be most of my month! What an exciting topic to come back to.

More coming down the pipe; I’m accelerating all the time.

Storing Encrypted Credentials In Git

Post Syndicated from Bozho original https://techblog.bozho.net/storing-encrypted-credentials-in-git/

We all know that we should not commit any passwords or keys to the repo with our code (no matter if public or private). Yet, thousands of production passwords can be found on GitHub (and probably thousands more in internal company repositories). Some have tried to fix that by removing the passwords (once they learned it’s not a good idea to store them publicly), but passwords have remained in the git history.

Knowing what not to do is the first and very important step. But how do we store production credentials. Database credentials, system secrets (e.g. for HMACs), access keys for 3rd party services like payment providers or social networks. There doesn’t seem to be an agreed upon solution.

I’ve previously argued with the 12-factor app recommendation to use environment variables – if you have a few that might be okay, but when the number of variables grow (as in any real application), it becomes impractical. And you can set environment variables via a bash script, but you’d have to store it somewhere. And in fact, even separate environment variables should be stored somewhere.

This somewhere could be a local directory (risky), a shared storage, e.g. FTP or S3 bucket with limited access, or a separate git repository. I think I prefer the git repository as it allows versioning (Note: S3 also does, but is provider-specific). So you can store all your environment-specific properties files with all their credentials and environment-specific configurations in a git repo with limited access (only Ops people). And that’s not bad, as long as it’s not the same repo as the source code.

Such a repo would look like this:

└─── production
|   |   application.properites
|   |   keystore.jks
└─── staging
|   |   application.properites
|   |   keystore.jks
└─── on-premise-client1
|   |   application.properites
|   |   keystore.jks
└─── on-premise-client2
|   |   application.properites
|   |   keystore.jks

Since many companies are using GitHub or BitBucket for their repositories, storing production credentials on a public provider may still be risky. That’s why it’s a good idea to encrypt the files in the repository. A good way to do it is via git-crypt. It is “transparent” encryption because it supports diff and encryption and decryption on the fly. Once you set it up, you continue working with the repo as if it’s not encrypted. There’s even a fork that works on Windows.

You simply run git-crypt init (after you’ve put the git-crypt binary on your OS Path), which generates a key. Then you specify your .gitattributes, e.g. like that:

secretfile filter=git-crypt diff=git-crypt
*.key filter=git-crypt diff=git-crypt
*.properties filter=git-crypt diff=git-crypt
*.jks filter=git-crypt diff=git-crypt

And you’re done. Well, almost. If this is a fresh repo, everything is good. If it is an existing repo, you’d have to clean up your history which contains the unencrypted files. Following these steps will get you there, with one addition – before calling git commit, you should call git-crypt status -f so that the existing files are actually encrypted.

You’re almost done. We should somehow share and backup the keys. For the sharing part, it’s not a big issue to have a team of 2-3 Ops people share the same key, but you could also use the GPG option of git-crypt (as documented in the README). What’s left is to backup your secret key (that’s generated in the .git/git-crypt directory). You can store it (password-protected) in some other storage, be it a company shared folder, Dropbox/Google Drive, or even your email. Just make sure your computer is not the only place where it’s present and that it’s protected. I don’t think key rotation is necessary, but you can devise some rotation procedure.

git-crypt authors claim to shine when it comes to encrypting just a few files in an otherwise public repo. And recommend looking at git-remote-gcrypt. But as often there are non-sensitive parts of environment-specific configurations, you may not want to encrypt everything. And I think it’s perfectly fine to use git-crypt even in a separate repo scenario. And even though encryption is an okay approach to protect credentials in your source code repo, it’s still not necessarily a good idea to have the environment configurations in the same repo. Especially given that different people/teams manage these credentials. Even in small companies, maybe not all members have production access.

The outstanding questions in this case is – how do you sync the properties with code changes. Sometimes the code adds new properties that should be reflected in the environment configurations. There are two scenarios here – first, properties that could vary across environments, but can have default values (e.g. scheduled job periods), and second, properties that require explicit configuration (e.g. database credentials). The former can have the default values bundled in the code repo and therefore in the release artifact, allowing external files to override them. The latter should be announced to the people who do the deployment so that they can set the proper values.

The whole process of having versioned environment-speific configurations is actually quite simple and logical, even with the encryption added to the picture. And I think it’s a good security practice we should try to follow.

The post Storing Encrypted Credentials In Git appeared first on Bozho's tech blog.

Majority of Canadians Consume Online Content Legally, Survey Finds

Post Syndicated from Andy original https://torrentfreak.com/majority-of-canadians-consume-online-content-legally-survey-finds-180531/

Back in January, a coalition of companies and organizations with ties to the entertainment industries called on local telecoms regulator CRTC to implement a national website blocking regime.

Under the banner of Fairplay Canada, members including Bell, Cineplex, Directors Guild of Canada, Maple Leaf Sports and Entertainment, Movie Theatre Association of Canada, and Rogers Media, spoke of an industry under threat from marauding pirates. But just how serious is this threat?

The results of a new survey commissioned by Innovation Science and Economic Development Canada (ISED) in collaboration with the Department of Canadian Heritage (PCH) aims to shine light on the problem by revealing the online content consumption habits of citizens in the Great White North.

While there are interesting findings for those on both sides of the site-blocking debate, the situation seems somewhat removed from the Armageddon scenario predicted by the entertainment industries.

Carried out among 3,301 Canadians aged 12 years and over, the Kantar TNS study aims to cover copyright infringement in six key content areas – music, movies, TV shows, video games, computer software, and eBooks. Attitudes and behaviors are also touched upon while measuring the effectiveness of Canada’s copyright measures.

General Digital Content Consumption

In its introduction, the report notes that 28 million Canadians used the Internet in the three-month study period to November 27, 2017. Of those, 22 million (80%) consumed digital content. Around 20 million (73%) streamed or accessed content, 16 million (59%) downloaded content, while 8 million (28%) shared content.

Music, TV shows and movies all battled for first place in the consumption ranks, with 48%, 48%, and 46% respectively.

Copyright Infringement

According to the study, the majority of Canadians do things completely by the book. An impressive 74% of media-consuming respondents said that they’d only accessed material from legal sources in the preceding three months.

The remaining 26% admitted to accessing at least one illegal file in the same period. Of those, just 5% said that all of their consumption was from illegal sources, with movies (36%), software (36%), TV shows (34%) and video games (33%) the most likely content to be consumed illegally.

Interestingly, the study found that few demographic factors – such as gender, region, rural and urban, income, employment status and language – play a role in illegal content consumption.

“We found that only age and income varied significantly between consumers who infringed by downloading or streaming/accessing content online illegally and consumers who did not consume infringing content online,” the report reads.

“More specifically, the profile of consumers who downloaded or streamed/accessed infringing content skewed slightly younger and towards individuals with household incomes of $100K+.”

Licensed services much more popular than pirate haunts

It will come as no surprise that Netflix was the most popular service with consumers, with 64% having used it in the past three months. Sites like YouTube and Facebook were a big hit too, visited by 36% and 28% of content consumers respectively.

Overall, 74% of online content consumers use licensed services for content while 42% use social networks. Under a third (31%) use a combination of peer-to-peer (BitTorrent), cyberlocker platforms, or linking sites. Stream-ripping services are used by 9% of content consumers.

“Consumers who reported downloading or streaming/accessing infringing content only are less likely to use licensed services and more likely to use peer-to-peer/cyberlocker/linking sites than other consumers of online content,” the report notes.

Attitudes towards legal consumption & infringing content

In common with similar surveys over the years, the Kantar research looked at the reasons why people consume content from various sources, both legal and otherwise.

Convenience (48%), speed (36%) and quality (34%) were the most-cited reasons for using legal sources. An interesting 33% of respondents said they use legal sites to avoid using illegal sources.

On the illicit front, 54% of those who obtained unauthorized content in the previous three months said they did so due to it being free, with 40% citing convenience and 34% mentioning speed.

Almost six out of ten (58%) said lower costs would encourage them to switch to official sources, with 47% saying they’d move if legal availability was improved.

Canada’s ‘Notice-and-Notice’ warning system

People in Canada who share content on peer-to-peer systems like BitTorrent without permission run the risk of receiving an infringement notice warning them to stop. These are sent by copyright holders via users’ ISPs and the hope is that the shock of receiving a warning will turn consumers back to the straight and narrow.

The study reveals that 10% of online content consumers over the age of 12 have received one of these notices but what kind of effect have they had?

“Respondents reported that receiving such a notice resulted in the following: increased awareness of copyright infringement (38%), taking steps to ensure password protected home networks (27%), a household discussion about copyright infringement (27%), and discontinuing illegal downloading or streaming (24%),” the report notes.

While these are all positives for the entertainment industries, Kantar reports that almost a quarter (24%) of people who receive a notice simply ignore them.


Once upon a time, people obtaining music via P2P networks was cited as the music industry’s greatest threat but, with the advent of sites like YouTube, so-called stream-ripping is the latest bogeyman.

According to the study, 11% of Internet users say they’ve used a stream-ripping service. They are most likely to be male (62%) and predominantly 18 to 34 (52%) years of age.

“Among Canadians who have used a service to stream-rip music or entertainment, nearly half (48%) have used stream-ripping sites, one-third have used downloader apps (38%), one-in-seven (14%) have used a stream-ripping plug-in, and one-in-ten (10%) have used stream-ripping software,” the report adds.

Set-Top Boxes and VPNs

Few general piracy studies would be complete in 2018 without touching on set-top devices and Virtual Private Networks and this report doesn’t disappoint.

More than one in five (21%) respondents aged 12+ reported using a VPN, with the main purpose of securing communications and Internet browsing (57%).

A relatively modest 36% said they use a VPN to access free content while 32% said the aim was to access geo-blocked content unavailable in Canada. Just over a quarter (27%) said that accessing content from overseas at a reasonable price was the main motivator.

One in ten (10%) of respondents reported using a set-top box, with 78% stating they use them to access paid-for content. Interestingly, only a small number say they use the devices to infringe.

“A minority use set-top boxes to access other content that is not legal or they are unsure if it is legal (16%), or to access live sports that are not legal or they are unsure if it is legal (11%),” the report notes.

“Individuals who consumed a mix of legal and illegal content online are more likely to use VPN services (42%) or TV set-top boxes (21%) than consumers who only downloaded or streamed/accessed legal content.”

Kantar says that the findings of the report will be used to help policymakers evaluate how Canada’s Copyright Act is coping with a changing market and technological developments.

“This research will provide the necessary information required to further develop copyright policy in Canada, as well as to provide a foundation to assess the effectiveness of the measures to address copyright infringement, should future analysis be undertaken,” it concludes.

The full report can be found here (pdf)

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.