#todo: report bug | Explore Tumblr posts and blogs

this-week-in-rust · 2 years ago

Text

This Week in Rust 492

Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on Twitter or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR.

Updates from Rust Community

Official

Announcing Rust 1.69.0 | Rust Blog

Project/Tooling Updates

rust-analyzer changelog #178

regex 1.8.0 release notes

Fornjot (code-first CAD in Rust) - Weekly Release - Where We've Been, Where We're Going

pavex, a new Rust web framework - Progress report #3

r3bl_tui v0.3.3 TUI engine released

Autometrics 0.4: Spot commits that introduce errors or slow down your application

Rust Search Extension v1.11.0 has been released

[video] Rust Releases! Rust 1.69.0

Observations/Thoughts

Is Rust a worthy contender for web development?

Bringing runtime checks to compile time in Rust

Can the Rust type system prevent deadlocks?

Why is Rust programming language so popular?

[video] Embeddable Rust

Rust Walkthroughs

Guide to Rust procedural macros

Rust + Embedded: A Development Power Duo

A blog article and project demonstrating GitHub actions in Rust

Foresterre's place | Using the todo! macro to prototype your API in Rust

Generics and Const Generics in Rust

Writing an NES emulator: Part 1 - The 6502 CPU

Integrating the Rust Axum Framework with Cloudflare Workers

ESP32 Embedded Rust at the HAL: GPIO Button Controlled Blinking

GBA From Scratch: A Basic Executable

[video] A Practical Introduction to Declarative Macros in Rust

Miscellaneous

Bringing Memory Safety to sudo and su

Console #154 - An Interview with Giuliano of Sniffnet - Rust app to easily monitor network traffic

[DE] Programmiersprache: Rust Foundation überarbeitet Trademark-Entwurf

Crate of the Week

This week's crate is system-deps, a crate that will compile your pkg-config-based dependencies for you.

Thanks to Aleksey Kladov for the suggestion!

Please submit your suggestions and votes for next week!

Call for Participation

Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

Some of these tasks may also have mentors available, visit the task page for more information.

Hyperswitch - add upsert endpoint to cards_info table

Hyperswitch - add a route that will invalidate cache

Hyperswitch - Implement ApiKeyInterface for MockDb

Hyperswitch - Implement ConfigInterface for MockDb

velo - Add ability to switch canvas background - Issue #22 - StaffEngineer/velo - GitHub 3

velo - Hex color widget - Issue #58 - StaffEngineer/velo - GitHub 1

ockam - Update CLI documentation for secure-channel-listener commands 1

ockam - Update CLI documentation for identity commands

ockam - Refactor auto-reconnect replacer 1

If you are a Rust project owner and are looking for contributors, please submit tasks here.

Updates from the Rust Project

411 pull requests were merged in the last week

add support for the x86_64h-apple-darwin target

support AIX-style archive type

assume value ranges in transmute

rustc_metadata: Remove Span from ModChild

add suggestion to use closure argument instead of a capture on borrowck error

deduplicate unreachable blocks, for real this time

delay a good path bug on drop for TypeErrCtxt (instead of a regular delayed bug)

ensure mir_drops_elaborated_and_const_checked when requiring codegen

fix ICE for transmutability in candidate assembly

fix lint regression in non_upper_case_globals

fix printing native CPU on cross-compiled compiler

make impl Debug for Span not panic on not having session globals

make non_upper_case_globals lint not report trait impls

make sysroot finding compatible with multiarch systems

missing blanket impl trait not public

normalize types and consts in MIR opts

panic instead of truncating if the incremental on-disk cache is too big

report allocation errors as panics

report more detailed reason why Index impl is not satisfied

set commit information environment variables when building tools

substitute missing trait items suggestion correctly

suggest using integration tests for test crate using own proc-macro

track if EvalCtxt has been tainted, make sure it can't be used to make query responses after

miri: add minimum alignment support for loongarch64

miri: disable preemption in tokio tests again

miri: remove a test that wasn't carrying its weight

don't transmute &List<GenericArg> <-> &List<Ty>

enable flatten-format-args by default

rm const traits in libcore

remove the size of locals heuristic in MIR inlining

don't allocate on SimplifyCfg/Locals/Const on every MIR pass

allow to feed a value in another query's cache and remove WithOptConstParam

implement StableHasher::write_u128 via write_u64

in LexicalResolver, don't construct graph unless necessary

turn on ConstDebugInfo pass

run various queries from other queries instead of explicitly in phases

add intrinsics::transmute_unchecked

