lime!

it was never available outside the usa i think. hard to get useful market penetration then

ugh

[…] the way people save and consume content on the web has evolved, so we’re channeling our resources into projects that better match browsing habits today.

…in what way?

vibe coding is when you let an llm write almost all your code, taking its output at face value. tony stark in the films just vaguely describes to his computer what he wants and trusts that it does the right thing.

i was thinking salmon and dill

please tell me you have an accepted code style with proper tooling and precommit hooks set up

but like… if your entire customer base is saying you’re wrong, aren’t you then wrong by definition? the buyers set the prices, in a way.

oh i know, i learned to drive on manual since most cars are manual here, i just haven’t owned one myself.

that said, with electric power-steering and throttle-by-wire, there’s no feel to get. it’s all just dead, no matter how fun the clutch is.

i can imagine. i’ve mostly had automatics, but when i was looking for my first car one of the candidates was an old saab with no tacho, it only had little indicators on the speedometer for where to shift. in that situation i imagine muscle memory is created pretty quickly.

especially in a diesel even 1500 is too much.

you can get the same performance by using the restrict keyword in C.

basically, C allows pointer aliasing while fortran does not, which means C programs need to be able to handle cases when a value is accessed from multiple locations. fortran does not, so a lot of accesses can be optimized into immediates, or unrolled without guards.

restrict is a pinky-promise to the compiler that no overlapping takes place, e.g. that a value will only be accessed from one place. it’s basically rust ownership semantics without enforcement.

it is a dynamically typed language, but it’s not a weakly typed language.

the main thing that makes fortran preferable to C is the way it handles arrays and vectors. due to different pointer semantics, they can be laid out more efficiently in memory, meaning less operations need to be done for a given calculation.

so it would be more accurate to just have tailwind be css with a suit.

basically this

in short,

• semantic html (<nav>, <main>, <aside> etc). ban use of <div> unless there is no fitting tag.
• aria roles (which you will need less of with semantic html)
• logical grouping, which facilitates
• structured text that flows in a screen reader
• never ever ever use <button>s instead of <a>nchors for links unless you have a very good reason.

also, don’t use the wording “circling back” unless you want people to get office ptsd.

sure there are ways that are harder to track but it happens on every platform. i will concede that i have stretched this past the breaking point though, and that i’m now basically criticizing all social media.

you’re probably right that it doesn’t matter for most people, but i’ve seen enough cases where illegal material is smuggled through the cracks of a system that i can absolutely believe that there will be groups committed to seeding and sharing removed content, possibly using a mainstream instance to post drops. then that instance gets implicated.

right, so it still exists, it’s just not associated with me. idk if i’d be comfortable running something like that.

i get that part, and i appreciate that you devs are here answering questions. i just don’t understand how that will work if people who have already seen the content still have it cached and can help seed it. or am i understanding that wrong?

delete, or hide? because if images are hosted on ipfs they’ll be up as long as someone wants them to be, and in a content-addressable network you’ll just be playing whack-a-mole with people linking illegal stuff.