#test to image api

[insert-content]

a summar(ule)y of 196 culture

since the tumblr veterans have been kind enough to introduce us newbies to their site and culture, i think it is only fair that we explain the culture of our glorious former home to any tumblr users who might be interested in the #196 tag. keep in mind, all these things are based on my perspective of the situation.

first of all, some general information (that you might’ve already heard):

196 (r/196 on reddit) was a subreddit with only one (official) rule; "post before you leave." it was mainly a meme/shitposting sub, but it cultivated a large queer and left-leaning community. in protest of the recent api chances in reddit, 196 has shut down indefinitely until reddit reverts these changes.

now for some culture/references that you might come across

spronkus kronkus:

spronkus is this yellow, rabbit-like creature.

they were the mascot of our subreddit. their appearance can vary from images to image, but as far as i’m aware, their full outfit consists of a bandanna in the colours of the trans flag around their neck, a gun labelled as such (other wise you obviously wouldn’t know what you’re looking at), and an axe also coloured like the trans flag.

r/place:

this is a rare event on reddit where the entire website gets a huge white canvas and can start creating pixel art on it. 196 participated by collaboratively creating our mascot, spronkus with "196!" written next to them.

this version of the pixel art was recreated by me as i couldn't find a nice image of it. there were some changes between the first version and the end result, so this might not be exactly how it looked in the end

post titles/"rule":

reddit forces it's users to title every post they make. as most of the posts on 196 spoke for themselves, many user instead titled their posts "rule", to indicate that they followed the subreddit's only rule. some people also tried to make puns with the word or tried to include it in words that shared some letters (example: wor(ule)d).

anarcho-stripperism:

as the amount of cropped porn jokingly posted to the subreddit increased, the moderators decided that porn would be banned from the sub, with one exception: anarcho-stripperism. she made food fucking videos, in which she jokingly tested the fuckability of different food items (fruits, pasta, etc.)

bigotry showcase:

bigotry showcase was a post flair (basically the reddit equivalent of tags) on the subreddit and was later restricted to only be used on saturdays. under this flair people posted instances of different forms of bigotry to make fun it.

eating babies/hungryposting:

at some point, the subreddit started to pretend to like eating babies, which started a variety of memes regarding the subject. even a post flair called "hungrypost" was added because of this

goblinhog:

goblinhog is the most prominent and well-known member of the 196 moderation team. besides this, on 196 he was mostly known for changing people’s flair if you enjoyed him enough about it.

flairs:

flairs are little tags that are displayed under your name in posts or comments, they are also subreddit specific. most subreddits give their users a palette of preset flairs and the option to make your own custom flair. however, in 196 you only had the option to customize your flair during special events. if you wanted to customize your flair outside of those events (which was basically the entire time), you had to ask a mod to do it for you.

punching nazis:

from time to time, the same gif of a person with a nazi armband getting punched in the face, and promptly falling to the ground, was reposted to the subreddit. this became a sort of tradition.

discourse/drama

wasp discourse:

the wasp discourse was a one to two weeks long heated discussion that generally divided the subreddit into two factions. one side said that they were justified in killing wasps if they were attacked by them, while the other claimed that since wasps are just animals, they aren't aware of what they're doing in the same way humans are, and therefore should be spared.

drama about the british:

there was a time when jokes along the lines of "ew, british" became pretty frequent on the subreddit. as a response, some user claimed that this was akin to racism and tried to get others to stop with the jokes. a debate over whether or not it was important or necessary to stop followed afterwards.

pillar discourse:

this was a debate over which type of pillar should be considered the best (ionic; doric; corinthian). i have seen the question "which pillar is the best?" being used as a sort of greeting between 196 refugees on here.

related subreddits

195:

195 was the predecessor to 196, and also was a social experiment with the same premise as 196 (one rule, post before you leave). as the creators of 195 ended the experiment, the community wanted something with the same vibe to continue posting, and thus 196 was born.

197:

197 is another part of the 196 ecosystem and is commonly understood to be the more politically right-leaning and bigoted as 196, as some people who were banned from 196 continued posting there. besides that, the subreddits were essentially the same in terms of how they functioned.

19684:

this subreddit adds a second rule which banned all mentions of sex (that’s why it’s name is a pun on 1984). some people took this as banning all discussion of sexuality, which resulted in a community that was slightly less accepting of queer people. it is currently still up and running as the 196 moderation team wants a way to stay in contact with the community.

amendments to the posts:

u/femboy_expert:

another well-known 196 user. as the name suggests they're an expert on the subject of femboys, with their flair on 196 reading "phd in feminine boys". as the subreddit was somewhat obsessed with femboys, it's no wonder that they became popular.

u/shitcum_backup:

this was the main account of a pretty popular shitposter on the subreddit. although i didn't see them as much in the last few months, i remember them sometimes having a unique speaking pattern, in which they referred to themself in the third person.

u/monko74:

this user commented "Every day I thank god for not making me a r/196 celebrity," which led to many users of the subreddit treating them like a micro celebrity. there are even a few subreddits solely dedicated to u/monko74.

691:

a sister subreddit that inverts the rule of 196, here you would be (temporarily) banned for posting. some time ago the members of this sub initiated a rebellion/revolution against the bot who performed all the bans (roomba).