add offset_of! macro (RFC #3308)

limit read size in File::read_to_end loop

specialize some io::Read and io::Write methods for VecDeque<u8> and &[u8]

implement Neg for signed non-zero integers

hashbrown: change key to return &K rather than &Q

hashbrown: relax the trait bounds of HashSet::raw_table{,_mut}

regex: fix prefix literal matching bug

portable-simd: lane → element for core::simd::Simd

portable-simd: implement dynamic byte-swizzle prototype

cargo: add the Win32_System_Console feature since it is used

cargo: allow named debuginfo options in Cargo.toml

cargo: better error message when getting an empty dep table

cargo: fix: allow win/mac credential managers to build on all platforms

cargo: improve error message for empty dep

clippy: arithmetic_side_effects cache symbols

clippy: arithmetic_side_effects detect integer methods that can introduce side effects

clippy: add items_after_test_module lint

clippy: add size-parameter to unecessary_box_returns

clippy: bugfix: ignore impl Trait(s) @ let_underscore_untyped

clippy: check for .. pattern in redundant_pattern_matching

clippy: don't suggest suboptimal_flops unavailable in nostd

clippy: fix #[allow(clippy::enum_variant_names)] directly on variants

clippy: fix false positive in allow_attributes

clippy: ignore manual_slice_size_calculation in code from macro expansions

clippy: ignore shadow warns in code from macro expansions

clippy: make len_zero lint not spanning over parenthesis

clippy: new lint: detect if expressions with simple boolean assignments to the same target

clippy: suppress the triggering of some lints in derived structures

rust-analyzer: add #[doc(alias(..))]-based field and function completions

rust-analyzer: don't wavy-underline the whole for loop

rust-analyzer: editor.parameterHints.enabled not always being respected

rust-analyzer: deduplicate passed workspaces by top level cargo workspace they belong to

rust-analyzer: fix need-mut large span in closures and a false positive

rust-analyzer: fix panic in const eval and parameter destructing

rust-analyzer: fix pat fragment handling in 2021 edition

rust-analyzer: mbe: fix token conversion for doc comments

rust-analyzer: remove extra argument "rustc"

rust-analyzer: report remaining macro errors in assoc item collection

rust-analyzer: resolve $crate in derive paths

rust-analyzer: register obligations during path inference

rust-analyzer: simple fix for make::impl_trait

rust-analyzer: specify --pre-release when publishing vsce nightly

Rust Compiler Performance Triage

A week mostly dominated by noise, in particular a persistent bimodality in keccak and cranelift-codegen. No significant changes outside of that, a relatively equal mix of regressions and improvements. Most of the bimodality has been removed in the full report as it's just noise.

Triage done by @simulacrum. Revision range: 74864fa..fdeef3e

3 Regressions, 6 Improvements, 5 Mixed; 1 of them in rollups 60 artifact comparisons made in total

Full report here

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

RFC: result_ffi_guarantees

Final Comment Period

Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.

RFCs

Add RFC on governance, establishing the Leadership Council

Tracking Issues & PRs

[disposition: merge] Use fulfillment to check Drop impl compatibility

[disposition: merge] Only check outlives goals on impl compared to trait

[disposition: merge] rustdoc: restructure type search engine to pick-and-use IDs

[disposition: merge] Stabilize raw-dylib, link_ordinal, import_name_type and -Cdlltool

[disposition: merge] Add deployment-target --print flag for Apple targets

New and Updated RFCs

[new] RFC: Rustdoc configuration via Cargo (includes feature descriptions)

[new] RFC: Partial Types

Call for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:

No RFCs issued a call for testing this week.

If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.

Upcoming Events

Rusty Events between 2023-04-26 - 2023-05-24 🦀

Virtual

2023-04-26 | Virtual (Cardiff, UK) | Rust and C++ Cardiff

Rust-friendly websites and web apps

2023-04-27 | Virtual (Charlottesville, VA, US) | Charlottesville Rust Meetup

Testing Tock, how unit tests in Rust improve and teach

2023-04-27 | Copenhagen, DK | Copenhagen Rust Community

Rust meetup #35 at Google Cloud

2023-04-29 | Virtual (Nürnberg, DE) | Rust Nuremberg

Deep Dive Session 3: Protohackers Exercises Mob Coding (as far as we get)

2023-05-02 | Virtual (Buffalo, NY, US) | Buffalo Rust Meetup

Buffalo Rust User Group, First Tuesdays

2023-05-03 | Virtual (Indianapolis, IN, US) | Indy Rust

Indy.rs - with Social Distancing

2023-05-09 | Virtual (Dallas, TX, US) | Dallas Rust

Second Tuesday

2023-05-11 | Virtual (Nürnberg, DE) | Rust Nuremberg

Rust Nürnberg online

2023-05-13 | Virtual | Rust GameDev

Rust GameDev Monthly Meetup

2023-05-16 | Virtual (Washington, DC, US) | Rust DC

Mid-month Rustful

2023-05-17 | Virtual (Cardiff, UK) | Rust and C++ Cardiff

Rust Atomics and Locks Book Club Chapter 2

2023-05-17 | Virtual (Vancouver, BC, CA) | Vancouver Rust

Rust Study/Hack/Hang-out

Asia

2023-05-06 | Kyoto, JP | Kansai Rust

Rust Talk: Vec, arrays, and slices

Europe

2023-04-26 | London, UK | Rust London User Group

Rust Hack & Learn April 2023

2023-04-27 | Bordeaux, FR | DedoTalk

#2 DedoTalk 🎙️ : Comment tester son code Rust?

2023-04-27 | Vienna, AT | Rust Vienna

Rust Vienna - April - Hosted by Sentry

2023-05-02 | Amsterdam, NL | Rust Developers Amsterdam Group

Fiberplane Rust Workshop

2023-05-10 | Amsterdam, NL | RustNL

RustNL 2023

2023-05-19 | Stuttgart, DE | Rust Community Stuttgart

OnSite Meeting

North America

2023-04-29 | Durham, NC, US | Triangle Rust

Rust Social / Coffee Chat at Boxyard RTP

2023-05-03 | Austin, TX, US | Rust ATX

Rust Lunch

2023-05-11 | Lehi, UT, US | Utah Rust

Upcoming Event

2023-05-16 | San Francisco, CA, US | San Francisco Rust Study Group

Rust Hacking in Person

Oceania

2023-04-27 | Brisbane, QLD, AU | Rust Brisbane

April Meetup

2023-05-03 | Christchurch, NZ | Christchurch Rust Meetup Group

Christchurch Rust meetup meeting

If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

That said, I really like the language. It’s as if someone set out to design a programming language, and just picked all the right answers. Great ecosystem, flawless cross platform, built-in build tools, no “magic”, static binaries, performance-focused, built-in concurrency checks. Maybe these “correct” choices are just laser-targeted at my soul, but in my experience, once you leap over the initial hurdles, it all just works™️, without much fanfare.

– John Austin on his blog

Thanks to Ivan Tham for the suggestion!

Please submit quotes and vote for next week!

This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, andrewpollack, U007D, kolharsam, joelmarcey, mariannegoldin, bennyvasquez.

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust

#rust-lang #rust #rustlang #twir #long post

1 note · View note

necromancercoding · 2 years ago

Note

Este tipo de problemas se soluciona con un hard reset.Y otro check importante sería saber si te sucede solo a ti o sucede a más usuarios, por saber si es algo local o del propio server// Pues parece que solo me pasa con Chrome, porque tanto en Edge como en Mozilla parace que va todo como la seda. Puesto que es un foro de pruebas solo lo veía yo, pero le he preguntado a una amiga y no le pasa. Entonces tiene pinta de ser problema de Chrome, pero ya he borrado cookies e historial, le pasado el cleaner y todo eso pero después de actualizar varias veces normal al final vuelve a pasar (? Y tengo que volver a hacer un hard reset. No entiendo nada la verdad, gracias por tu respuesta Necro, me ha servido para saber que es algo particular 🤍 Preguntaré también en asistencia a ver si me pueden echar otro cable.

¡Hola de nuevo, anon! A ver, es bueno saber que es algo más localizado, y que si es un foro de pruebas, no tiene por qué pasarte en el foro final; que a las malas, cambias a un nuevo foro de pruebas y listo. Ahora, ¿por qué puede estar pasando?

Han habido casos en donde ciertas versiones de Chrome no cacheaban bien el CSS de ciertas páginas (hay páginas que usan ciertos bypasses de phpbb para evitar esto), por lo que si no encuentras otra solución y te está pasando en más páginas, te recomendaría desinstalar por completo Chrome (asegúrate de estar loggead@ y guardar todos tus marcadores/recorridos/historial/passwords en tu cuenta de Google para ahorrarte pérdidas) y volver a instalarlo desde cero, para asegurar que tienes todo al día y que tu navegador tiene todo en regla. Si siguen pasando y si en asistencia no te dan solución (es posible que te digan que no tiene nada que ver con ellos si solo te pasa en ciertos navegadores y en un entorno localizado, y en parte tienen razón, pero estaría bien saber si ha ocurrido en otras ocasiones y si han habido soluciones para esto), te recomiendo hacer un bug report en Chrome, que al ser localizado en su navegador, podrán también darte una respuesta más concreta.

#necro talks

0 notes

transienturl · 2 years ago

Note

Ooh, very nice hack.

(Besides not working with at.tumblr.com URLs, but what did one expect, really.)

Edit: Ah, it only works on the first GIF on a post. Never mind.

What logic does Tumblr use to populate the gifs selected by the "insert gif" feature? The results it returns seem nonsensical, and I've never been able to figure out if there's some way I can game the system to get the kinds of gifs I expect to see.

(Tangentially, it seems like Tumblr rolled its own gif solution. Why did you guys opt to go custom versus integrate something like Giphy?)

it’s mostly based on tag usage, i think. also there’s a secret hack where you can just put the URL of a specific post in the search input and it’ll return the GIFs from that post. (or at least there used to be, i haven’t tried that in awhile.)

as for why not integrate with giphy: our GIF search was built in 2016 or so, basically as a potential giphy competitor. we didn’t want to integrate them. personally it still irks me that so much of how giphy started was scraping GIFs from tumblr and other sites without providing attribution.

#can I support form that #screw it I'm doing it anyway #todo: report bug

104 notes · View notes

sweetstardewvalley · 2 years ago

Text

🐛 Onde e como reportar bugs do 1.5 mobile!

Todos os bugs devem ser reportados no fórum oficial apenas em Inglês.

Antes de postar é preciso ler as instruções de postagem localizadas no primeiro post do tópico.

Segue a tradução:

Nota: Tenha certeza que o seu aplicativo está atualizado antes de postar o seu bug report, o problema que tu tem pode já ter sido consertado!

É necessário preencher um formulário muito simples ao postar seu bug, assim a equipe pode trabalhar melhor para arrumá-lo.

Tipo de telefone: (seja o mais específico possível) Detalhes do teu problema: (Coisas como onde está acontecendo e o que acontece. O que tu estava fazendo no jogo quando aconteceu e se tu está passando por esse problema consistentemente) Screenshots/vídeos: (encorajamos muito o envio) No dia do problema, tu caregou o save através do menu de load (acordou na cama) ou foi um load de emergência (onde tu começa no lugar onde parou antes)? Qualquer outra informação que seja relevante:

#stardew valley #tradução #bugs

4 notes · View notes

caio-cc · 2 years ago

Note

oi Caio, tudo bom? queria te perguntar a respeito de uma roupa cc que no meu jogo parece ter sofrido um bug. eu fiquei apaixonada naquele Flower Dress da sua coleção Florence, mas quando eu adicionei na pasta de mods, uma das versões ficou com todos os swatches do vestido bugados, reproduzindo a textura da pele da sim em vez da estampa, mudando apenas a cor do bolero (só uma, a outra funcionou perfeita). mais alguém reportou esse problema? seria possível separar as versões em dois arquivos?

Oi, tudo e vc? Isso não é um bug. É apenas uma forma de conseguir mudar a cor do vestido, nos acessórios tem um item para você escolher a cor. :D

#reply

1 note · View note

transienturl · 1 year ago

Text

ughhhh

so tumblr's frontend appears to have nice logic to disallow e.g. white-text-on-white-background in blog themes and gracefully increase the contrast

unfortunately, it's not done serverside or when the user sets their theme colors. so the api gives you the raw colors without this process being applied, and that's all we can use for xkit rewritten's themed posts script. this can result in unreadable text.

interestingly, this process doesn't seem to be applied to the blog cards that appear when one mouses over a blog avatar; that's a clear oversight and I'll bug report that.

fixing that wouldn't help with the xkit themed post scenario though. and I can't easily replicate the code tumblr uses; it looks damned complicated when minified.

(to observe this, go to @labs and mouse over the avatar of one of its posts; unlike on the main page where its description is grey, the description is white in the card. yep, I noticed this on an official blog... and spent some extra time checking if it was special behavior for that blog or if it was related to hiding the blog title, just to be sure :D)

#tumblr meta #todo: report bug

2 notes · View notes

transienturl · 2 years ago

Note

Reminder to myself to test this more thoroughly later, but I definitely have not experienced "it just works."

I’ve been fairly surprised that the web beta post editor has no undo/redo functionality. It feels like that would be an essential feature! It’s super frustrating when I delete some piece of text I was writing, maybe trying to rephrase it – only to change my mind and then have to type it from scratch. Why can I undo and redo in this ask box and when replying to a post, but not when composing a new post?

Answer: Hey, @schyrsivochter!

This is a curious one—a few of us here at HQ have tested, and it works as expected, so this leads us to think that what you’ve found here must be a bug. We recommend that you file a Support request about it, and we will take a look. You’ll find news on our work here or at @changes.

Thanks for flagging this with us—send a report and we’ll get it resolved as soon as possible. Keep the questions coming!

Best,

—Javi, Cyle, Aaron

#todo: report bug

55 notes · View notes

meeeeyahhhhh · 6 years ago

Text

Knock Knock. Who’s There? (Jasonette) (continuation of The Most Vibriant Color)

Orange. Orange was the color of pill bottles, the eyes of vampiric bats in the night, and the tint of the orange plastics that polluted the earth. Orange was the color of a shirt Jason Todd was trying to pack. The voices finally broke him into going to Paris and now he needed to pack. Jason had no idea how long he would be there, but he also had no plans of returning to Gotham anytime soon. Dick walked into the room, “Dickie boy, what’s up?”

The older adoptee stared at his brother, “Are you sure you want to leave? You just got back.”

Jason didn’t just want to go, he needed to leave. If the pit madness didn’t drive him insane, the constant way Bruce and Dick treated him like he was a bomb just waiting to explode would. They claimed they missed him, mourned him, wept oh so many tears, but in the end they had just replaced him. Jason would never be Dick; he knew it; Bruce knew it; hell, Dick himself said he would never be good enough.

The steel blue orbs bore into Jason’s making him shift uncomfortably, “Then it will feel like I never came back,” he laughed but Dick found no humor in his words, “Listen Dick, I’m not you. I’m going to be fine.”

Jason wasn’t fine, not right now, not in Gotham. He was suffocating. Loneliness was a silent killer, one worse then the Joker. Jason knew it would kill him all over again if he didn’t do anything to stop it. Dick didn’t understand, he was the golden child. Dick was the first, the better Robin, the most charming, respectful, and kind one of the Bat’s kids. He lived a good life in the circus with his family and then immediately be adopted by one of, if not, the richest men in the world. Dick didn’t grow up on the streets, he wasn’t treated like an outsider in his adopted family, he wasn’t toyed with, frayed, bruised, ripped, or mutilated like Jason. A stranger in his own body is what Jason was.

All of these feeling were internalized of course. What’s the point of talking about the emptiness that plagued him, when everyone was already moved on? Jason had no purpose anymore. Why would Bruce miss one of his thousand kids? Jason was just another passion project... right? Did he serve any real purpose to begin with? All of these thoughts stuck with Jason. No matter how much he wished they would just go away, they would stay ever fervently whirling like a tornado inside Jason’s psyche. The only way to escape them was to leave. They’d have to, if they didn’t Jason didn’t know what he’d do. This is his last hope to try and just be a kid again. A luxury Jason was never given, this is the time where Jason reclaims the innocence that was stolen from him.

He swore it. He meant it. He was going to live it.

After Dick had finally left the room, Jason finished packing. This was the final piece to the puzzle that was Jason’s future. Gotham would lose Jason Todd again, this time by choice. What good did his return do anyway. Gotham could live without Red Hood, she could live without another troubled kid, she could live with one of her kids living without her. Gotham couldn’t live with one of her babies dying again in front of her. Paris craved chaos and by Kawamii was Jason going to raise hell while he’s there. Gotham knew this, so she passed one of her favorite boys to Paris in hopes of his life being preserved. Paris welcomed him with open arms too. What about a baker’s daughter?

Orange. A color of insincerity, empty calories, a color without substance. Orange was a color that would haunt Marinette. Everywhere she turned an Ex-friend and a liar would be there trying to gain her attention. The liar spun beautiful tales of her exploits, but she also created terrors to ruin Marinette. The pathetic excuse of a reporter pestered her into helping her tabloid of a blog, “Come on! Get me an interview with Ladybug!” She would shout, “I have to know about what happened with Rena and Carapace!”

“For the last time, Alya, I’m not in anyway, shape, or form obligated to help you. I’ve made myself very clear in stating that we aren’t friends. You talk bad about me, try to ruin my commission website, and on top of all of that you expe- no, demand something of me?!?” Marinette was furious. The insolence Alya repeatedly shown to her angered her to new bounds, “You think you are in a position to be speaking to me at this moment? Alya, I’m tired of this routine you have taken accustomed to falling into. Just because you forgot your own actions, doesn’t mean I’ve forgotten nor forgiven you for. If you come by the bakery again, I’ll put a restraining order on you in school and outside. You have become a stalker, I don’t want anything todo with you.”

Marinette had to take deep breaths and close her eyes to calm herself down. 1... 2... 3... repeat. 1... 2... 3... repeat until calm. She could not risk akumitization, it was not an option. Ladybug couldn’t be compromised. Emotions are a luxury that Marinette cannot be awarded. Alya on the other hand, she had no control and abused that.

Once Marinette had opened her eyes, she saw a purple little butterfly touch and be absorbed by Alya’s frames. The exchange between the supervillain and Alya was brief, he didn’t have to say much before the glow of power overtook the glasses sporting journalist. Marinette thought to herself, ‘I can never catch a break, can I?’

Marinette ran, commanding the people to evacuate, to the nearest locker to hide and change in. Tikki has taken no time to change and showcase her new look. Ladybug had outgrown the red and black, polka dotted, skin tight, spandex. She was much too mature for that now. Ladybug was layered in body armor, away with the pigtails that feigned innocence. Her hair was now loosely pulled back by two braids with the rest of her hair down, now her suit was a majority of black. Marinette’s mask’s colors had been inverted. Ladybug was a guardian of the order, a leader, a symbol, she needed to update her look.

She existed the locker, yo-yo in hand. Ladybug swung to higher ground. She had no information on the powers of this akuma, it was time to play everyone’s favorite: the waiting game. This also allowed for Char Noir to get here in time. In the beginning Chat was a little pushy and childish, but after 5 years of fighting he became jaded and more serious in his role. He got himself a girlfriend that didn’t work out but she was there, became a better friend, and more importantly a friend. Chat was tired, the only reason he was still fighting is because of Ladybug. His lady needed someone to balance her out, so until they can find his replacement they’re stuck.

After 5 minutes of waiting and observing, Chat had arrived, “What’s the status? What happened Bugsboo?”

“The akuma’s in her glasses. Alya, was told off by Marinette apparently and couldn’t handle it. And before you say something about Marinette instigating, Alya was harassing her about an interview with me. I will not give her an interview either. She doesn’t want to fact check, fine. I don’t want to give her an interview.”

Chat sighed. This whole situation was getting out of hand. He lost Marinette. Alya is on a warpath. Lila keeps harassing him. Maybe it was time to build his ark while the flood rages. He’s exhausted of playing middleman, of losing important people, he’s tired of fighting. After this he would beg Marinette to accept his apology, but if she didn’t want to he’d understand. This was going on for long enough.

The fight itself only took around 30 minutes. Once the cure was done, Alya awoke to see Ladybug staring her down. Alya didn’t seem to get that Ladybug was infact angry at her, “Ladybug! Can I get an interview?”

“I believe Marinette had told you I wouldn’t be giving you anymore interviews,” she said with venom, she hadn’t meant to but it was seeping out. “I saw the messages you and the rest of you class sent her. All of the hate, I know you tried to ruin her website. And for the last time, I do not know a Lia Rogatonie or whatever her name is. Now if you’ll excuse me, I have to leave. Bug Out!”

Alya was left stunned. Tears stained the cheeks of the “reporter” and she realized that she had been live-streaming the exchange. All of Alya’s followers had seen her be chewed out by the savior of Paris and Chat had only nodded. It wasn’t long after Ladybug left that Chat went in the opposite direction.

Marinette landed in an ally by the airport. She had to run home now that school was cancelled. Not actively paying attention to her surroundings, she had run into a large man. He was about 6’0 (182.88 cm) and all muscle. His jet black hair had a white streak going through it, he was devilishly handsome, and his eyes. Oh god, his eyes. They were clear blue, however, there was green infringing on them. It was a sickly green too. Marinette almost drooled at the sight of the Grecian god standing before her.

He had stumbled a bit but she had fell completely on her bottom. Marinette’s face was the same shade of her old suit design. Eventually the man had helped her up with an extended hand, “Are you okay?” He asked in rapid English.

If it wasn’t for all of the lessons Jagged and Penny had given her, she wouldn’t have understood a lick of anything he said, “Umm, I’m fine. T-Thank you,” she responded in accented English.

“You wouldn’t have the directions for Le Grand Paris would you,” he switched the language on her. “That’s where I’m staying, I got lost.”

“Oh, yes of course! I could help you get there, Monsieur...” she waited for him to fill the blanks.

“Jason,” He supplied, “Jason Todd.”

She outstretched her hand again, “Marinette Dupain-Cheng,” she said with her blindingly bright smile.

The sun was setting. A gorgeous orange glow was cast over the two as they walked towards Le Grand Paris. Each thought the other as etherial being and fell into comfortable conversation. This would be the start of a beautiful friendship and possibly romance.

A/N: This was one of my favorite things to write. Thank you to everyone who likes, comments, reblogs, and thank you for sending in the asks. They make my day like you wouldn’t believe. I never expected this many people would actually like the word vomit that comes from my mind. Also, special thanks to @/abrx2002 for the idea to make this series dealing with the entire rainbow! I was just going to do red, but now I’m doing the whole rainbow. If the series isnt done by purple, I’ll do more colors. Also if I didn’t tag you, it’s because I can only tag 50 people at a time. However, I’ll tag you in the comments!

Tag list: @abrx2002 @amayakans @mystery-5-5 @normal-piece-of-shit @st0rmy-w1th1n @mysteriouslyswimmingfan-blo-blog @g-arya @smolplantmum @rayray384 @rosa97 @drarryismylife101 @kris-pines04 @black-streak @storyteller-d @weird-pale-blonde-person @maribat-shenanigans @vivilakitty @mycupisbroken @zalladane @gingerdaile @18-fandoms-unite-08 @seraphichana @zebrabaker @northernbluetongue @jardimazul @ranger-gothamite @grimmhallow31 @finallyaniguana @persephonebutkore @rarity36 @throneoffirebreathingbitchqueen @hell-or-high-waters @moonlightstar64 @raisuke06 @evil-cricket @starwindmaden @kuroko26 @primeemeraldheiress @ladysblackcat @senpaiweird @loveswifi @2sunchild2 @timetomakeanewwish @theyellowfeverexperience @iloontjeboontje @vgirl-10123 @vixen-uchiha @winter-gardenflower @yokizu @risingmoonyue @semaalcocer-blog

651 notes · View notes

karaokulta · 11 months ago

Text

¡Atención, gamers y profesionales del marketing! 🎮 Hoy, quiero sumergirme en el potentísimo mundo de los videojuegos y cómo el marketing y branding son tan esenciales como un ultimate en el momento justo. **Marca tu territorio en el mapa de batalla virtual** 📍 - No importa si eres un indie que está empezando o un triple A consolidado, tu juego necesita más que una buena historia o gráficos impresionantes. Necesita una identidad que grite: ¡Aquí estoy y soy espectacular! - Piénsalo como seleccionar tu personaje en un RPG: cada atributo cuenta, cada habilidad suma, y el diseño de tu avatar... ese, amigos, es tu logo, tu color palette, tu packaging. **Crea una historia que los jugadores quieran vivir, no sólo jugar** 📜 - El storytelling es tu quest principal; debe seducir a los jugadores, hacerlos sentir parte de algo épico. El lore de tu marca es la inmersión que cautiva, más allá de cualquier gameplay. - Y sí, como en cualquier buena narrativa, tus personajes (productos, servicios, DLCs) deben evolucionar, enfrentar conflictos y ¡ganar! (reconocimiento, ventas, fandom). **Power-ups sociales: tu guild indiscutible** 🗣️ - Las redes sociales son como tu party: cada una tiene habilidades únicas (engagement, targeting, formatos de contenido) y debes saber cuándo y cómo usarlas. - El contenido es tu spell más potente. ¿Es oportuno? ¿Atractivo? ¿Levantará a la audiencia de sus asientos? Ese es el tipo de magia que queremos. **El endgame: Fidelización** 🔐 - Todo gran juego tiene su replay value, algo que hace que los jugadores vuelven una y otra vez. Eso, para nosotros, es la lealtad de marca. ¿Tu producto tiene un New Game+ atractivo? Piénsalo. - Las DLCs y expansiones son como programa de lealtad. Ofrecen más contenido, más razones para quedarse, más recompensas por ser un jugador leal a tu marca. Ahora, como bien sabe todo buen estratega, es importante aprender de los mejores pero también de tus propios errores (¡bug report, por favor! 🐞). Y recuerda, el feedback de tu comunidad vale oro; escúchales, porque al final del día, ellos son tus jugadores más apasionados y tu marketing más efectivo. Cuéntame, ¿qué estrategias únicas estás implementando en tu próximo lanzamiento? ¿Cómo estás construyendo tu comunidad de jugadores leales? ¡Sumérgete en la conversación y comparte tus insights! ¿Conoces a alguien que está rompiendo esquemas en la industria del videojuego? Taggea a esos innovadores o pregúntales que nos dejen una pista de sus misiones secretas en los comentarios. 🕹️ #Videojuegos #MarketingDigital #GamingBranding #Storytelling #EstrategiaDeContenidos #CommunityBuilding #Branding #InnovaciónEnVideojuegos

0 notes

aezart · 4 years ago

Text

I've joined a game jam!

For the next 90 days, I'm going to be participating in 90 Days & Ship It! Jam 2021. It's a game jam hosted by Game Endeavor, which challenges devs to make a complete game by August 7.

I'm very excited for this, because I find that I just can't muster the energy to work on game development lately unless I have a deadline. And since most game jams are 30 days or less, most of my projects don't make it past the prototype/demo stage.

I'm thinking I'll be able to make a fairly solid game in this 90 day period. I already have a very basic idea of the kind of thing I want to make: a grid-based gem puzzle, similar in style to games like "Bejeweled" (but not the same game mechanics).

Beyond the basic game mechanics, I'm not sure what kinds of game modes I'll want. A story mode would probably be too much. But maybe a puzzle mode and an high-score-challenge endless mode could work.

I don't intend to start actual work until the jam begins in about 17 hours. For now, though, I've set up some infrastructure for my development process:

An empty Godot project

A Fossil repository

An itch.io page

Scripts for building the Godot project and publishing to itch

I'm using Fossil instead of Git for version control because it has a built-in wiki and issue tracker. Lately I've been having some anxiety about storing issues externally to the repo, because it ties me to a web server. Fossil's issue tracking UI is definitely not my favorite (I'd prefer something that feels more like a developer-oriented "todo" list and less like an end-user-oriented bug-reporting tool), but not having to worry about losing access to my issues is a huge relief.

