#html border

[selysie]

personal bworders ki made 04 metadata mostly 04 myswelf 02 use, bwut kyu guys cwan use it too! (⁠*^ω^*⁠)

(pt: personal borders i made for metadata mostly for myself to use, but you guys can use it too! /end pt)

don't claim dem as kyurs pawlease !! nd don't use thy pwink & black dividers since it's not free 02 use ,,,, (⁠;⁠;⁠;⁠・⁠_⁠・⁠)

(pt: don't claim them as yours please!! and don't use the pink and black dividers since it's not free to use /end pt.)

[lavendergalactic]

☆ 　resources to make your own rentry/bundlrs border!

sources from da-lace.com f2u, like + reblog appreciated!

i forgot da-lace existed and then i remembered.. anyway have fun with these! no need to credit since i didn't make them

[sunn-mechanic]

can anyone familiar with html tell me how i can fiddle with the html of my blog theme to give the posts a border? i am suffering over here

[floofyflooftheallmighty]

Here's two generators I made that I'm v proud of :3

Sparkledog/animal generator

Basic gender & sexuality generator

[codingflicks]

CSS Gradient Border Animation

[1shimaru]

ik I complain abt everything being broken at my house but I always feel like I gotta offset it w some good news. Cant think of anything except "at least the raccoons are gone. It would be worse with raccoons."

[codenewbies]

CSS Button Border Animation

[lazuliquetzal]

This feature is for the most part screen-reader and keyboard navigation friendly (though there are some browser/software combos that have trouble with it). Link has more information:

So I thought this was commonly known internet navigation (but apparently it might just be those of us who have been using the internet since the 90’s who still know it). Or so it seems based on… a grumpy comment I got.

When you see an arrow like this:

It means you click it to expand out a hidden section.

It’s an accordion section/menu! It’s useful in web design to hide information that may be overwhelming under specific headers so people can only see what they need.

Here I’m using it for people who need the content warnings to be able to check, but for those who don’t need them and don’t want to be spoiled to just move right past without accidentally reading anything.

It’s still the user’s responsibility to click the arrow and read things as they need! But it is all warned. (And, yes, the all encompassing issues are already a tag on the fic, I’m just providing additonal warnings per chapter.)

[fluffypotatey]

why does html hate me so T^T

[josegremarquez]

CSS: Más Allá de los Estilos Básicos

CSS es una herramienta indispensable para darle vida a nuestras páginas web. Sin embargo, un mal uso puede llevar a problemas de rendimiento, mantenimiento y compatibilidad. En este artículo, exploraremos los conceptos fundamentales de CSS, desde los selectores básicos hasta las convenciones de escritura, y te daremos algunos consejos para evitar errores comunes. Selectores CSS: La Base de…

[divinector]

CSS Border Animation

[selysie]

mwore html bworders by mwe 04 metadata !!! ^ω^

(pt: more html borders by me for metadata !!! /end pt.)

[destinationtoast]

1/3 - Hi there! Three (I think) part ask incoming. You're the main person I know of who compiles tons of interesting fandom stats, so I wanted to ask you about it if you have the time to answer. :) I think a lot about how AO3 works great as a fan*fic* archive, but for other fanworks, like images, audio, video, etc., it's only as good as wherever the media is being hosted. With the way hosting sites come and go, or change their TOS to nuke nsfw or queer content, etc., it makes me wonder

how many broken image links litter AO3 at this point. I know it's not considered the primary place to find fanart, but a lot of folks do post images there—for events like Big Bangs, as standalone art, and even as decorative section breaks, etc. My question is: do you think there's a way to look at, say, works tagged with #fanart (of which there are 99,504 atm) and determine what percentage of those are broken links? From what little I understand, one would have to (perhaps with the use of a simple bot?) try to open any link bordered by the <img src> html, and see what portion of those return an error versus what ones actually load? I suppose it could even be something like looking at fanart posted in 2007, 2012, 2017, and 2022 to compare how many older links are broken versus newer links. Anyway, this may be completely unfeasible, but I figured I'd ask about your thoughts! Thanks!

Ooh, thanks for the great question! I took a while to answer because I wasn't initially sure what to recommend and ended up gathering some data to investigate. (If anyone else also has relevant data, please share in the notes!)

I liked your idea of looking at samples different years going back, and I decided to look through 100 AO3 works tagged "Fanart" (or a subtag) that were posted 10 years ago -- as a very fast starting point, I didn't even take a random sample of works, I instead looked at the first 100 multimedia fanworks posted in July 2014. (And August, when necessary; see more notes on methodology at the end.) Please keep in mind that this sample that may not be very representative of AO3 more broadly; to get better estimates, more sampling would be needed. Based on this initial data gathering (and the fact that most fanworks on AO3 were posted within the past 10 years), I would tentatively guess that that most fanart, fanvids, and podfic on AO3 still have accessible multimedia.

Given how many broken links and embeds there are on older webpages, I assumed that a ton of the links from 10 years ago would be broken. But I was pleasantly surprised by the results:

Wow -- 10 years on roughly 90% of the multimedia still works! I was honestly floored; I'd been originally planning to also look at 5 years ago to see how much better that was, but if ~90% are still working 10 years on, 5 years ago doesn't have room to be dramatically better. (However, I'd love to see more follow up sampling across different years to find out.)

There were a lot of AO3 users in this sample who posted multiple works -- some posted as many as a dozen multimedia works in July 2014. I didn't want the results to be overly skewed by any one fanwork creator, so I also redid the analysis with just one work from each unique creator:

Okay, cool, those results are pretty similar. I also did some further breakdowns on this smaller set of works to look at which hosts creators were using, and how many of the hosts were still working:

The most common fanart host used in this sample was Tumblr, then wixmp -- which I think from some very quick googling might be because Deviantart switched to using Wix for image hosting at some point? (i.e., I think most of those artists may have posted their art on Deviantart, then linked to/embedded the image on AO3, and the image's direct URL was was wixmp.) There were a few other hosts at the time that were used by 5+ different artists in the sample, and then there were a whole lot of hosts were used by just one or a few artists.

Most of the 10-year-old fanart is still up for all of these hosting categories! Photobucket is the least reliable of the most commonly used hosts. In the Other category, 25% of the links are broken, but that's still better than I expected (see full host list here).

This is getting long, so I'm moving the breakdowns for fanvids and podfic beneath the cut:

Fanvids were almost all hosted on YouTube, Vimeo, or both (the above categories are not mutually exclusive). All the Vimeo links still worked, whether they required a password to view or not. Most YouTube links were working, and the few missing ones had almost all been taken down by YouTube for copyright reasons (according to the errors I got -- I'm not rendering judgment about whether they were actually fair use), rather than by the vidder who posted it. And almost a third of vidders also linked to other hosts besides the big two, but many of those links were broken; 59% still worked. (see full host list here)

For podfic, mediafire was a popular solution 10 years ago, though many podficcers used it as a backup rather than the main link that they shared. A lot of podficcers made use of a fandom hosting site that specialized in podfic -- either parakaproductions.com or audiofic.jinjurly.com. Four podficcers used soundcloud (often as a backup). And once again there were a lot of less-frequently used hosts, often used as backup links; 69% of those still worked. (see full host list here)

Some methodology notes and further thoughts:

For fanvids and podfic (but mostly not from fanart), the fanwork creators tended to provide multiple links, and in those cases, I counted the multimedia as working if at least one of the links was still working.

I counted embedded media and links to other sites that host the media all the same way.

I counted the media as broken if I got a 404 when I tried to visit it, or if a site like YouTube had taken it down due to copyright issues, or if I got an Access Denied message for a site like Google Drive.

I counted the media as working if it required a password that was given on the page (common with Vimeo), or if an embed was broken but there were working links to other sites.

How representative is this data? Well, these samples contained most/all of the multimedia fanworks posted in July 2014; that month, there were 70 fanvids, 135 podfic, and 186 pieces of fanart posted that haven't been deleted since. So it's pretty representative of July 2014 specifically. :) But there could have been, say, a fanwork challenge going on in July 2014 that caused unusual uploading patterns then.

The above data gathering and analysis took me several hours over several days. If you want to follow up, you could do more data gathering similar to what I did (I'm happy to elaborate on my process as needed). Or you could write a bot to do something similar; you could have it fetch more AO3 fanworks and try following the links within each work. However, that would be slightly tricky; I ran across more kinds of errors and complicated situations than I expected (e.g., if a YouTube video has been taken down due to copyright, it still has a working YouTube page; sometimes an embed is broken, but if you open the link within the embed in a separate window, it still works fine; many Vimeo links require a password to test, and it could be hard for the bot to reliably find the password in the surrounding text). So you'd have to program your bot to be able to handle a bunch of different special cases.

Regardless of which path you are considering, if you or anyone else does any follow up work here, I encourage you to start by looking through a bunch of fanworks yourself and deciding which scenarios you want count as "working" vs. "not working," and any other things you want to pay attention to.

Hope that helps, and please feel free to DM me with follow up questions. And if you follow up, please share anything else you figure out in this space!

[comment-day]

How To Embed An Image In An Ao3 Comment

Sometimes, an image is worth a thousand words. You've read a fic, and the only way to respond to it is with a picture. Maybe this is a scribble you drew in the notes app on your phone, maybe it's art you drew with actual artistic talent, maybe it's a meme you just looked up, maybe it's a meme you just made. But you have your image, and you want to put it in someone's comments. How do you do that?

Ao3 comments support HTML, so to embed an image you need an image link to where the image is hosted somewhere on the web, and you need a bit of HTML code. First thing, the image.

You can use a site like Imgur to host your image, or a private tumblr post, or a fandom image host like Squidge Image Hosting. The important thing is that you want the actual image URL, and not the link to the page that the image is hosted on. Let's say you put your image in a private tumblr post, it would look something like this to get the image link.

You want to right-click (or control-click, whatever works on your screen) to get this dropdown menu, and go down to Copy Image Address. That drops the URL into your clipboard. And then you copy this code:

<img src="YOUR IMAGE URL" alt="DESCRIPTION OF YOUR IMAGE" border="0" width="Max-width 95%" />

In order that's the code that tells the HTML which image to pull off the web, a description that will work for screen readers, telling it that it doesn't need a border, and a bit of code that will keep the image from running off the screen if you grabbed a big image. You put your image URL in that bit of code and write a fast description, and then bingo, you're ready to post your image!

Oh god though, you're on mobile, that all looks awful: quick tip! If you host your image on images.squidge.org, they will do the html for you. It's free fandom image hosting as long as you're over 18. Upload your image, and then scroll down on the page, and there's a convenient button with the HTML just done for you already.

Scroll down to HTML and hit the copy button, and then just paste that into the Ao3 comment box, update the image description (cause it'll just have the title there) and you're good to go!

Go forth and decorate the world with images!

[vestaignis]

Водопад Кедунг Каян — это скрытая жемчужина, расположенная на территории Национального парка горы Мерапи. Эта очень интересная туристическая достопримечательность, находится на границе районов Магеланг и Бойолали, Центральная Ява, Индонезия. Водопад Кедунг Каян берет свое начало исключительно из источника на горе Мербабу,и расположен на высоте примерно 1200 метров над уровнем моря.Водопад Кедунг Каян  имеет высоту около 40 метров, он очень мощный,объем потока воды, никогда не уменьшается, даже в разгар засушливого сезона. Чтобы добраться к водопаду нужно будет спуститься к руслу реки и даже в одном месте пересечь ее в брод.Красотой этого водопада можно любоваться с разных сторон. Либо сверху, сбоку или спереди.

Территория вокруг самого водопада застроена таким образом, чтобы стать туристическим местом. Вокруг есть несколько вспомогательных объектов, таких как жилье и кемпинги. Атмосфера в самой локации у водопада не слишком оживленная, поэтому вы сможете более свободно наслаждаться свежестью природы. Вода, падающая с этого водопада, впадает в небольшую каменистую речку. Можно зайти в бассейн, поиграть в воде под плеск водопада.

Kedung Kayan Falls is a hidden gem located within Mount Merapi National Park. This very interesting tourist attraction is located on the border of Magelang and Boyolali districts, Central Java, Indonesia. Kedung Kayan Falls originates exclusively from a spring on Mount Merbabu, and is located at an altitude of approximately 1200 meters above sea level. Kedung Kayan Falls  has a height of about 40 meters, it is very powerful, the volume of water flow never decreases, even at the height of the dry season . To get to the waterfall, you will need to go down to the river bed and even cross it into a ford in one place. The beauty of this waterfall can be admired from different angles. Either from above, from the side or from the front.

The area around the waterfall itself has been developed in such a way as to become a tourist destination. There are several supporting facilities such as accommodation and campsites around. The atmosphere in the waterfall location itself is not too lively, so you can more freely enjoy the freshness of nature. The water falling from this waterfall flows into a small rocky river. You can go into the pool and play in the water while listening to the splash of the waterfall.

Источник://www.tripadvisor.ru/Attraction_Review-g6925271-d711 5 432-Reviews-Kedung_Kayang_Waterfall-Boyolali_ Central _ Java .html,//www.getyourguide.ru/air-terjun-kedung-kayang-l194646/kul-tura-i-istoriia-tc27/,/jateng.akurat.co/wisata-kuliner /1333640325 / misteri-dan-cerita-mistis-yang-ada-di-air-terjun-kedung-kayang-magelang-yang-menjadi-daya-tarik-wisata,/discoveryourindonesia . com/kedung-kayang/,/commons.wikimedia.org /wiki/ File:Kedung_ Kayang_Waterfall.jpg,/ksmtour.com/informasi/tempat-wisata/jawa-tengah/air-terjun-kedung-kayang-jawa-tengah-yang-konon-berpenunggu.html.

[codingflicks]

CSS Gradient Border