u/Smart_Calendar1874:

this wasn’t necessarily part of the subreddit, but it was a pretty popular meme. and since it’s getting posted on here again, and i know enough about it, i’ll add it to the post. this user made a post to r/AskReddit titled "How would you get a small cylinder (5.1in length, ~4.5in girth) unstuck from a mini M&Ms tube filled with butter and microwaved mashed banana? [sic]" it was pretty clear that they were referring to their penis, yet they continued to claim "it’s a cylinder," in the comment section. this lead to comments like "it is imperative that the cylinder […] remains unharmed," in response to people’s advice of cutting the m&m tube.

it's going to be very interesting to see which aspects of 196 culture are going to survive the tumblr migration, and which aspects won't be applicable on this site.

i'm obviously not the ultimate scholar on 196 lore. if i’ve missed or left out anything, or said something wrong, please comment it.

[zihua-art]

Business card design (FRONT)

Business card design (BACK)

[izicodes]

Sugary Scribbles | #8

Saturday 6th January 2024

IT'S BASICALLY WORKING (on larger screens)! My never-ending war on website responsiveness continues! I have a large screen and I stupidly only took into account of MY screen size. What I did do though is created a message for phone-table sizes because it just wouldn't make sense it working on really small devices - in my opinion~! But for now I will put this on hold because I am excited about my other project idea I came up with yesterday oops~!

This is my first project of the year and it's super adorable in my opinion! It paints, it erases, it deletes and it saves your artwork! Ticks all the boxes I made at the beginning of the project! Turned a simple 'Make a HTML painting webpage' into something more cuter and cool! Job well done! 😩🙌🏾💗

You can try it out (if you have a larger screen size), all that happens is the painting will be off the mouse direction a bit, sorry!

link to the Sugary-Scribbles web app! 🍡

Lastly, here is a cool drawing I made as I was testing the site~! I'm a better artist than this I swear, just not good using a mouse...

List of resources I used during the project

Figma - to plan the webpage

Canva: to make the header

Photopea: for further photo editing

RedKetchup: to colour pick quickly

CSS Animations: to add the zoom-in-n-out animation

MDN Canvas: to know what the element does properly

YouTube Tutorial: to get inspiration and extra help

Flaticon: for the icons and cursors

Html2canvas API: to turn the drawing into an image (tutorial)

That's all, have a nice day/night and happy coding! 🖤

[vague-humanoid]

For years, hashing technology has made it possible for platforms to automatically detect known child sexual abuse materials (CSAM) to stop kids from being retraumatized online. However, rapidly detecting new or unknown CSAM remained a bigger challenge for platforms as new victims continued to be victimized. Now, AI may be ready to change that.

Today, a prominent child safety organization, Thorn, in partnership with a leading cloud-based AI solutions provider, Hive, announced the release of an API expanding access to an AI model designed to flag unknown CSAM. It's the earliest use of AI technology striving to expose unreported CSAM at scale.

An expansion of Thorn's CSAM detection tool, Safer, the AI feature uses "advanced machine learning (ML) classification models" to "detect new or previously unreported CSAM," generating a "risk score to make human decisions easier and faster."

The model was trained in part using data from the National Center for Missing and Exploited Children (NCMEC) CyberTipline, relying on real CSAM data to detect patterns in harmful images and videos. Once suspected CSAM is flagged, a human reviewer remains in the loop to ensure oversight. It could potentially be used to probe suspected CSAM rings proliferating online.

It could also, of course, make mistakes, but Kevin Guo, Hive's CEO, told Ars that extensive testing was conducted to reduce false positives or negatives substantially. While he wouldn't share stats, he said that platforms would not be interested in a tool where "99 out of a hundred things the tool is flagging aren't correct."

[edwardos]

Attention Noticeably Beta 1.8 fans: I have a monumental piece of historic significance news.

This is not about something new that's coming out, but a discovery I made recently about old stuff in my development files. I found old screenshots I forgot I had that were made very early on while first developing the mod. That is what this post will be about.

That screenshot up there is the first screenshot I took in-game of this entire thing, in December 15th 2022, and that was taken a few hours less than exactly two years ago. It's currently NBODE's 2nd birthday.

This all just happened to coincidentally come together for me recently, when I was looking for things to post, just four days before the two-year anniversary, which I didn't even realize at the time was very quickly approaching. I was scouring my old build and screenshot folders more than usual, from back when I had to "reset" the mod folder to fix infrastructural issues in 2023 - which I did TWICE - and found out that I had more screenshots than I was dimly aware of.

When this happened, I knew that in a few days, it would be time to celebrate.

So here, two years after Noticeably Beta 1.8 officially started, let's look at some pieces of its very early development history in notes and images.

↑ This screenshot was created on the same day as the previous one, but further grass images in this post are from two days later, and then two plus five days later, and so on.

It was extremely primitive at the end of 2022, and I hadn't changed the healing system or the title in the top left corner yet. But one of the first things I ever did was work to fix Beta 1.7's terrible model for tall grass. My efforts temporarily made the grass white.

These images have - I think - never been shared on this microblog before this. I was so early into development and so paranoid about idea theft that I stayed private and/or cryptic for a while, and didn't make so much as a cryptic post with unexplained screenshots of the mod until April. It got only one note. This is that post.