#game jam #game development #godot engine

1 note · View note

shinsengumi-archives · 5 years ago

Text

Ikedaya Incident from Nagakura’s Diary

All the same, in any way I can’t finish it off normally, I’m stuck on the description of Nagakura’s exploits in Ikeda-I (and how easy it was to retell: “to this destiny, then to that bam!”) So I’m doing a half-closed record again, please take a look at the subject of bugs and who-where-to-who-why. She tried to preserve the stylistics of Nagakurina, but he has almost every sentence there: “without losing a minute, he chopped off”, “without losing a minute, ran” and other endless repetitions, I dilute as much as possible))

A native of Omi Province named Omiya Shungoro (aka Masuya Kemon) held a horse harness shop on Shijo Kobashi Street. Shinsengumi was arrested of this type and taken to the barracks, where during the course of the investigation he gave his real name - Furutaka Shungoro. During the interrogation, he stubbornly did not want to confess, so he was tortured, and in the end he confessed everything. According to Furutaki’s testimony, 10 people often visited his house, all like one of Choshu, and in his warehouse he kept all kinds of equipment for setting fire to the imperial palace. The implementation of their plan was scheduled for the 22nd day of 6 months - on a windy day they were going to set fire to the palace, capture Emperor Komei and take him to Yamaguchi Castle. In plotting this plot, people from Choshu were hiding in the vicinity of Shijou, as well as on Sanjou Street, in a hotel under the guise of the Minakuchi clan from Omi, etc. - Only about 300 people. From Furutaki's confession, all their intentions became clear, which Shinsengumi immediately reported to the head of the Aizu clan, Mr. Matsudaira Katamori. Utterly shocked

