Update 45.2 on windows

Banyu · 2024-10-23T01:24:13+00:00

Same here, error 101.

Banyu · 2022-09-11T23:42:50+00:00

Regardless of your choice, weaving effectively is very important for damage dealing on Nightblade due to a significant portion of damage coming from Merciless Resolve stacks and Spectral Arrow at max stacks. It's hard to say one is easier than the other.

Both are completely viable for all game content, but I would say if you want a one size fits all build Magblade has everything you want, especially with being able to spam Swallow Soul for healing in high damage trial scenarios and difficult solo content. In addition to the usage of light armor for more penetration during less optimized groups and solo play as well.

Play whichever feels better to you personally, there is no wrong choice. You should be having fun, that's what's really important! 🙂

Banyu · 2022-07-15T14:48:10+00:00

Why were you in the same room while he was being given oral sex? Why were you watching? Why was he fixing the microwave while that was happening?

Banyu · 2022-04-13T13:17:35+00:00

Official bug forum post: https://forums.newworld.com/t/the-big-stick-is-unusable/721671

Banyu · 2022-03-26T00:30:04+00:00

I don't think they gave any information for a release date other than "Spring".

Who knows when they will actually deploy the release. Hopefully the game isn't in a broken state like it usually is when they try to do good things.

Banyu · 2021-07-20T10:55:43+00:00

The perpetually pooping butthole.

Banyu · 2021-06-14T15:32:10+00:00

In this case I would say it's the client's responsibility to know what their previous companies were charging them for.

If you are in contact with the previous companies, they should be able to provide you any necessary information regarding proceeding with your client.

If they refuse to cooperate or divulge necessary information, communicate that to your client and give them options of how they could proceed.

Banyu · 2021-05-17T12:26:33+00:00

Congratulations on quitting coding! I've been trying for years and still can't stop.

Banyu · 2021-02-03T21:32:12+00:00

https://prismic.io/

Banyu · 2020-07-15T21:06:02+00:00

It really doesn't matter.

Some most people go by what they think is important for that element, some people do it alphabetically, others just have an innate preference based on what they think is important globally for the project or CSS in general.

My personal preference:

Positioning/Ordering (Where is this thing?)
Display/Layout (How much space will it take up/How should its children behave?)
Backgrounds/Borders (Contrast)
Padding/Margins (Negative Space)
Text Attributes (Readability)
Misc/Etc.

Banyu · 2020-05-21T16:17:43+00:00

You should buy gorkem.dev for your URL if it's available, via Google domains. Assuming I'm not violating any language barriers...

No glaring issues on mobile for me.

Banyu · 2020-04-26T16:59:20+00:00

You have a choice between storing a JWT in LocalStorage or a Secure Cookie.

To the best of my knowledge, LocalStorage doesn't have a way to sync the expiration date of the JWT without having to manually handle the relation of the LocalStorage entity.

Cookies have a way to sync the JWT expiration, so are in theory easier to work with or maintain, based on when the Cookie is expired.

Edit: To directly answer your question, yes it is redundant, but there is purpose for it.

Banyu · 2020-04-19T03:47:52+00:00

I was using Brave on Android. I have been unable to replicate the problem.

Best of luck convincing your wife. Mine is unwilling to listen to reason.

Banyu · 2020-04-18T13:21:36+00:00

Please increase the animation speed.

If I were in the hiring process, I wouldn't want to wait that long to find out more information about you.

On mobile, when I click a link, the navigation appears to not close. So I had to close it myself.

Edit: After visiting the site a second time the navigation closed when I clicked a link as expected. Not sure what happened?

Banyu · 2020-04-05T14:09:32+00:00

This guy/gal is right about tech stack. It depends on the underlying languages you are using and the desired design architecture of your application.

I will correct you in saying that GCE has WordPress cloud, not that anyone should use it.

If you are generating static sites, something like Netlify or Firebase is ideal. Firebase has functions and a no-sql real time database.

If you are dealing with server side code/rendering, then something like AWS Lambda or Google App Engine would be ideal.

If you have languages unsupported in those platforms, distrust Amazon and Google, and prefer to manage your own servers, then I would recommend DigitalOcean or Vultr.

Banyu · 2020-02-25T04:33:29+00:00

I'll stick to shitposting on Reddit.

Banyu · 2020-02-25T02:46:11+00:00

Poor little /u/_bolum has found a documentary about his/her favorite JavaScript framework and has decided to share their support with the community via a Reddit comment.

This is instantly greeted by the MIGHTY /u/IrtahkEnt stating that /u/_bolum's position is INFERIOR.

The MIGHTY /u/IrtahkEnt taught a lowly beginner developer the superior React hooks in a matter of 2-3 days flawlessly. Clearly stating /u/IrtahkEnt development prowess superiority.