So, I continued to mess around with the game's models. This struggle was still all in 2022.

On January 2nd the next year, I had even more trouble. Somehow I was randomly gaining tall grass items that could be placed down again, but would then not be the same thing as the grass that was already there. I still don't understand that one.

Jumping to the 23rd of January 2023, I discovered the API feature I wanted from ModLoader.AddOverride().

This proved to me that I could change textures of existing blocks with code in the mod as I wanted, and that I could properly enforce the difference between existing cobblestone and my new block called concrete. Scroll up to the picture with the crafting table again and you'll see what I mean. I was so happy to find this piece of functionality (especially while knowing that web searches and old forum posts just REFUSED to say anything about how to do it) I posted this outdated meme in my development channel.

Also for some reason while modding new blocks in, you have to set pickaxe speed effectiveness on them quite manually. Even after setting the material to "stone", you have to actually tell the code that pickaxes should actually do something efficiently do it. I had no idea why it was happening at first. This pic came shortly after my first confused pickaxe speed test. ↓

There's plenty more to see from this turbulent period of modding upheaval and history, and we don't have all day, so I'm going to post a blitz of seemingly random images with random gaps (in chronological order) with little or no description.

The first time I crafted soilstone.

A mess of early soilstone and cobblestone blocks.

I don't remember doing this. Evidently it was an item functionality test.

Early emerald ore generation, from back before I ensured that it didn't suck.

The first Sazmit I found in testing probably.

Even as I picked out images for and wrote for this, I found myself being impressed and amazed by how I was able to overcome challenges - all that time ago, while being such a novice - and how far this mod has come. There are plenty of images still left, so more individual posts on this era will be coming out on the blog as time goes on. And I haven't even gone into the second folder for this yet.

These images are all from the first four months. And I've been working on this mod, trying to craft and redefine most of everything there is in this base version into perfection for two years, with no release yet. It's been a hard journey from the start to all the way into the last month of 2024 as I write this, and I've pulled off some outstanding victories and easy yet smart victories over the code to make basic aspects of Beta 1.8, like fences and bookshelves, much better in that time. I even fixed a glaring oversight in Beta 1.8 or two.

As a quick note, development kind of went on longer than this, because in December of 2022 I studied for the mod ahead of time by playing hours of vanilla Beta 1.8.

I know you guys are patient, but I think it's really about time I finished Alpha 1.0.0 of this treasured Minecraft mod already, so I can try to make a public Modrinth page to host it and more people than just me and one friend can get to play this mod. I really want to watch other people play it. I'm super proud.

[frog707]

Project update

In June, when I started the jolt-jni open-source software project, I considered it a subsidiary project. However, it proved so absorbing that it soon soaked up most of my attention, leaving little for all my other projects.

This is surprising, since unlike most of my projects, it has no graphical component (yet) meaning no satisfying CGI images to enjoy (and perhaps share on social media).

Also unlike most of my projects, I was coding it from scratch, yet constrained by a preexisting API. In practice, that meant writing a ton of boring boilerplate. Prior to this I'd been scornful of the idea of using AI to generate code. But for generating boilerplate code, I can see that mechanical aids have their place.

Now that the library is about 80% complete, I've turned more of my attention to testing. My progress (measured in lines of code) is much slower. Some days I delete more code than I add. The good news is, I enjoy troubleshooting far more than coding.

For the record, here are the current statistics:

+ 1472 commits

+ Overall 48K lines of code (excluding comments and blanks)

+ 29K lines of Java (including 8K lines of tests and examples)

+ 17K lines of C++

[leftistscum]

I AM CURSING YOU FUCKBAGS TO 1000 YEARS OF OWOFIED NONSENSE. I HAVE TO SUFFER, NOW YOU HAVE TO SUFFER WITH ME.

Update:

All this effort and it doesn't even work. I'm not mad, just disappointed. Current theory is that I didn't include an important part of it in the while loop. The bot scans new posts, and I'm not gonna re-post this for the second time. It's only been actually tested two or three times including this try, and I'm keeping this as a sort of devlog. Update 2:

I restarted the OAuth apps that I made earlier today (an OAuth callback server to catch the keys, and another OAuth thing to generate the Authorization verifier). I worked almost all day to get these two to work together. The API ended up sending this error, and I don't know what it means, but it doesn't throw any errors client-side. Here's the error it throws. {'meta': {'status': 429, 'msg': 'Limit Exceeded'}, 'response': [], 'errors': [{'title': 'Limit Exceeded', 'code': 0, 'detail': 'Minor hiccup. Try again.'}]} Like, okay, great. Now I gotta actually look at the documentation and find out what this magic gibberish means, because this could relate to all those times I tried to authenticate, OR I hit the daily limit on posts seen by my bot, which I highly doubt. Update 2.5 after some research, I've learned absolutely nothing. That error code is a giant ball of nothing that basically says I exceeded a rate limit, but doesn't give any explanation as to which rate I exceeded. Thanks, Tumblr. At least Reddit threw client side errors that you didn't have to go to a broken API console to see. Fuck all of you, and I'll see you tomorrow.