Hijikata Toshizo, based on the testimony of Furutaki, led a detachment to Gion Kaiso (chambers of commerce) , which is at the foot of the stairs of the Yasaka-jinja temple. Already at 7 o’clock in the afternoon (from 4 p.m. to 6 p.m.), Shinsengumi arrived there and searched every corner of the teahouse, but they didn’t find anyone - apparently everyone had already escaped from there. Then they began to comb the entire area along the Kamogawa coast and received information that in the north, in the Ikeda-ya hotel near Sanjo Kobashi, perhaps Choshu was holding a secret meeting. Leaving a few people outside, Kondo Isami, Okita Soji, Nagakura Shinpachi and Todo Heiske entered the front door and found rifles, spears and other weapons that they tied together to confiscate. Entering the front hall, they called the owner Ikeda-ya and said: “Tonight we check all the hotels!” The owner got scared and rushed up the far stairs to the second floor, four Shinsenites immediately rushed after him, and there were about twenty Choshu, and all with swords at the ready. “You are arrested until the circumstances are clarified. If you resist, you will be ruthlessly killed, ”Kondo shouted in a thunderous voice. The rebels trembled with fear and stepped back, but then the bravest of them suddenly attacked. Okita instantly finished him off with one blow. Then the others rushed to the first floor, and Kondo immediately ordered them to follow. Light was burning in the lower rooms, and this became a big help for Shinsengumi, but soon Okita was forced to leave the battlefield due to his illness (he returned to the barracks) , so there were three of them left inside the hotel. Kondo held the defense in the far rooms, Nagakura guarded the area from the kitchen to the main entrance, Todo - access to the garden. Noticing that one of the rebels rushed to the front door, Nagakura chased after him. Near the exit, the fugitive pierced Tani Mantaro with a spear, and Nagakura finished off with a blow to the shoulder, after which he returned to his former place. When another man ran to the same exit, Nagakura caught up with him and cut him off the shoulder obliquely. Then one of the conspirators rushed towards the garden and disappeared into the restroom. Nagakura pierced the enemy through and through, he tried to draw his sword, but lost his strength and fell. Without waiting a minute, the Shinsenovets cut him with one blow. Todo Heiske was seriously injured by one of Choshu, blood pouring in his eyes, preventing him from fighting, and besides, his sword blade broke. Seeing this, Nagakura hastened to help Todo, intending to hit his opponent in the side, but he skillfully repelled the blow and switched to Shinpachi. Todo due to severe wounds was no longer able to continue the fight (retired to the same place and Okita) . 永倉は必死に闘い��づけ近藤を見ていると,三度ばかり切られそうになり,助太to PLCしようとすれど, 奥の間に志士が大勢いてそれもままならず、永倉はやっとのことでこの者の肩先に切り込んで倒した。。 Nagakura, fighting not for life but for death, saw that Kondo was nearly killed 3 times? Or 必死 does this apply to Kondo? Nagakura wanted to help him, and what was there with that crowd of people? And the one whom he killed at the end is talking about the same with whom Todo had fought before, or is this already from Kondin’s opponents? The four rebels laid down their arms and apologized, after which they were immediately connected. Nagakura’s hand was slightly injured, and the blade of the sword was chopped, so I had to take the sword of one of Choshu. At this moment, several people from Shinsengumi burst through the main entrance and began to search the hotel. Having broken the ceiling, one of the conspirators collapsed from the second floor, and Takeda Kanryusai immediately cut him down. All those who managed to run out into the street surrendered to the riot police. 島田魁の鑓が長州人に刀鎗の太刀打より五寸ほほど手前より切り落とされ、すぐさま刀にて仕留める - I don’t understand what the hell is like after that? Skirmishes also occurred in front of Ikeda-ya in the Sanjo Kobashi area. The owner of Ikeda-I was not tied up, as a result of which he untied several conspirators and allowed them to escape. Noticing this, Harada Sanosuke rushed after him and dealt with them with his spear. At this time, the vassals of Matsudaira Etтu no kami (Matsudaira Sadaaki) killed two Choshu - they died instantly. And the vassals of Matsudaira Higo no kami (Matsudaira Katamori) took the rebel from Choshu for the samurai of the Minakuti clan, and without becoming tied, they led him under arrest. On the way, the detainee slashed the warrior of the Aizu clan from the shoulder obliquely and rushed to run, but at the gates of the residence of Choshu he was caught and killed. Meanwhile, Shinsengumi arrested another 4 or 5 people from Choshu, as well as the owner of Ikeda-ya, and without exception brought everyone to the city prefecture. After this, Matsudaira Higo-no-kami immediately reported the incident to the imperial court, where everyone was in great admiration. As a reward, Shinsengumi granted 300 ryos from the emperor, a gift sword and 500 ryos from the shogunate, and 25 ryos from Matsudaira Higo no kami.

