It’s possible, you copy the post id and put a number in front of it, like the following:

#43294288@startrek.website

However, it doesn’t autoformat to a link (unfortunately). To do that you need to do regular links. IE: [link](#43294288@startrek.website) which produces this link

Edit: Damn it, messed this up, just a sec let me read some more.

Looks like it’s simply not possible. There’s open github cases around this and this particular feature was just dropped. Shame, I’d have liked the #postId@site format.

It’s very clear that at this point, insofar as there is any logic at all to the decision making of people investing in Tesla (and there’s very little evidence of that), they’re evaluating it as a software company, not a car company.

Nah, the logic to the decision is that other people are buying a lot of tesla stock and the price keeps going up. It’s very nearly a ponzi scheme. It has value completely detached to what the company is doing. It’s tulips, crypto, beanie babies. Most institutional investors realizes this, they also are trying to get in and get out without holding the bag.

Regardless, I’d bet anything that you are not able to reencode blurays to 15mbps without substantial quality loss.

It’s crazy how confident you are about something you’ve never done.

Yes, I’ve gotten transparent encodes with 15mbps. Lots of people have.

If you don’t believe me, go to the AV1 subreddit and ask “can you get a transparent encode with only 15mbps”. Or just go read up on svt-av1 and av1an and do it yourself.

Look, this is just an incorrect oversimplification of the problem. It’s popular on the internet but it’s just factually incorrect.

Here’s a thread discussing the exact problem I’m describing

https://www.reddit.com/r/AV1/comments/1co9sgx/av1_in_dark_scenes/

The issue at play for streaming services is they have a general pipeline for encoding. I mean, it could be described as cheaping out because they don’t have enough QA spot checking and special purposing encodes to make sure the quality isn’t trash. But it’s really not strictly a “not enough bits” problem.

I promise streaming services and CDNs employ world-class experts in encoding

They don’t really care about the quality

It’s funny that you are trying to make both these points at the same time.

You don’t hire world class experts if you don’t care about quality.

I have a hobby of doing re-encoding blurays to lower bitrates. And one thing that’s pretty obvious is the world class experts who wrote the encoders in the first place have them overly tuned to omit data from dark areas of a scene to avoid wasting bits in that location. This is true of H265, VP9, and AV1. You have to specifically tune those encoders to push the encoder to spend more of it’s bits on the dark area or you have to up the bitrate to absurd levels.

Where these encoders spend the bitrate in dark scenes is on any areas of light within the scene. That works great if you are looking at something like a tree with a lot of dark patches, but it really messes with a single light person with darkness everywhere. It just so happens that it’s really easy to dump 2mbps on a torch in a hall and leave just 0.1mbps on the rest of the scene.

That will unarguably provide a drastically worse experience on a high-enough quality tv than a 40mbps+ bluray. Like, day and night in most scenes and even more in others.

I can tell you that this is simply false. And it’s the same psuedo-scientific logic that someone trying to sell gold plated cables and FLAC encodings pushes.

Look, beyond just the darkness tuning problem that streaming services have, the other problem they have is a QOS. The way content is encoded for streaming just isn’t ideal. When you say “they have to hit 14mpbs” the fact is that they are forcing themselves to do 14mbps throughout the entire video. The reason they do this is because they want to limit buffering as much as possible. It’s a lot better experience to lower your resolution because you are constantly buffering. But that action makes it really hard to do good video optimizations on the encoder. Ever second of the video they are burning 14mb whether they need those 14mb or not. The way that’d deliver less data would be if they only averaged 14mbps rather than forcing it throughout. Allowing for 40mbps bursts when needed but then pushing everything else out at 1mbps saves on bandwidth. However, the end user doesn’t know that the reason they just started buffering is because a high motion action scene is coming up (and netflix doesn’t want to buffer for more than a few minutes).

The other point I’d make is that streaming companies simply have a pipeline that they shove all video through. And, because it’s so generalized, these sorts of tradeoffs which make stuff look like a blocky mess happen. Sometimes that blocky mess is present in the source material (The streaming services aren’t ripping the blurays themselves, they get it from the content providers who aren’t necessarily sending in raws).

I say all this because you can absolutely get 4k and 1080p looking good at sub-bluray rates. I have a library filled with these re-encodes that look great because of my experience here. A decent amount of HD media can be encoded at 1 or 2mbps and look great. But you have to make tradeoffs that streaming companies won’t make.

For the record, the way I do my encoding is a scene by scene encode using VMAF to adjust the quality rate with some custom software I built to do just that. I target a 95% VMAF which ends up looking just fantastic across media.

Blocky artifacts typically appear in low light situations. There will be situations where it might just be blocky due to not having enough bits (high motion scenes) but there are plenty of cases where low light tuning is where you’d end up noticing the blockyness.

People don’t like hearing this, but streaming services tune their codecs to properly calibrated TVs. Very few people have properly calibrated TVs. In particular, people really like to up the brightness and contrast.

A lot of scenes that look like mud are that way because you really aren’t supposed to be able distinguish between those levels of blackness.

That said, streaming services should have seen the 1000 comments like the ones here and adjusted already. You don’t need bluray level of bits to make things look better in those dark scenes, you need to tune your encoder to allow it to throw more bits into the void.

It’s a mess. You first run into bandwidth problems on the incoming streams. But you also run into a problem with the device support matrix.

If you say “We’ll support H.264, H.265, AV1, AV2” and “We’ll support 480p, 720p, 1080p, 4k”. Now you’d be asking the clients to do 16 different encodes to upload.

This gets more complicated if you add more streams or supported formats. You also end up needing to coordinate that with the client.

AFAIK, the way youtube currently handles this problem is they have dedicated encoders for live streams and fast encoding. For popular videos they do a second step where they do a more full matrix to optimize viewership.

IDK what youtube does for storage (if anything).

A service like youtube is simply hard to pull of with bailing twine and string (like lemmy).

A core part of the service that youtube offers is re-encoding uploads. That requires some beefy hardware to serve even a moderate number of people.