Side note: I am surviving off one breakfast pizza from Casey's, one Pipeline Punch, one grape flavored 3D, 4mg Estradiol, 50mg Spironolactone, and I currently have 100mg Progesterone dissolving in my stomach, which at this point, might actually kill me. It's only 9:36 at the time of writing this, but it feels like I've been working on this for days. This is to say that I may have missed something super obvious, and if that's the case, well, I'll leave tomorrows problems to tomorrow's me.

Update 3

Just woke up and re-ran all the assorted programs just to get a fresh start. I'm still getting that error code, but more importantly, my access token and secret changed? I'm not expert when it comes to stuff like this, but I though tokens and secrets are constant and specific to apps. I can't actually test this thing until the API lets me through. Update 3.5

Found the error code. It wasn't way too hard, but it means my bot probably did something way too much yesterday and I have no idea what. It works on the server's clock and goes by callendar day. This means that if a bot hits the error code at 11:59 PM, it can hit it again at 12:00 AM. For an error 429 to happen, any one of the following has to trigger it.

300 API calls per minute, per IP address.

18,000 API calls per hour, per IP address.

432,000 API calls per day, per IP address.

1,000 API calls per hour, per consumer key.

5,000 API calls per day, per consumer key.

250 new published posts (including reblogs) per day, per user.

250 images uploaded per day, per user.

200 follows per day, per user.

1,000 likes per day, per user.

10 new blogs per day, per user.

20 videos uploaded per day, per user.

60 minutes of total video uploaded per day, per user.

So I can't test this until the server's calendar deems it a new day Update 4

It still doesn't work, but I am one step closer. Because of Tumblr's broken-ass console, I've had to find an alternate way to get an OAuth key. It turns out I was using a temporary access key, which is why it changed when I re-ran everything. I had to do this by using two other scripts. One of them is Tumblr's interactive console on Github , and the other one was a Yaml parser because boy do they like to encrypt. This has been my morning so far. Day two and 5 scripts later, just to finally have something that I should've had at the start.

Update 4.5

I FINALLY GOT AN API RESPONSE!!! LET'S FUCKING GOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

Update 4.5.5

I have implemented a feature that makes the thing wait for a second then search for any comments with a timestamp older than the last time it waited and has the right keyword in the 196 tag. I have obviously accidentally wasted all my API tries today, but testing begins again tomorrow. You will fear my wrath soon enough. Update 5

Decided to check up on the bot, and ran straight into this wall of text. It looks like blog info? Some of those links take me to profile headers. This isn't a static thing either, it updates every 20 seconds like clockwork. Because I made it update every 20 seconds like clockwork. I think this means it's testing time. Wish me luck. Breaking News. Didn't work, but we're a lil bit closer. Again.

[equipe]

Notes de mise à jour

🌟 Nouveautés

Sur le Web, les Coches arc-en-ciel sont à présent visibles dans l'en-tête des pages de blogs, en complément de leur présence dans les billets eux-mêmes.

Sur le Web, la mention "0 note" est dorénavant affichée dans le bas d'un billet ne comportant aucune réaction. Ce libellé cliquable était auparavant masqué dans cette configuration.

Lors de l'utilisation de l'option de partage "Copier le lien", les adresses at.tumblr.com ne sont désormais plus utilisées pour créer des liens au format court.

Sur le Web mobile, se rendre sur l'URL d'un billet en particulier montre maintenant le contenu de ce dernier tout en masquant l'en-tête du blog dans la partie haute.

En réponse à une requête formulée ici, nous avons ajouté le lien vers l'image de l'avatar dans les éléments du format NPF fournis par notre API. Cette fonctionnalité est particulièrement utile pour les personnes qui souhaitent utiliser NPF / JSON dans leurs thèmes de blog.

Certains utilisateurs expérimentent en ce moment des libellés exempts d'emojis dans les onglets du tableau de bord.

🛠️ Correctifs

Sur le Web mobile, le contour bleu qui apparaissait brièvement à l'ouverture d'une image dans un billet n'est à présent plus visible.

Sur le Web mobile toujours, le bouton de fermeture d'une image affichée en mode lightbox est à présent bien proposé.

Sur le Web mobile toujours et encore, appuyer sur "Partager" dans le pop-up de célébration surgissant lors de la publication d'un billet pouvait afficher la fenêtre de partage en dessous du pop-up et la rendait ainsi inutilisable.

Le nouvel éditeur de billets sur le Web comptait les balises HTML lors du calcul de la taille d'une citation. Le nombre affiché à présent reflète davantage la réalité.

Sur le Web, enregistrer la modification d'un billet depuis le tableau de bord ne provoque plus le rechargement de la page.

Dans le formulaire destiné au Support, il est à présent nécessaire de compléter le test reCAPTCHA pour que le bouton "Suivant" soit activé.

Correction d'un bug dans la fonction Recherche qui pouvait ne donner aucun résultat lorsque le chiffre "0" était utilisé dans une requête.

Correction d'un problème sur le Web qui pouvait désolidariser le média rattaché normalement sur le côté lors du clic sur l'espace vierge du bord droit d'une page.

Correction sur le Web d'une anomalie connexe : un média rattaché sur le côté d'une page de blog pouvait chevaucher la barre de défilement de ce dernier.

