As someone who lives in Antwerp, this museum is my number one recommendation for people visiting the city.
It is also a Unesco World Heritage site, which is very unusual for a museum. But that's because the museum occupies what historically was a printing business stretching back many many generations who had -- fortunately -- a bit of a hoarding streak.
Well worth a visit. While you're at it, 'Goodie Foodie' on the same square as the museum serves the best pancakes in the city.
Plenty of advice here, which I'm certain is well intended, but it feels like we're victim blaming here.
Things like "you cannot mix marketing and transactional email" are good advice, but they do nothing if you're using different subdomains but the same infrastructure (IP address) to send them out.
Microsoft is simply trying to squeeze smaller operators out of the market.
I run an open source project, we send out transaction emails from ome subdomain, and a newsletter to 50K+ subscribers once every 3 months.
I can't afford to pay for different/dedicated IO addresses for each. We use Scaleway for email delivery and it's constant trouble with two providers: qq.com who don't give a damn about non-chinese senders, and Microsoft, who are simply trying to break the ipen internet.
Before, we were on AWS SES. Guess what, we didn't even bother using different subdomains. We also didn't have dedicated IPs. Yet Microsoft did not block us because the sender IP was AWS.
It's pay to play, as simple as that.
Fortunately, we're an open source project, not a business. So when people reach out, I simply explain to them that they have chosen a mail provider that is openly hostile to small volunteer-run projects like us and that that choice has consequences. No emails for you.
IMHO we need to be more vocal about what's really going on here (the rent-seeking on the open internet by big tech), and less victim blaming (what about dns-sec).
No matter how hard I try, I cannot make two pairs of jeans that are identical.
Same pattern, same denim, same person making them (me), they don't fit/feel the same.
Consistent results when using fabric is hard. Also keep in mind that good denim is practically sheet metal in comparison to most fabrics, so on one hand easier to get consistent results, but on the other hand, even small differences are more noticeable than something lighter or (god forbid) stretchy.
You cannot just engineer your way out of some of the challenges inherit in garment construction (trust me, Ive tried).
The title says "France rejects backdoor mandate" but TFA makes it clear that France is not a hive-mind:
- The rejection was by the French National Assembly (think parliament/congres)
- Ths happened despite pressure from the internal ministry (the government)
I find it interesting that it is often a similar story at the EU level where the European Parliament puts a stop to the worst impulses of the European Commission.
For a real-worl use case, look towards the 'script' processor in Elastic' Beats family of data shippers [1] (example is from Metricbeat but it exists in other Beats too)
They can be configured to mutate the data with some basic DSL syntax, but if you have more advanced needs, you can break out to JavaScript and transform the JSON any way you want.
This is very useful because now any transformation becomes possible. And because this is the user of your product who writes that JavaScript more as configuration than code.
And since there's no build step, it is just part if the configuration loaded at startup.
I've been working on something to handle the "plumbing for your observability". It's a way to collect, stream, and route observability data that can get it from and into a wide variety of systems.
It's not targeted at the 'cloud native' crowd, but rather more at traditional on-prem infra.
It is all manageable via an API and provides a Kafka API for streaming data (RedPanda under the hood).
I think there's a bigger issue going on here.
I too have received the same email for my open source project (1) which also was on Vercel's sponsorship deal.
A little Googling shows others piping up in the last couple of hours who received a similar message (2).
What seems odd is that they make it sound like the deal 'expired'. But I find it more than a bit curious that all the reports I find about this are from the last couple of hours, all expiring at the exact same date (14 June).
Given that Vercel no longer offers sponsorship (3), this feels like they decided to revoke the deal, and offer a 6-month credit to ease the transition.
Obviously, I am appreciative of the free service I've received, but the messaging about these changes could be a lot more honest IMHO.
The English summary focuses on the move from MS Office to LibreOffice (it's a post on the Document Foundation blog, so it makes sense that this is their focus), but the original German press release (1) lists 6 pillars:
- Switching from Microsoft Office to LibreOffice
- Switching the operating system from Microsoft Windows to Linux
- Collaboration within the state administration and with external parties: Use of the open source products Nextcloud, Open Xchange/Thunderbird in conjunction with the Univention AD connector to replace Microsoft Sharepoint and Microsoft Exchange/Outlook
- Conception of an open source based directory service to replace Microsoft Active Directory
- Inventory of specialist procedures regarding compatibility and interoperability with LibreOffice and Linux
- Development of an open source based telephony solution to replace Telekom-Flexport
So it's a good bit more ambitious than replacing MS Office.
> My idea was that surely it's possible to write a bunch of markdown, and then have that get wrapped in a bunch of JSX tags that come pre-styled, using the styles of your existing repo? For example, what I expected was to be able to write *test* (Markdown for bold) and then get a component that looked like<Bold>test</Bold> where <Bold> is a library-defined React component
It surely is possible, so perhaps I can share some links if others are wondering the same thing.
If you like to roll your own solution for that, you can use the unified ecosystem: https://unifiedjs.com/
However, if you want JSX just do what everyone does and reach for MDX:
https://mdxjs.com/
> We thought this would be a no-brainer and that there would be some CMS/SSG libraries out there that made this Markdown conversion process easy and facilitated integration with any number of frontend frameworks.
It is also a Unesco World Heritage site, which is very unusual for a museum. But that's because the museum occupies what historically was a printing business stretching back many many generations who had -- fortunately -- a bit of a hoarding streak.
Well worth a visit. While you're at it, 'Goodie Foodie' on the same square as the museum serves the best pancakes in the city.