| // ==UserScript== | |
| // @name Youtube shorts redirect | |
| // @namespace Violentmonkey Scripts | |
| // @match *://*.youtube.com/* | |
| // @grant none | |
| // @version 1.0 | |
| // @author belst | |
| // @description 9/22/2022, 1:26:47 PM | |
| // ==/UserScript== |
| # Basic key operators to query the JSON objects : | |
| # #> : Get the JSON object at that path (if you need to do something fancy) | |
| # -> : Get the JSON object at that path (if you don't) | |
| # ->> : Get the JSON object at that path as text | |
| # {obj, n} : Get the nth item in that object | |
| # https://www.postgresql.org/docs/9.4/functions-json.html#FUNCTIONS-JSONB-OP-TABLE | |
| # Date | |
| # date before today |
Caching is a big subject and it can get pretty complicated. Luckily, the browsers have done all the really hard work for us and we just need to #useThePlatform.
There are three types of caches you'll likely deal with in Remix applications:
Cache-Control header.Cache-Control headers.
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| ... | |
| </head> | |
| <body data-controller="js"> | |
| <%= yield %> | |
| </body> | |
| </html> |
| // dm Klopapier Widget | |
| // | |
| // Copyright (C) 2020 by marco79 <marco79cgn@gmail.com> | |
| // | |
| // Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. | |
| // | |
| // THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL | |
| // IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, | |
| // INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER | |
| // IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE |
| ruby '2.7.1' | |
| gem 'rails', github: 'rails/rails' | |
| gem 'tzinfo-data', '>= 1.2016.7' # Don't rely on OSX/Linux timezone data | |
| # Action Text | |
| gem 'actiontext', github: 'basecamp/actiontext', ref: 'okra' | |
| gem 'okra', github: 'basecamp/okra' | |
| # Drivers |
This is another piece of code I've extrapolated from a Ruby on Rails project I'm currently working on. The code implmenets social login with a RoR API-based application, targeted at API clients.
The setup does not involve any browser-redirects or sessions as you would have to use working with Omniauth.
Instead, what it does is takes an access_token generated on client-side SDKs, retireves user info from the access token
and creates a new user and Identity in the database.
This setup works with native applications as described in the Google iOS Sign In Docs (see Authenticating with a backend server)
One way to do this is to use bundler to scaffold our gem:
bundler gem my_gem
I prefer to put tasks meant to manage the gem itself in lib/tasks, and tasks the gem is meant to provide to gem users in lib/my_gem/tasks.
| # This is a full-blown offset-based pagination system modelled after GraphQL-Ruby's | |
| # built-in connections. It has a few different elements: | |
| # | |
| # - `::Page`, a plain ol' Ruby class for modeling _pages_ of things. | |
| # This class handles applying pagination arguments to lists (Arrays and AR::Relations) | |
| # and provides metadata about pagination. (Similar to `will_paginate`.) | |
| # - `Schema::BasePage` is a generic GraphQL-Ruby object type. It's never used directly, | |
| # but it can generate subclasses which wrap _specific_ object types in the schema. | |
| # - `Schema::BaseObject.page_type` is a convenience method for generating page types | |
| # from your object types. You could leave this out and make subclasses with plain ol' |
Recently more and more chatbots appear, the overall chatbot market grows and the platform for it grows as well. Today we are taking a close look at what benefits creating a microservice chatbot on Discord - (a communication platform mainly targeted at gamers) would provide.
The concepts and ideas explained in this whitepaper are geared towards bots with a bigger userbase where the limits of a usual bot style appear with a greater effect
(If you are already proficient with the Discord API and the way a normal bot works, you may skip ahead to The Concept)