Correction sur le Web d'un problème qui pouvait faire disparaître le paramètre d'affichage des coches lorsqu'il était désactivé.

Lors de la consultation d'un onglet spécifique sur le Web, ce dernier est maintenant centré dans la barre d'onglets plutôt que de se retrouver potentiellement masqué dans la liste déroulante.

Correction d'une anomalie qui avait provoqué le retour des coches bleues en lieu et places de coches arc-en-ciel.

Correction d'un bug qui rendait invisibles tous les nouveaux commentaires ajoutés à des billets.

🚧 En cours

Un bug pouvait se produire dans le fil Abonnements de l'application iOS et provoquer le passage automatique d'un lot de billets à un autre lors de la navigation, ce qui en perturbait la fluidité. Le bug est à présent corrigé et la mise à jour devrait être disponible très prochainement.

🌱 Prochainement

L'application Android permettra bientôt de glisser/déplacer les tags afin de les réorganiser dans un billet.

Nos équipes travaillent à l'ajout de fonctions permettant de faire pivoter ou de rogner les images dans l'éditeur d'images de l'application !

Nos équipes sont informées d'un problème dans l'application Android qui provoque un chargement infini de l'onglet "Pour vous". Fermer et relancer l'application permet de contourner ce problème, mais un correctif en bonne et due forme est en cours.

Nous avons également remarqué que l'option permettant d'indiquer qui peut activer Blaze sur vos billets est visible dans l'application iOS, sans pour autant être encore opérationnelle. Cette fonctionnalité est en cours de finalisation, nous vous en dirons plus prochainement !

👻🧀🍪🐴

Vous rencontrez un problème ? Écrivez-nous (en anglais) et nous reviendrons vers vous aussi vite que possible !

Vous souhaitez nous faire part de vos commentaires ? Rendez-nous visite sur le blog Work in Progress et participez aux discussions de la Communauté !

[usafphantom2]

USA signals return of Turkey in the F-35 program

Fernando Valduga By Fernando Valduga 01/30/2024 - 20:17in Military

The first Turkish F-35 fighter at the ceremony held at Lockheed Martin in Forth Worth, Texas, United States, on June 21, 2018. (Photo: Atilgan Ozdil/Anadolu Agency/Getty Images)

The United States is signaling the possibility of Turkey returning to the F-35 program, as long as the issue of the Russian S-400 anti-aircraft defense system is resolved.

During an exclusive interview with the Turkish media, Acting Deputy Secretary of State Victoria Nuland revealed that the U.S. is open to Turkey's reintegration into the F-35 fighter program, subject to the resolution of the controversy related to the Turkish acquisition of Russia's S-400 anti-aircraft defense system.

Nuland recognized the complexity of the diplomacy involved, stating: "We were in the process of negotiating the sale of the Patriot missile system, and while these negotiations were underway, Turkey went down another path." She emphasized that the resolution of the S-400 issue is a precondition for Turkey's reintegration into the F-35 family, emphasizing the importance of ensuring the maintenance of a solid air defense capability by Turkey.

The statement was made during Nuland's visit to Turkey on Sunday, with the main objective of "reinvigorating" the ties between the two nations. The delicate balance between addressing security concerns and promoting collaboration served as a backdrop for their discussions.

“Obviously, if we can solve this issue of the S-400, which we would like to do, the US would be delighted to receive [Turkey] back to the F-35 family. But we have to solve this other issue first,” Nuland told Turkish television CNNTurk on Monday.

The visit takes place a few days after Ankara ratified Sweden's accession to NATO and Washington approved the sale of F-16 fighters to the Turkish military.

Nuland addressed the ongoing approval process in Congress for the acquisition of U.S.-made F-16 fighters and modernization kits, highlighting efforts to persuade lawmakers. She emphasized the importance of Turkey's development of the F-16 fleet for the safety of the United States and argued that Turkey's active participation is crucial for an equitable distribution of the burden among allies.

As diplomatic efforts intensify, Turkey's potential return to the F-35 program remains dependent on the successful resolution of the S-400 issue, reflecting the intricate interaction between security considerations and strategic partnerships.

But the acquisition of the F-35 may be more complex. Turkey was expelled from the consortium that manufactures the new generation of F-35 poacher fighters in 2020, under the Anti-Adversaries of America Act through Sanctions (CAATSA), after acquiring Russia's S-400 anti-missile defense system. CAATSA was approved by an overwhelming majority by Congress in 2017 and introduces sanctions on any significant transactions with Russia.

Tags: Military AviationF-35 Lightning IITAF - Turkish Air Force / Turkish Air Force

Sharing

tweet

Fernando Valduga

Fernando Valduga

Aviation photographer and pilot since 1992, he has participated in several events and air operations, such as Cruzex, AirVenture, Dayton Airshow and FIDAE. He has works published in specialized aviation magazines in Brazil and abroad. He uses Canon equipment during his photographic work in the world of aviation.

Related news

HELICOPTERS

IMAGES: USAF deploys Jolly Green II in Japan

30/01/2024 - 19:00

MILITARY

Senegal wants to buy South Korean FA-50 jets

30/01/2024 - 18:24

MILITARY

