farzaa

Dec. 2021 Update

Hey everyone, it's been an insane last two months. Over 35,000 devs, $200,000 in booked revenue, and multiple web3 companies created + launched by buildspace alumni. Crazy to think 6 months ago we were building ZipSchool -- a product for kids K-5 (you can still use it if you want hehe).

TLDR: We've become to default place devs come to join web3 (ex. see here, here, here, and thousands of others here). We'll also be raising money. Focused mainly on raising from founders/ex-founders. If that sounds like you, pls DM me :).

Going to combine the November and December update here.

fchollet

'''This script goes along the blog post
"Building powerful image classification models using very little data"
from blog.keras.io.
It uses data that can be downloaded at:
https://www.kaggle.com/c/dogs-vs-cats/data
In our setup, we:
- created a data/ folder
- created train/ and validation/ subfolders inside data/
- created cats/ and dogs/ subfolders inside train/ and validation/
- put the cat pictures index 0-999 in data/train/cats

emaloney

Simplified notation for avoiding the [weak self]/strongSelf dance with closures

• Proposal: TBD
• Author: Evan Maloney
• Status: Draft
• Review manager: TBD

Introduction

Frequently, closures are used as completion callbacks for asynchronous operations, such as when dealing with network requests. It is quite common to model these sorts of operations in such a way that an object instance represents a request/response transaction, for example:

1lann

Storing and playing back replays in League of Legends

How it works

When you spectate a game in League of Legends, you tell the client to use a HTTP server, and make HTTP requests to it to retrieve data in chunks which make up a game. But what if you could return back the exact same data at a later time, simulating the spectate but viewing it at anytime? That's the concept behind replays and that's how they work.

There is some behavior in the API which I do not fully understand yet, so there are if statements to catch these edge cases.

Current game information

Before you can even get the game's metadata, you'll need to retrieve necessary information for the game. This call is part of the official Riot Games API.

/observer-mode/rest/consumer/getSpectatorGameInfo/{platformId}/{summonerId}

themasch

REST Service for LoL spectators

This is an unofficial, uncomplete and (pretty sure) wrong documentation of the RESTful service which powers the League of Legends spectator mode.

This documentation is desgined to be community driven and should be extended by everyone. If you find things missing, add them please!

How it works

Riot's spectator mode works by requesting replay data via HTTP form a service. The data is split in chunks which usually contain about 30 seconds of gameplay. Additionally there are key frames which seem to contain more information then a single chunk. They seem to be used to support