Rfc

Never read one before and I am willing to read some but there are way too many and some are just too damn outdated. What's a must read RFC? For example, I think ( I'm not sure though ) that RFC 1945 which describes HTTP 1.0 isn't useful to read because that version is outdated and RFC 7230 (HTTP 1.1) & RFC 7540 (HTTP 1.2) should be read instead.

Just like that, can someone suggest all the RFCs that a newbie like me should go ahead and read? I've read Networking Top down approach book and I believe reading RFCs is the way to go now.

Rekkles went Kraken + Guinsoo + RFC in his LEC game just now. I wanted to see how this stacked up in practice tool, and if this build was correct. Here are my conclusions. Note, I closed my PT so I don't have the exact numbers.

I tested the following builds:

Test 1:

• (1) Duskblade + Muramana + RFC
• (2) Kraken + Guinsoo + RFC
• (3 )Kraken + Muramana + RFC

NOTE: Kraken builds used Zerkers, Duskblade used the standard swifties.

At all soul levels, (2) is the highest damage build by far. Higher DPS, higher damage. The downside is losing the CDR from duskblade + muramana, and lower AD meaning lower healing from your Q.

So now that we know Kraken + Crit is stronger, is IE better than Guinsoos? Note, I tested, and over-capping crit with Senna's passive gives her over-capped Guinsoo's on-hit damage.

I did test 2 based on 80 souls, so that she wouldn't have any over-capped on-hit, which theoretically should favor IE.

Test 2 (80 souls):

• Kraken + Guinsoo + RFC + LDR
• Kraken + IE + RFC + LDR

In this test, Guinsoo outdamaged IE by ~10%, even with the crit damage ratio increase in a previous patch.

Conlusion (TLDR):

• Senna ADC's highest damage build is Kraken + Guinsoo + RFC + Zerkers. This build outdamages duskblade in AA+Q+AA by 20%+ and has much higher DPS.
• It only costs 300 more than the Duskblade build
• You sacrifice some utility due to lack of CDR from duskblade and muramana

REASONING:

• Senna's passive lets her over-cap guinsoo's on-hit damage. This is NOT necessary to outdamage her other builds though
• Guinsoo's on-hit applies to ALL targets hit by her Q
• Phantom hit gives an extra second off her Q CD when she attacks
• Senna's AS Ratio was recently increased to 0.3 from 0.2 (50% increase)
• Kraken now counts Q as an auto attack for the true damage

I believe most members of this community are quite familiar with the present issues with melee units and RFC.

Most of them feel kinda bad or lackluster without it in many fights and some don't even exist without it, like Zed.

When thinking about it, I noticed there's a design imbalance between melee and ranged:

Melee units:

• Have to walk up close
• Stay more time in a vulnerable position (being hit by other melee and ranged units)

Ranged units:

• Only sometimes have to walk up close
• Stay less time in a vulnerable position, compared to melee units

With RFC, melee units essentially become 660 range units. It's understandable that melee units 'want to' become ranged units because the ranged category has a net gain in the tradeoff.

If you're here and you play TFT, I bet that you've played countless games where you lost because the melee unit had bad pathing or spent too much time walking instead of attacking. Winning and losing are all part of the game, but those losses feel specially frustrating.

It's important to note that, the higher the range, the unit:

• spends less time walking (+ value)

• spends more time attacking, therefore casting spells (+ value)
• spends less time in a vulnerable position (+ value)

All of the above is a non-issue if units have gap-closers. Think of Set 3 Irelia and Set 4 Talon, for instance. They are melee units that never seemed to require an RFC to work properly.

The crazy solution I have in mind is: make all melee carries have a built-in gap-closer, not only high cost ones. That's it. The gap-closer may become more sophisticated as the cost increased, but even low cost (like $2) units should have some form of gap-closer, that would make them not need RFC.