Lockheed Martin delivers 75º APY-9 radar for the E-2D Advanced Hawkeye built by Northrop Grumman

30/01/2024 - 16:00

MILITARY

UAS Aerosonde of Textron Systems performs operational flight from a Coastal Combat Ship

30/01/2024 - 14:00

Aurora's Liberty Lifter X-plane advanced in the preliminary tests.

MILITARY

Aurora modifies the design of the large Liberty Lifter aircraft

30/01/2024 - 09:00

MILITARY

Argentina decides to buy 24 American F-16 fighters instead of Chinese JF-17 jets

30/01/2024 - 06:00

[simply-sithel]

My dudes... I don't know if I'm the last one to learn this, but I come bearing good news! Google's Apps Script is amazing and makes Spreadsheets & Slides so much more powerful!

Tumblr is hardly the best platform to talk about code on but this was a game changer! As a minor helper on @renegadepublishing's yearly exchange, my scripts let me keep up with the growing quantity of entries and while I only figured it out at the end of this year's labors, it will be so very, very, very helpful for next year's.

Will tuck further ravings under the cut but the short of it is that it (A) let me programmatically pull deets from AO3 to enrich final report and (B) let me programmatically fill the results slide show with data.

Coherently flowing prose often fail me when shifting to a technical discussion, so to break down the work:

this was all in JavaScript. I obviously love Kotlin more these days, but it felt painless/rather accessible being in JS

the primary 'key' passed around for the entries (when participents submitted updates and final entries) tended to just be the fic URL (plus gifter/giftee names) - a good UUID but carries no meta info

almost (tho not all) of the entries were hosted on AO3 which made programatic scraping possible

we definitely needed the author & fic name... which required visiting the page. And once you're on the page, why not grab more details? In the end we wound up scraping: title, author, last update, word count, fandom, rating. And while there's more one could collect, we lacked the space to visually display it along with the results. Remember-- the point is the typesetting!

Apps Script let you make URL requests [getContent]

I used the Cheerio library to process the page's contents and let me comb through it using jQuery. Link goes to GitHub page, which has the Script ID you'll need to import it in the Libraries section.

I found the Google Sheets APIs easy enough to read/work with -- just lots of arrays, really. Also, the quotas that you get seem generous to me (for a free product)

AO3 specific note : had to append "?view_adult=true" to the URLs if I wanted to bypass that check screen, but I also had to handle locked fic, which keep you at a reduced info lock screen. Be sure to test E rated & locked fic when drafting your script (Incognito Window is your friend)

Here is the Gist of the pictured script-- it was a 'round 2' edit where I went back and pulled Rating & Locked status : [LINK]

The above refers mostly to the Sheets side of things. The other most magical feature was the population of Slides w/ sheet data!

Notes as follows:

images are my current weakness-- had to go in later and adjust/layout/upload images manually. SUPER LAME. Next time I'm going to dig into pulling images from the drive...

I was able to embed links programmatically into the slides but it was VERY HACKY code. The generation of the PDF links was still a manual task, and while I imagine I could script that, sounds hairy (I want to avoid all things Auth)

The {{name_pattern}} was/is only a stylistic choice. Doing a find & replace on something so distinct is safest tho.

I did not use Alt Text on my things but I think going forward, it would be how I'd ID/address the non-string replacement actions (finding the right shape to anchor a URL link on was finicky the way I did it)

Here is my (very messy!) script for populating the slides: [LINK]

For next time:

using a script to pull tags/fandoms/pairings will make the gifter/giftee pairing process sooooo much smoother (so far it's been very manual!! Bless @aetherseer's tenacity!)

I need to figure out image imports/population of the slides... ignoring any aspect ratio/size issues

[corbindavenport]

Introducing Alt Text Creator

Images on web pages are supposed to have alternate text, which gives screen readers, search engines, and other tools a text description of the image. Alt text is critical for accessibility and search engine optimization (SEO), but it can also be time-consuming, which is why I am releasing Alt Text Creator!

Alt Text Creator is a new browser extension for Mozilla Firefox and Google Chrome (and other browsers that can install from the Chrome Web Store) that automatically generates alt text for image using the OpenAI GPT-4 with Vision AI. You just right-click any image, select "Create Alt Text" in the context menu, and a few seconds later the result will appear in a notification. The alt text is automatically copied to your clipboard, so it doesn't interrupt your workflow with another button to click.

I've been using a prototype version of this extension for about three months (my day job is News Editor at How-To Geek), and I've been impressed by how well the GPT-4 AI model describes text. I usually don't need to tweak the result at all, except to make it more specific. If you're curious about the AI prompt and interaction, you can check out the source code. Alt Text Creator also uses the "Low Resolution" mode and saves a local cache of responses to reduce usage costs.

I found at least one other browser extension with similar functionality, but Alt Text Creator is unique for two reasons. First, it uses your own OpenAI API key that you provide. That means the initial setup is a bit more annoying, but the cost is based on usage and billed directly through OpenAI. There's no recurring subscription, and ChatGPT Plus is not required. In my own testing, creating alt text for a single image costs under $0.01. Second, the extension uses as few permissions as possible—it doesn't even have access to your current tab, just the image you select.

