Yes, certainly. It sounds like some/most members of the team don't understand the stylesheet architecture of your project and it's vital to sort that out ASAP. The more time passes, the harder it will get to get everything back on track.
Try to avoid finger-pointing and this shouldn't be a very hard conversation (assuming they aren't super stubborn).
As a side note, the fact that you first address this issue on the Fediverse and not in your team makes me think that maybe there are some underlying issues regarding trust and open communication. You might want to further look into that. Take it with a large grain of salt though. I don't really know anything about your team so it's likely that I overdramatize the situation.
That sounds like a pretty straight forward and simple conversation.
Do you do code reviews? Have code owners? If you (or a set of people you trust) were required to sign off on changes on the base files that aren't supposed to be changed willy-nilly, you could catch it before it went to main
If the code you have quoted is verbatim what you have tried, seems like you need to extract the parentheses and possibly a single or double quote, depending on the source css. The example source you have given has a single quote.
From Microsoft? Oh no... is this a blazor sales pitch?
Edit: not really. Of course he had to use it, but it wasn't too prominent. Didn't finish the video but server-side rendering seems to be the "future". I dunno... that doesn't give me a warm tingly feeling.
More specifically, he argued (and the recent and upcoming releases of most major frameworks agree) that rendering most content on the server with islands of client-side interactivity is the future.
That’s not necessarily a huge revelation, but the big difference from what people have been doing with PHP for decades is the level of integration and simplicity in mixing server-side and client-side code seamlessly so that a dev can choose the appropriate thing in each context and not have to go through a lot of effort when requirements change or scaling becomes an issue. I would say that this represents a new level of maturity in the “modern” web frameworks where devs can choose the right technology for every problem to serve their users best.
Does individual users send activities directly? I thought only users of your instance and remote federated instances send traffic to your instance, so this change would only affect data coming through from the larger instances?
Also, what’s happening with the original request while they remain in queue? Say for example if large-instance.com is sending 11 updates to your instance; while your back end server is processing the first 10, what’s happening with the 11th? Does it get put on hold while your back end churn, or does it get a 200 OK response, despite the request may be failed at a later date? Neither of which seems ideal — if the instance get put in a queue waiting for a response while you churn, or worst yet, if your backend fails and your buffer is waiting X seconds to time out each request, you’re going to hurt the global federation by holding up a spot in their out going federation queue; if the instance is sent with a 200 OK and your backend eventually fails, you’d lose data as the other instance wouldn’t know they’d need to retry.
A HTTP 200 response is sent immediately. There is a small risk of data loss but only during the time when rate limiting is happening. Most instances behave well and only send activities at a sensible rate but when things go wrong we need to avoid the bad effects caused by those that are mis-configured or under attack.
It's not a perfect solution. But the alternative - fail to accept some activities, causing them to retry later and us to slowly fall more and more behind - is worse.
Thanks for the clarification! I’m inclined to agree here, small risk of data loss but failing to receive updates all together during peak burst is probably much worse.
Learning HTML syntax is the simple part. The tedious part is learning which tags already exist, and which tags goes in which other tag (and which attributes they may (not) contain).
For that, always, ALWAYS go to the official HTML spec: WHATWG HTML.
HTML has not been maintained by WC3 (though they still do maintain CSS) and has been a "living standard" since HTML5 (2009-ish, IIRC).
I've read through the entire spec (using TTS, because only reading is boring) and learned a TON, because writing React straight out of the gate, without learning the HTML fundamentals first is a HUUUUGE pain.
FF124, Windows; What I see is grey and a loading icon.
Have you opened the Browser Console?
downloadable font: Glyph bbox was incorrect
While one would not expect that to cause such issues, depending on if you're using a SPA or what kind of bootstrapping you use, or a Firefox consequential issue, it may. What happens if you skip web fonts?
I can open the browser console, and I can context menu inspect elements, and it selects them in the inspector. So it seems like the DOM is being rendered and laid out, to an interactable level.
When I open CTRL+SHIFT+M it looks very funky and broken. No border, nothing rendered; only the resize handle, which remains usable. Using different Window to compare, there should be a border and border shadow. This makes me come back to the font issue, and makes me wonder if trying to render a faulty font brings Firefox into a broken render state.
Speaking of a “black hole” email address, are there any addresses set up for the purpose of catching spam? Like if Gmail had an address for spam that contributed to its spam detection.
The Stalwart mail server allows for that. They call them "spam traps".
Basically, it's a real email address that literally never gets used or referenced anywhere, thus assuring any email received is unsolicited by definition. Stalwart's spam engine uses any such email to help train the spam filter.
I can't imagine that Stalwart is only one implementing such a system.
I've never used Stalwart, but it's the email server I've selected should I decide to do what everyone tells me I shouldn't: run my own server for me, my wife, and the two domains we control. Their documentation is basically a master class in email.
“Spam trap” and “spam honeypot” are exactly the keywords to search for. I found a bunch of info about some services you can use to set them up. I’d recommend adding “-avoid” to your search filters because every email marketer has their own article titled “About Spam Traps and How to Avoid Them” which just pollutes search results if you’re actually looking to set up your own.
Web Development
Top