Or maybe, an even more crazier idea, make RFC give melee units a gap-closer ability instead of turning them into ranged units. As if a Hypothetical 3-cost Irelia only had Bladesurge, but a 3-cost Irelia with RFC would re-cast Bladesurge on kill and dash to the enemy unit with lowest mana/armor.

I'd like to close my thoughts by reiterating the idea I stated before: ranged units have a net gain in the tradeoff over melee units. Melee units lose too much value in combat by just spending less time attacking, which means less time casting spells. Even if Zed doesn't have mana, his ability requires three consecutive autos to activate.

I invite you guys to share your thoughts on the melee units/RFC matter. All thoughts, any thoughts.

Do you think the game b

Recently I've been building an item build optimizer for my website, and was puzzled to find out that botrk was performing consistently better in my simulations than in-game. After spending some quality time with practice dummies, I guess I found out what's going on.

You probably know botrk passive is based on target's current HP (10% if melee, 6% if ranged). A more subtle fact: the current HP is calculated before, not after, the hit lands. So against a 1000-HP dummy, botrk passive is supposed to hit 100. Armor/MR is set to 0 to ensure no rounding errors.

1. botrk only: AD 113, hits 213 => botrk passive: 100

https://preview.redd.it/rg6eequgjj861.png?width=1920&format=png&auto=webp&s=7017c47c718d257d0662c4acafcb89e4c6c95670

2. with Stormrazor: AD 153, hits 241 => botrk passive 88

https://preview.redd.it/ow6sm4fklj861.png?width=1920&format=png&auto=webp&s=e40caa9a679bba7f9f1b3c2052178dec9607dd07

3. with RFC: AD 113, hits 201 => botrk passive 88

https://preview.redd.it/7sjerdbllj861.png?width=1920&format=png&auto=webp&s=f1cf015151c5bfe8ef784070021887bba6570dff

4. with Stormrazor and RFC: AD 153, hits 229 => botrk passive 76

https://preview.redd.it/qc3m6ysllj861.png?width=1920&format=png&auto=webp&s=3fa14cc71bd2abc6cc9259a1cc7acf331cb0b981

So, it looks like the current HP is calculated before the AD part of the auto, but after the on-hit effects of Stormrazor/RFC. But this is not consistent with other on-hit items.

5. with Guinsoo: AD 113, hits 253 (Guinsoo 40) => botrk passive 100

https://preview.redd.it/ddmkk28olj861.png?width=1920&format=png&auto=webp&s=344eed4bdb905b5459b83f908153281d146b0e25

Now the fun part: with Nashor's Tooth, Wit's End, or Muramana, it depends on whether you bought botrk first or not. If you buy it first, botrk passive deals 100 (current HP is calculated before the on-hit effects). If you buy it second, it deals less than 100 (calculated after the on-hit effects).

6-1. botrk and then nashor: AD 108, hits 208 => botrk passive 100

https://preview.redd.it/n9tkq1wvlj861.png?width=1920&format=png&auto=webp&s=c9b5edd0dfdc99ae482d2e02de98751c2cba5343

6-2. nashor and then botrk: AD 108, hits 204 => botrk passive 96

https://preview.redd.it/836u46iwlj861.png?width=1920&format=png&auto=webp&s=01e0abcfcc166b026da57e67f4e738241cf87335

7-1. botrk and then wit's end: AD 143, hits 243 => botrk passive 100

Buen dia,

Soy mexicano y por razones de que no encontraba trabajo por mi area decidi empezar a trabajar en UpWork, es un sitio para freelancers.

El dia de hoy con urgencia me pidieron mi RFC a causa de una ley mexicana de Taxes que entro en vigor al parecer el 01 de Junio (creo) y fue modificada este Enero del 2021.

Al parecer aaaal parecer solamente me quitaran 1% de mis ingresos. Alguien pudiera orientarme acerca de esta ley o que tanto impactara siendo mexicano.