This is more of a niche tool than my other projects, but it's something that has made my work a bit less annoying, and it might help a few other people too. I might try to add support for other AI backends in the future, but I consider this extension feature-complete in its current state.

Download for Google Chrome

Download for Mozilla Firefox

[mariacallous]

In the weeks following the release of OpenAI’s viral chatbot ChatGPT late last year, Google AI chief Jeff Dean expressed concern that deploying a conversational search engine too quickly might pose a reputational risk for Alphabet. But last week Google announced its own chatbot, Bard, which in its first demo made a factual error about the James Webb Space Telescope.

Also last week, Microsoft integrated ChatGPT-based technology into Bing search results. Sarah Bird, Microsoft’s head of responsible AI, acknowledged that the bot could still “hallucinate” untrue information but said the technology had been made more reliable. In the days that followed, Bing claimed that running was invented in the 1700s and tried to convince one user that the year is 2022.

Alex Hanna sees a familiar pattern in these events—financial incentives to rapidly commercialize AI outweighing concerns about safety or ethics. There isn’t much money in responsibility or safety, but there’s plenty in overhyping the technology, says Hanna, who previously worked on Google’s Ethical AI team and is now head of research at nonprofit Distributed AI Research.

The race to make large language models—AI systems trained on massive amounts of data from the web to work with text—and the movement to make ethics a core part of the AI design process began around the same time. In 2018, Google launched the language model BERT, and before long Meta, Microsoft, and Nvidia had released similar projects based on the AI that is now part of Google search results. Also in 2018, Google adopted AI ethics principles said to limit future projects. Since then, researchers have warned that large language models carry heightened ethical risks and can spew or even intensify toxic, hateful speech. These models are also predisposed to making things up.

As startups and tech giants have attempted to build competitors to ChatGPT, some in the industry wonder whether the bot has shifted perceptions for when it’s acceptable or ethical to deploy AI powerful enough to generate realistic text and images.

OpenAI’s process for releasing models has changed in the past few years. Executives said the text generator GPT-2 was released in stages over months in 2019 due to fear of misuse and its impact on society (that strategy was criticized by some as a  publicity stunt). In 2020, the training process for its more powerful successor, GPT-3, was well documented in public, but less than two months later OpenAI began commercializing the technology through an API for developers. By November 2022, the ChatGPT release process included no technical paper or research publication, only a blog post, a demo, and soon a subscription plan.

Irene Solaiman, policy director at open source AI startup Hugging Face, believes outside pressure can help hold AI systems like ChatGPT to account. She is working with people in academia and industry to create ways for nonexperts to perform tests on text and image generators to evaluate bias and other problems. If outsiders can probe AI systems, companies will no longer have an excuse to avoid testing for things like skewed outputs or climate impacts, says Solaiman, who previously worked at OpenAI on reducing the system’s toxicity. 

Each evaluation is a window into an AI model, Solaiman says, not a perfect readout of how it will always perform. But she hopes to make it possible to identify and stop harms that AI can cause because alarming cases have already arisen, including players of the game AI Dungeon using GPT-3 to generate text describing sex scenes involving children. “That’s an extreme case of what we can’t afford to let happen,” Solaiman says.

Solaiman��s latest research at Hugging Face found that major tech companies have taken an increasingly closed approach to the generative models they released from 2018 to 2022. That trend accelerated with Alphabet’s AI teams at Google and DeepMind, and more widely across companies working on AI after the staged release of GPT-2. Companies that guard their breakthroughs as trade secrets can also make the forefront of AI less accessible for marginalized researchers with few resources, Solaiman says.

As more money gets shoveled into large language models, closed releases are reversing the trend seen throughout the history of the field of natural language processing. Researchers have traditionally shared details about training data sets, parameter weights, and code to promote reproducibility of results. “We have increasingly little knowledge about what database systems were trained on or how they were evaluated, especially for the most powerful systems being released as products,” says Alex Tamkin, a Stanford University PhD student whose work focuses on large language models.

He credits people in the field of AI ethics with raising public consciousness about why it’s dangerous to move fast and break things when technology is deployed to billions of people. Without that work in recent years, things could be a lot worse.

In fall 2020, Tamkin co-led a symposium with OpenAI’s policy director, Miles Brundage, about the societal impact of large language models. The interdisciplinary group emphasized the need for industry leaders to set ethical standards and take steps like running bias evaluations before deployment and avoiding certain use cases.

Tamkin believes external AI auditing services need to grow alongside the companies building on AI because internal evaluations tend to fall short. He believes participatory methods of evaluation that include community members and other stakeholders have great potential to increase democratic participation in the creation of AI models.

Merve Hickok, who is a research director at an AI ethics and policy center at the University of Michigan, says trying to get companies to put aside or puncture AI hype, regulate themselves, and adopt ethics principles isn’t enough. Protecting human rights means moving past conversations about what’s ethical and into conversations about what’s legal, she says.

Hickok and Hanna of DAIR are both watching the European Union finalize its AI Act this year to see how it treats models that generate text and imagery. Hickok said she’s especially interested in seeing how European lawmakers treat liability for harm involving models created by companies like Google, Microsoft, and OpenAI.