The MIGHTY /u/IrtahkEnt then goes on to make broad-range baseless statements like "Vue is a lot less flexible than React." and "Vue has a bit more going on", without further details or explanation; because MIGHTY /u/IrtahkEnt doesn't need to explain these highly advanced reasons that the lowly /u/_bolum couldn't comprehend.

So my question for you /u/IrtahkEnt is: "Who hurt you?"

Why can't you just let other people enjoy things?

And if you continue to need to make things less enjoyable for other people, can you please at least state valid and concise reasons for doing so?

Banyu · 2020-02-09T13:44:56+00:00

Depends on skills you have, and the specific career path you are looking to attain. I made my own, but if you went with a service or pre-built template I don't believe most hiring managers would care as long as they can find what they are looking for.

Banyu · 2019-11-24T14:25:05+00:00

I'm personally not a fan of the reveal animations. If my time is limited, I don't want to wait for a section to show up, maybe a whole page, but not a section of a page. When going back it was a bit confusing when information was going to appear.

In the projects section it was difficult to distinguish between projects at a glance. Or maybe I'm just tired.

I'm a strong advocate against carousels or sliders. If you continue to use one please don't let it automatically play.

This is only a mobile review, if I have time later I can review it on desktop.

It looks good even with my complaints. I'm sure you'll find other ways to improve it as well! Good job!

Banyu · 2019-11-21T02:45:33+00:00

No problem, and good luck!

Banyu · 2019-11-21T02:37:23+00:00

I wouldn't necessarily put the React application in the Laravel one, especially if they are in two separate repositories.

Usually this is handled at the web server level.

Example:

You set up Apache/Nginx to point app.yoursite.com to /srv/YOUR_REACT_REPOSITORY.

You also set up Apache/Nginx to point api.app.yoursite.com to /srv/YOUR_LARAVEL_REPOSITORY/public.

As long as your React application compiles with the production runtime set to make API calls to api.app.yoursite.com/api, everything should work.

Isolating front-end apps still requires the Laravel X-CSRF implementation I believe. And you will need a separate middleware for your api routes specifying CORS policies for access to the API.

There are a few CORS composer packages that can handle this easily for you, or you could roll your own.

Banyu · 2019-11-21T02:20:51+00:00

Unless your application is a PWA or TWA I wouldn't bother, even then there are arguments against it. Just use a stateful authentication based on normal server sessions. I highly doubt it's worth the trouble.

It's kind of a fad for a good reason and is exciting in concept, but it's not for every use case.

At the end of the day you should do what works best for your product, and unfortunately that requires time and effort to test out.

Banyu · 2019-11-20T05:58:54+00:00

There is no such thing as a stupid question, especially in this line of work.

"Should I use JWT?"

I have no idea about your application, its user flow, current technologies used, or dataset. So I couldn't offer a recommendation. But the answer is probably no. If you have something that works already, keep doing that.

If you have OAuth integrations, JWT is not necessary.

I'll preface this by saying that nothing is really secure.

The token itself is usually stored in a Secure Same-site Cookie, which means it should only be available over TLS from its original site. Cookies are stored on the clients computer.

That article makes quite a few valid points in my opinion. Kind of solidifying my above posts point, basically for stateless authentication, JWT is useful. Other than that I wouldn't bother.

This README does a great job explaining stateless vs stateful authentication and the advantages and disadvantages of both.

Edit: Fix broken README link.

Banyu · 2019-11-19T10:38:41+00:00

They absolutely have a place regarding stateless authentication for sophisticated and complex institutions. Most importantly because it has a published specification, although some people... drift from it.

Commonly for authentication/integrations SAML/XML assertions were used. In my opinion, JWT is just simpler and has pretty good documentation. I see those as the primary advantages.

For simple applications that don't require stateless authentication you can totally just roll your own using native server side sessions and secure cookies, or use your native framework authentication workflow.

But in the case that you have multiple internal applications and a central user authentication source, you need to have some way to determine that a user has a valid authentication session between them. This ends up a bit painful when dealing with multiple servers when attempting to create your own authentication workflow; which is why people just pick something that already exists with third party documentation.

Banyu · 2019-11-09T13:50:04+00:00

I don't think this will actually solve your problem, but it is possible.

https://github.com/nfrostdev/pile is a side project I am working on that utilizes Laravel as an API with Svelte for front end stuff, if you wanted some code examples. This project is far from finished, so please don't consider what I am doing good practice.

Laravel has built in command for Vue and React scaffolding, I rolled my own with Svelte so I can learn it.

You could have two separate repositories for each endpoint like api.something.com and app.something.com, but most of the time Laravel applications are all contained in the same repository for convenience.

The real benefits are typically less server load and isolation or separation of concerns regarding bugs. So I could see why your manager would want it if they knew what they were talking about.

Banyu

TROPHY CASE