Si no proporciono mi RFC UpWork me quitara 20% de mis ingresos por cada pago.

Gracias de antemano

I'm not asking about why Rust doesn't have this or trying to start a conversation - I'm only asking if there's an existing RFC that I could read that discusses it.

Also, note that I'm not asking about (multiple) inheritance, because I understand (and support) the motivation for not having that. Below isn't really inheritance, since there's no inheriting of methods or trait implementations. It's just a reduction of boilerplate, and the compiler should have the ability to yell at me if I'm trying to 'fold' in fields of the same name.

Context:

When I write CRUD apps, I'll often have a number of very similar objects for related endpoints that are used to deserialize params. Often, they'll all have the same set of base fields and might differ in a few others, since UPDATE might not allow all the fields that CREATE does, etc.

Basically, instead of...

#[derive(Deserialize)]
struct CreateParams {
    name: String,
    description: String,
    type_of_thing: SomeEnum,
    // ... more unique fields
}

#[derive(Deserialize)]
struct PostParams {
    name: String,
    description: String,
    // ... more unique fields
}

... I wish I could do...

struct BaseParams {
    name: String,
    description: String,
}

#[derive(Deserialize)]
struct CreateParams {
    ..BaseParams,
    type_of_thing: SomeEnum,
    // ... more unique fields
}

#[derive(Deserialize)]
struct PostParams {
    ..BaseParams,
    // ... more unique fields
}

I don't hugely care about the redundant definitions when writing, since I just copy/paste them anyway, but it does kind of harm readability since there's no explicit link between the different params objects; you just have to look at the field definitions to know they have similar fields/types.