2nd version

https://fushigi-dono.diary.ru/p163570341.htm?oam#more1

Finally, I post the second version of the events in Ikeda-ya from Nagakura Shinpachi! Shmyrina_Anna already translated the first here , and here she explained why there are two of them. One version, dictated to the journalist (and generously edited and supplemented by him) was published in the Otaru Shimbun newspaper from March to June 1913 under the heading Shinsengumi Nagakura Shinpachi, and was later reprinted several times under the title Shinsengumi Tenmatsuki (which something like "Detailed Notes" or "Shinsengumi Fact Records"). And in 1998, all of a sudden, the very first lost memoirs were found (where and how they were found, for some reason, it’s not written anywhere), and they were published under the name Shinsengumi Senjo Nikki. ronin of the Bunkyu era). Thanks for them to Donna Anne (Lliotar) . So there is an opportunity to compare and feel the difference! The translation is not literal, but very close to the text, the style tried to preserve Nagakurin whenever possible. Unlike a journalist, he wrote in such a way that the three of us spent three days analyzing one proposal (post below) On June 6, 1, Genji A native of Omi Province named Omiya Shungoro (aka Masuya Kemon) held a horse harness shop on Shijou Kobashi Street. Shinsengumi was arrested of this type and taken to the barracks, where in the course of an investigation he gave his real name - Furutaka Shyungoro (actually he is Shyuntaro, but Nagakura says so) . During the interrogation, he stubbornly did not want to confess, so he was tortured, and in the end he confessed everything. According to Furutaki’s testimony, 10 people often visited his house, all like one of Choshu, and in his warehouse he kept all kinds of equipment for setting fire to the imperial palace. The implementation of their plan was scheduled for the 22nd day of 6 months - on a windy day they were going to set fire to the palace, capture Emperor Komei and take him to Yamaguchi Castle. In plotting this plot, people from Choshu were hiding in the vicinity of Shijou, as well as on Sanjou Street, in a hotel under the guise of the Minakuchi clan from Omi, etc. - Only about 300 people. From Furutaki's confession, all their intentions became clear, which Shinsengumi immediately reported to the head of the Aizu clan, Mr. Matsudaira Katamori. Utterly shocked Hijikata Toshizo, based on the testimony of Furutaki, led a detachment to Gion Kaiso, which is at the foot of the stairs of the Yasaka-jinja temple. Already at 7 o’clock in the afternoon (from 4 p.m. to 6 p.m. ), Shinsengumi arrived there and searched every corner of the teahouse, but they didn’t find anyone - apparently everyone had already escaped from there. Then they began to comb the entire area along the Kamogawa coast and received information that in the north, in the Ikeda-ya hotel near Sanjo Kobashi, perhaps Choshu was holding a secret meeting. Leaving a few people outside, Kondo Isami, Okita Soji, Nagakura Shinpachi and Todo Heiske entered the front door and found rifles, spears and other weapons that they tied together to confiscate. Entering the front hall, they called the owner Ikeda-ya and said: “Tonight we check all the hotels!” The owner got scared and rushed up the far stairs to the second floor, four Shinsenites immediately rushed after him, and there were about twenty Choshu, and all with swords at the ready. “You are arrested until the circumstances are clarified. If you resist, you will be ruthlessly killed, ”Kondo shouted in a thunderous voice. The rebels trembled with fear and stepped back, but then the bravest of them suddenly attacked. Okita instantly finished him off with one blow. Then the others rushed to the first floor, and Kondo immediately ordered them to follow. Light was burning in the lower rooms, and this became a big help for Shinsengumi, but soon Okita was forced to leave the battlefield due to his illness, so there were three of them left inside the hotel. Kondo held the defense in the far rooms, Nagakura guarded the area from the kitchen to the main entrance, Todo - access to the garden. Noticing that one of the rebels rushed to the front door, Nagakura chased after him. Near the exit, the fugitive pierced Tani Mantaro with a spear, and Nagakura finished off with a blow to the shoulder, after which he returned to his former place. When another man ran to the same exit, Nagakura caught up with him and cut him off the shoulder obliquely. Then one of the conspirators rushed towards the garden and disappeared into the restroom. Nagakura pierced the enemy through and through, he tried to draw his sword, but lost his strength and fell. Without waiting a minute, the Shinsenovets cut him with one blow. Todo Heiske was seriously injured by one of Choshu, blood pouring in his eyes, preventing him from fighting, and besides, his sword blade broke. Seeing this, Nagakura hastened to help Todo, intending to hit his opponent in the side, but he skillfully repelled the blow and switched to Shinpachi. Due to a severe wound, Todo was no longer able to continue the fight. Nagakura fought not for life, but for death. Kondo Isami noticed that Shinpachi nearly wounded three times, and wanted to come to his aid, but could not, because he himself in the depths of the room opposed many opponents. In the end, Nagakura defeated the enemy, cutting his shoulder. The four rebels laid down their arms and apologized, after which they were immediately connected. Nagakura’s hand was slightly injured, and the blade of the sword was chopped, so I had to take the katana of one of Choshu. At this moment, several people from Shinsengumi burst through the main entrance and began to search the hotel. Having broken the ceiling, one of the conspirators collapsed from the second floor, and Takeda Kanryusai immediately cut him down. All those who managed to run out into the street surrendered to the riot police. Shimada Kai crossed the spear with the enemy blade, and when the base of the spear was cut off, he instantly dealt with the enemy katana. Skirmishes also occurred in front of Ikeda-ya in the Sanjo Kobashi area. The owner of Ikeda-I was not tied up, as a result of which he untied several conspirators and allowed them to escape. Noticing this, Harada Sanosuke rushed after him and dealt with them with his spear. At this time, the vassals of Matsudaira Etтu no kami (Matsudaira Sadaaki) killed two Choshu - they died instantly. And the vassals of Matsudaira Higo no kami (Matsudaira Katamori) took the rebel from Choshu for the samurai of the Minakuti clan, and without becoming tied, they led him under arrest. On the way, the detainee slashed the warrior of the Aizu clan from the shoulder obliquely and rushed to run, but at the gates of the residence of Choshu he was caught and killed. Meanwhile, Shinsengumi arrested another 4 or 5 people from Choshu, as well as the owner of Ikeda-ya, and all, without exception, were taken to the city prefecture. After this, Matsudaira Higo-no-kami immediately reported the incident to the imperial court, where everyone was in great admiration. As a reward, Shinsengumi granted 300 ryos from the emperor, a gift sword and 500 ryos from the shogunate, and 25 ryos from Matsudaira Higo no kami. Etu-no kami and Higo-no kami - honorary titles given by the name of the provinces, something like "Count Higo." Well, now the pictures. This is the plan of the Ikeda-I hotel and the movement scheme of the Kondo and Hijikata groups:

The numbers indicate the size of the rooms in the tatami. Apparently, the administrator was sitting in the “cash desk”, and weapons were stored in the “closet”. The red arrow shows which stairs and where Kondo and the others climbed. Here the schematic is even better - if you hover over it with the mouse, you will see who was where.

On the second floor on the left is Okita, on the right is Kondo. On the first: at the entrance of Tani Mantaro and Takeda Kanryusai, at the exit to the courtyard - Todo, in the middle of the Nagakur corridor. Three others held the defense in the kindergarten behind the hotel, and they had the hardest time - there was open space, those who escaped could jump from anywhere in the Engava and attack from any direction. So Okuzawa died on the spot, Ando and Nitta later died of wounds. This is the very second floor:

Tiny Ikeda-ya:

Nagakura writes: "the light was on in the lower rooms" - there is not even just light, but an "eight-room lamp")) I looked for what it was and found it :

Well , it looks like this Ikeda-I these days:

The Gion Kaiso, which is mentioned in the text, is literally the “assembly hall” in Gion. There used to be such buildings both in cities and in villages - there people were going to discuss something or buy-sell, there were all kinds of trade missions, etc. Now at this place this is:

It is viewed from the temple, and if facing the temple’s gate, then (the former "chambers of commerce" is on the right):

On the site where I found a small description of this "assembly hall", it is said that next to it Shinsengumi were waiting for reinforcements from the Aizu clan, but they did not wait and decided to act independently.

#ikedaya #event #nagakura diary #fushigidono #translated #Translated from Russian #wip

10 notes · View notes