“Some things need to be mandated because we have seen over and over again that if not mandated, these companies continue to break things and continue to push for profit over rights, and profit over communities,” Hickok says.

While policy gets hashed out in Brussels, the stakes remain high. A day after the Bard demo mistake, a drop in Alphabet’s stock price shaved about $100 billion in market cap. “It’s the first time I’ve seen this destruction of wealth because of a large language model error on that scale,” says Hanna. She is not optimistic this will convince the company to slow its rush to launch, however. “My guess is that it’s not really going to be a cautionary tale.”

[adafruit]

ESP32-S3 moon phase clock test on 2.1" round TFT display 🌜🌚🖥️

Now that we have somewhat-kinda-sorta working support for RGB TFT displays on the ESP32-S3 - shout out to Jepler, who is doing the hard work over in this PR https://github.com/adafruit/circuitpython/pull/8351 - its time to test it with wifi too! That's right, the S3 can do wifi and these big displays at once, and CircuitPython is a beautiful framework for it since its so fast to iterate. This code snippet is based on PaintYourDragon's moon clock code here https://learn.adafruit.com/moon-phase-clock-for-adafruit-matrixportal but pared down for testing. We get the geolocation from IP, then look up the moon phase. Currently we just hardcoded it to display today's phase, but the next step is generating ~28 different phase images, and we'll display the one for the current evening as the API informs us.

[metaflamedragon]

Twitter paid endpoint

well, I think this says it all great job with user-friendliness, twitter! other websites let me use their API to multi-post, meanwhile twitter's endpoints are locked behind big money. Anyway, I'm MetaflameDragon pretty much everywhere I can be (tumblr & meow rn). Feel free to follow me :3 (also, test post 2, image version)

Posted using PostyBirb

[rafael-salazar]

OpenAI’s GPT-4 exhibits “human-level performance” on professional benchmarks

Multimodal AI model can process images and text, pass bar exams. OpenAI plans to release GPT-4’s text capability through ChatGPT and its commercial API, but with a waitlist at first. GPT-4 is currently available to subscribers of ChatGPT Plus. Also, the firm is testing GPT-4’s image input capability with a single partner, Be My Eyes, an upcoming smartphone app that can recognize a scene and…

[inn0vatia]

Internet marketers turn to Delhi-based SEO companies for quality services

An online presence cannot be successful without search engine optimization (SEO). SEO companies in Delhi are no exception. With the right SEO company, businesses can increase their visibility on search engines, improve their website’s ranking, and drive more traffic to their website. This essay will discuss the benefits of hiring an SEO company in Delhi and why it is important for businesses to do so.

A Delhi SEO Company's Benefits

Hiring an SEO company in Delhi can provide businesses with a number of benefits. Firstly, an SEO company can help businesses optimize their website for search engines. This includes optimizing content, images, and videos for better visibility on search engine results pages. Additionally, an SEO company can help businesses create content that is optimized for search engines, as well as create backlinks to other websites to increase their website’s ranking.

Another benefit of hiring an SEO company in Delhi is that they can help businesses stay up-to-date with the latest SEO trends and techniques. SEO is constantly changing, and an experienced SEO company can help businesses stay ahead of the curve. An SEO company can also provide businesses with valuable insights into their website’s performance and suggest ways to improve it.

Why It Is Important for Businesses to Hire an SEO Company in Delhi

It is important for businesses to hire an SEO company in Delhi because it can help them increase their visibility on search engines. With the right SEO strategies, businesses can improve their website’s ranking and drive more traffic to their website. As a result, a business may be able to generate more leads and sales. Additionally, an SEO company can help businesses stay ahead of the competition by providing them with valuable insights into their website’s performance and suggesting ways to improve it.

Mobile App Development Agency in Delhi

Mobile app development is an ever-growing industry in Delhi, India. With the increasing demand for mobile apps, many mobile app development agencies have been established in the city. This essay will discuss the benefits of working with a mobile app development agency in Delhi and the various services they offer.

Advantages of Working with a Mobile App Development Agency in Delhi

Working with a mobile app development agency in Delhi has many advantages. Firstly, they have the expertise and experience to develop high-quality apps that meet the needs of their clients. They are also well-versed in the latest technologies and trends, which allows them to create innovative and cutting-edge apps. Additionally, they have access to a wide range of resources, such as experienced developers, designers, and testers, which helps them to create apps quickly and efficiently. Furthermore, they are able to provide their clients with comprehensive support throughout the entire development process.

Services Offered by Mobile App Development Agencies in Delhi

Mobile app development agencies in Delhi offer a wide range of services. These include designing and developing custom mobile apps, providing maintenance and support services, and integrating third-party APIs. They also offer testing services to ensure that the apps are bug-free and perform optimally on different devices. Additionally, they can help clients with marketing and promotion of their apps, as well as provide analytics and insights into user behaviour.

Conclusion

In conclusion, working with a mobile app development agency in Delhi has many advantages. They have the expertise and resources to develop high-quality apps that meet the needs of their clients. Additionally, they offer a wide range of services, such as designing and developing custom apps, providing maintenance and support services, and integrating third-party APIs. By working with a mobile app development agency in Delhi, businesses can ensure that their apps are developed quickly and efficiently, while also receiving comprehensive support throughout the entire process.