And yes, I know I can write a macro to accomplish that, but that is more work and less readable, so I still would rather just copy/paste. (Even though the macro 'guarantees' that the structs' shared fields stay in sync.)

I got into red wriggler composting 9 months ago and I love it. As I learned, I kept a lot of my friends abreast of my vermiculture struggles and in the past few months, more and more of them have been asking me about the basics, about how to get started and about my insight into the the process.

I also recall that when I got started, there was a ton of content out there, but I ended up spending a ton of time watching dozens of videos and reading multiple blogs to answer my top-of-mind questions.

This prompted me to put together a beginner's doc that I feel comfortable sharing with people, and I thought this might be the sort of thing that might interest you: https://docs.google.com/document/d/1YuNx63MhO0vQdkqEYBZhF55VxPIAHKHDHIQh19GWbW0/

I'm far from an expert, so if you have suggestions or ideas, I've enabled commenting and would love to hear from you! Maybe some of this can be adapted to go into the subreddit's empty wiki?

Thanks again to this great community for making this exciting journey seem approachable!

I have an EVPL from a service provider and one of the legs is showing packet loss. I figured I could use this as an opportunity to learn to set up RFC2544 tests on our Juniper hardware. With the config below, I see the packets arrive on the interface of the MX104 when I use the monitor traffic interface xe-2/0/0.1202 matching "port 4001" command, but that command doesn't show any outbound packets and the ACX2200 initiatior reports 100% packet loss. Can anyone point me in the right direction to run a family inet test between these two devices? I've seen that the MX240/480/960 routers require some chassis-level config to enable rfc2544 testing, but I've never seen the requirement for anything similar on the MX104. Am I maybe missing something at that level?

ACX 2200 Config

services {
    rpm {
        rfc2544-benchmarking {
            profiles {
                test-profile test1 {
                    test-type frame-loss;
                    packet-size [ 1280 64 ];
                    bandwidth-kbps 1000;
                }
            }
            tests {
                test-name test1 {
                    test-profile test1;
                    mode initiate-and-terminate;
                    family inet;
                    source-udp-port 4001;
                    destination-udp-port 4001;
                    destination-ipv4-address 1.2.3.12;
                    source-ipv4-address 1.2.3.24;
                }
            }
        }
    }
}

MX104 Config

services {
    rpm {
        rfc2544-benchmarking {
            tests {
                test-name test1 {
                    mode reflect;
                    family inet;
                    source-udp-port 4001;
                    destination-udp-port 4001;
                    test-interface xe-2/0/0.1202;
                    destination-ipv4-address 1.2.3.24;
                    source-ipv4-address 1.2.3.12;
                }
            }
        }
    }
}

Edit: I've tried the config on the MX104 as above but without test-interface and as above but without source-ipv4-address. I've tried using two ip addresses on each end of the /31 that connects these two devices(1.2.3.12/31). Regardless of what I do, running test services rpm rfc2544-benchmarking test test1 start on the MX104, which I presume is needed for the r

As I have reported a year ago, Tutanota still steals e-mails.

If you add a domain to Tutanota but set your MX records elsewhere (to your own server perhaps), Tutanota will steal all e-mails directed to addresses on such domain. They will not be delivered to the mail server set by MX records, but instead directly to the Tutanota Mailbox.

This violates several RFCs and security as it can be exploited in a number of ways.

E-mails should always be delivered to mail server designated by MX records.

Hi guys

I'm planning the following setup for my first XMR miner.According to most of the posts in this sub the 3900X should be the CPU that bring most value for money.

Setup:

• AMD Ryzen 9 3900X (500$)
• Graphic card: Sapphire Radeon RX 550 Pulse 2GB
• Mainboard: AsRock B550M Pro4
• Power Supply: Corsair TX550M (Gold)
• RAM: Crucial 32GB DDR4 2666 MT/s UDIMM HyperX Fury 1x, 32GB, DDR4-3200, DIMM 288 HyperX Fury RGB, 2x, 8GB, DDR4-3200, DIMM 288
• HD: Toshiba P300 6TB Toshiba P300 Retail 3TB, 3.5", CMR
• Case: Fractal Node 804

The whole setup will cost me around 1k USD. Thoughts?

Update

- I'm planning to use the server for other things, such as a private NAS and private app server (running some docker containers) in case I want to test something. Hence the high storage and RAM.

- My cost per KWh are 0,28$

- I'm not planning to fully amortize the hardware cost, just part of it. :)

- added graphic card: Sapphire Radeon RX 550 Pulse 2GB (just took the cheapest AMD I found)

- changed RAM to 2x HyperX Fury RGB for dual-channel capability and oc to some extend

- replaced SMR harddisk with CMR (SMR are not suitable for RAIDs)

It is my favorite item and i miss being able to build it. but since it gives no ad it seem troll to build 99% of game

Today i was playing Senna in soloq, i was stomping lane against Samira, i got superfed. I built the boots, kraken, guinsoo, rfc and then i didnt know what to build next.

What do you think are the best items? I thought collector could be cool for the Lethality and damage. But maybe Navori is better coz that + Qs passive u can spam Qs really fast and procs kraken faster.

EDIT: u/K-2-L-U Reminded me that Guinsoo removes critcs, and navori only procs with crits xD.

thinking ldr, mortal, bloodthrister, or collector but honestly no idea

Hey, was wondering which of the 2 is more optimal. Kraken - Guinsoos is OP right now as we all know, but building Rageknife after Kraken then leaving it alone to complete Rapid Firecannon first also feels really good. I do understand that Rageknife is a powerspike and you rush that, but is the double-hit passive of Guinsoos a better powerspike than the RFC range? Or is it up to preference?

Also, this is anecdotal, but pros have done this, Rekkles finished RFC first after getting Kraken and Rageknife in G2 vs MSF earlier.

And I didn't play tft before set 4.

I couldn't find a Uke chord chart small enough to fit in my case that I didn't have to pay for, so I created my own. I'm posting it in case someone else finds it helpful, but also to solicit suggestions or improvements.

• Is there a different order you'd prefer?
• Is it missing what you consider a common chord?
• Did you find one of the many mistakes I'm sure I've made?
• Is it so close to what you need if it just had this one feature?

Let me know, please!

You can see the current version at
https://gitlab.com/zanfar/ukechart/-/blob/master/uke-chord-ref.pdf

Features:

• Small enough (5”×7”/A7) to fit in a soprano case
• Still printable on a standard-sized index card
• Can be printed 2-up on a Letter or A4 piece of paper
• Organized by base note and type for quick reference

it went from being core 3rd item for draven for 5 years to not usable :(

RIP RAPIDFIRE CANNON

After the announcement (https://brave.com/themis-rfcc/), where it is stated

>First, the Brave Research team will organize public sessions where the THEMISv2 components are presented and  discussed. The  goal  of  the  first  phase (from the 8th January to the beginning of February) is  to  introduce  THEMISv2  to  the community,

I was expecting some infos to be delivered...
But as of now, end of January, nothing has happened.
The discord channel shows this message (https://imgur.com/a/2EBlogH) from the 11th of January:

>Hi there! Thanks for joining the the RFC Discord server! We'll be sharing here a technical report this week next week, which outlines how the THEMISv2 protocol works in the context of Brave Ads and Rewards, specs, required properties and guarantees, etc. It will also have information on how the event will roll -- So basically, the tech report will serve as a basis for the whole event, stay tuned!

this week next week .... ? When?

Here's Larry's full message: https://externals.io/message/112417#112469

tl;dr: the enum RFC now doesn't include value-specific methods anymore. I personally think that's a very good thing. I explained my thoughts here: https://externals.io/message/112417#112452

Nikita also voiced his concerns about value-specific methods here: https://externals.io/message/112417#112453

So this won't be possible:

enum Suit implements Colorful {
  case Hearts {
    public function color(): string {
      return "Red";
    }
  }
 
  case Diamonds {
    public function color(): string {
      return "Red";
    }
  }
 
  case Clubs {
    public function color(): string {
      return "Black";
    }
  }
 
  case Spades {
    public function color(): string {
      return "Black";
    }
  }
 
  public function shape(): string {
    return "Rectangle";
  }
}

But this will:

enum Suit implements Colorful {
    case Hearts;
    case Diamonds;
    case Clubs;
    case Spades;

    public function color(): string {
        return match ($this) {
            Suit::Hearts, Suite::Diamonds => "Red",
            Suit::Clubs, Suite::Spades => "Black",
        }
    }
}

Inspired by work of /u/Nicolas-Rougier, I have developed a package to give a coherent look to emacs, based on a palette of just a few colors. But I wanted this theming to remain customizable. Here are some example results: light dark darker.

And here is a example palette configuration function:

(defun est-cloudy-night () ;; dark palette, blue accents
  (interactive)
  (let ((est-color-bg-selected "#192435")
        (est-color-bg-subtle   "#242e41")
        (est-color-bg-default  "#2b3547")
        (est-color-fg-default  "#cccfd4")
        (est-color-fg-salient  "#5a8bca")
        (est-color-fg-popout   "#00c8ff"))
    (est-reevaluate)))

More tweaks are possible; the whole code is here.

What’s the process for completing RFC’s? It’s been years since I’ve done them and my SM told me to scan everything in one tray. I get done scanning 7 totes worth and the Ironman asks if I want to continue with another tray. Who can help me with how to correct this or did I do it the right way? Thanks in advance!

A diamond 2 streamer I told me rfc is not that good in wild rift for tf because you need all the ap tou can get... rank 1 and 2 tf do build it, 3 and 4 not tho... what do you think?

PS: if you have a good build for gold 1 tf too, pls comment it, thanks a lot :)

View Poll

Having an issue with my wife's 4a5g that will not allow the chat features, although turned on. Tried resetting message caches and carrier cache.

Any ideas ?

(She still has the light blue sms bubble and not the royal blue for Rfc/ wifi)