I would argue this might make xz safer mid-term. So much eyes on it. I’m not familiar with other solutions, but who’s to say the bad actor won’t try a similar trick elsewhere
![the background blur](https://lemmy.world/pictrs/image/5af7b4ae-1adc-44e4-87d5-81b46a8999ce.gif?thumbnail=256&format=webp)
![](https://lemmy.world/pictrs/image/5af7b4ae-1adc-44e4-87d5-81b46a8999ce.gif?thumbnail=1024&format=webp)
Or maybe training for a dance battle. There are the chicks from the Hilton Head Island Raptor Cam. I made a few other gifs in the comment section there
I live in Montpellier. It’s free for the whole metropole, meaning Montpellier and the 30 cities around it
I think all the bananas (and beans) are already in the picture
You can even see the decline in posts and votes before GPT became mainstream. This definitely look more like search engine failing to get rid of those cheap copycats.
I made a website to compare prices across regions for Nintendo Switch games. It started as a Google Spreadsheet but because of traffic I quickly had to move to a standalone website. Getting around 2M users per months now. I’m trying to keep the ads to a minimum, and I’m partnering with online stores for gift cards.
It’s the basic bricks (the framework) wefwef was built with. It’s a way of building « app » that feels native but are actually websites, with less troubles of adapting to different systems.
In this instance, it’s (almost) just a matter of using an option on the framework to tell it « Now look like an Android app rather then iOS »
If you are curious https://ionicframework.com/
From the fix, I believe the custom emojis were not double checked after a user submits a post. The post data was used to display the emojis, and thus allowing injection.
The fix now is to search the emojis in the custom emojis list from the backend rather than the user post.
It’s more likely an instance issue rather than a wefwef one. Try signing up into another one. Also, it’s time to charge your phone