kan man.

PressAlt+F4AndIfItComesBackThenDeleteC:\Windows\System32pleaseDontMindMyWritingMyPunctuationIsNotWorking

You can compare total better than per user at these scales.
Lemmy needs a certain amount of performance to keep up with federation, but once you have all the images and posts and comments you don’t need second versions until you scale to a size that mandates multiple machines. Which I would guess is more in the 6+ digit user range, where you start averaging requests per second not minute.

In some sense, every lemmy user is a user of your instance via federation. You need to pay the performance for all 100k of us whether your instance has 10 or 10k of those. Local users are just a bit extra demanding on your hosting resources.

I suspect the bias we see here with larger instances paying a bit more (50-ish instead of 10-ish) is more due to reliability and snappyness than actual performance needs too. You tend to get optional smaller-gains pricier perks you might not go for for a smaller instance.

Link is detected without the emoji in my app. You might wanna hardcode the link as https://en.wikipedia.org/wiki/😂
[https://en.wikipedia.org/wiki/😂](https://en.wikipedia.org/wiki/😂)

If you rename a file only changing the casing it doesn’t update properly, you need to rename it to something else and back.
This is so userfriendly I have been stumped by it multiple times.

On the other hand in using Linux I have had a number of problems with the casing of files: The number is 0

Yeah. You want to preserve the AI’s abilities. Hence adding the “paste imagination” feature for example. If you simply use that and finish “editing” that is current AI. Then you can quickly redo only sections from imagination until they look good, maybe with a specific prompt or other form of understanding about what needs to be done and changed there.

We can invert our visual center, so basically we see an image, think about it, then can summon a mental version of that painting back as an image by converting the abstraction of it and change things about the abstraction until the mental image seems good. This abstraction can handle ideas like recognizing, moving, scaling, recoloring objects. It can do all we can imagine because it is literally how we interpret the world. Then we spend hours trying to paint that mental image we created using limited tools. If we could just project something the same way we see, that would probably match image-AI in the initial output but after tens, hundreds of passes you could likely within minutes create something completely impossible by any other means.

If you feel like you can think clearly and are questioning if you are dreaming but are unsure, you are not.
All methods of lucid dreaming aim at making you think clearly and question if you are in a dream. With that thought, it should be quite obvious to confirm you are in fact in a dream. Dreams are really not that good, sleeping is just kinda like a heavy suspension of disbelief.

Yeah. It is not like you can perfectly recreate them, but as long as you don’t see a problem with whatever your brain fabricates it’s not gonna do anything.

What I used to do was try to breath through my nose. That is a different mechanism, where probably for safety your body doesn’t “disconnect” your breathing. If you hold your nose shut, you will still be able to breathe in a dream.
It is something you can easily make a habit, as just quickly pinching your nose doesn’t look weird, and then you will naturally do it in your sleep too and become lucid.

All you really need is a moment of doubt, and if you have experienced a few dreams you will always be able to tell if you are dreaming or awake at a thought, at least in my experience.

I have stopped lucid dreaming a while ago, but I think I am still always aware when I sleep based just off of how I sleep. Ever since then it feels more like I am just going along with my dreams most of the time, and occasionally I just decide a nightmare sucks too bad and change it or wake myself up.

You know, thinking about it, I doubt this is a coincidence.

The finger-counting is familiar to me as a technique for lucid dreaming. If you look at your hands in a dream, your brain will kinda fuck it up, so if you train yourself to pay attention to that you realize you are dreaming and become lucid.

My guess is that the origin of fae is something like sleep paralysis deamons or hallucinations, and people realized they could detect those from the same flaws of our own imagination.

Now for AI, it isn’t really drawing. What we are using in image-AI is still much more like projecting up a mental image, dreaming. We can’t get it right all at once either, even our human brain is not good enough at it, it is reasonable image-AI makes the same kind of mistakes.

The next step would logically be to emulate the drawing process. You need to imagine up an image, then observe it at large, check for inconsistencies using reasoning and visual intuition.
Hone in on any problems, stuff that doesn’t look right or doesn’t make sense. Lines not straight.
Then start reimagining those sections, applying learned techniques and strategies, painter stuff (I am not an artist).
Loosely I imagine the ai operating a digital drawing program with a lot of extra unusual tools like paste imagination or telepathic select, or morph from mind.

The main thing differentiating dreaming from painting is that for painting you can “write stuff down” and don’t have to keep it all in your head all the time. This allows you to iterate and focus in without loosing all the detail everywhere else.

Yeah, for amateurs it’ll be a while longer for this tech to become easily available.
Though It is also fundamentally fixable, you can take the output of your sensor and apply the same sort of logic to it as professional large telescopes. The blocking spots will be larger since the telescope will not correct for atmospheric distortions and likely be in a less favorable spot, but still you can do far better than throwing out entire frames or even entire exposures.
It is ofc a much much larger ask for hobby astronomers to deal with this initial wild-west software mess of figuring all of that out.

As for the RF mess, this is the first time I hear of that. It seems honestly kinda odd to me, we have a lot of frequency control regulations globally and I have heard SpaceX go through the usual frequency allocation proceedings. A violation of that would be easy to show and should get them in serious trouble quickly. Do you have any source on that?

Maybe to add a bit of general context to this, I am not an astronomer but I work in an adjacent field. So I hear a lot of astronomers talk about their work both in private and public.
You don’t really hear them talk about satellites often. What from what I gather really wrecks astronomy is light pollution, which has been doubling every few years for a while now and is basically caging optical astronomy to a select few areas.

The worst thing for astronomy in the last century has probably, ironically, been the invention of the LED.

The satellite streak thing is probably a minor point, where newspapers caught some justified ranting of astronomers and blew it way out of proportion.

Wrecking is not really the right term.
It is causing work for astronomers, and wrecking very few older systems, but generally it is an issue you can work around. I.e. something temporary. What you usually see in my experience of the field is you have some of your work degraded by satellite streaks, which are about 2x more common since starlink, and you understandably complain at starlink. And then get around to coding up a solution to deal with the streaks, spend another few runs until it about works, and eventually forget this was ever a thing.

In more detail, the base issue is, that you are taking an image, with probably minutes or hours or days of exposure, and every satellite passing through that image is going to create a streak that does not represent a star. Naturally that is not good in most cases.
The classic approach here, because this issue has existed since before starlink satellites, is to - depending on frequency and exposure length and your methodology - either retake the entire shot, or throw out at least the frames with the satellite on it, manually.

The updated approach is to use info about satellite positions to automatically block out the very small angle of the sky around them that their light can be scattered to by the atmosphere, and remove this before summing that frame into your final exposure. Depending on methodology, it might also be feasible to automatically throw away frames with any satellite on them, or you can count up which parts of the image were blocked for how long in total and append a tiny bit of exposure only to them at the end.

To complicate this, I think more modern complaints are not about the permanent constellation satellites but those freshly deployed, that are still raising their orbits. Simply because their positions are not as easy to determine, since their orbits are changing. So you need to further adapt your system to specifically detect these chains of satellites and also block them out of your exposures.

The issue here is that you need to create this system that deals with satellite data. And then you need that control over the frames in your exposure, which naturally does not match how exposure used to work in the olden days of film, but to my knowledge does work on all “modern” telescopes.
My knowledge here is limited but I think this covers about 30-40 years of optical telescopes, which should largely be all optical ground based telescopes relevant today. Further, you probably do need to replace electronics in older telescopes, since they were not built to allow this selective blocking, only to interrupt the exposure.

In summary, not affected are narrow fov modern optical telescopes, and in general telescopes operating far from visual frequencies.
Affected with some extra work, would be some older narrow (but not very narrow) fov telescopes, as you now have to make them dodge satellites or turn off shortly, when previously you could have just thrown away the entire exposure in the rarer cases you caught a satellite. This would be software only (not that software is free).
Modern wide fov telescopes might need hardware upgrades or just software upgrades to recover frames with streaks on them.
Old wide fov telescopes may be taken out of commission or at least have their effective observation times cut shorter by needing to pass out on more and more exposure time over satellites in the frame.

It is a problem, yes, but in my understanding one that can be overcome, and is causing the main annoyance and majority of its issues while the number of satellites is increasing, not after they have been increased.
I don’t know of a single area of ground based astronomy that couldn’t be done with even a million satellites in leo.

I think they were talking about HughesNet the entire time. With the pricing, datacaps, and the latency lies. HughesNet does use geostationary satellites and has 600ms latency according to Wikipedia.

i2p doesn’t really have exit nodes, it’s mostly for i2p internal connections.
The only exit I know is stormycloud.i2p, and that one is somehow immensely limited ro the point of it being hard to load clear-net text pages.

We can’t make enough. And crispr is for inside cells, there is another layer needed for getting it there, like a virus shell for example.

Spreads Dirac Sea with malicious intent

That isn’t really going out of your way, it is the base mode of how the fediverse works. Looking at something on a different instance.
Plenty of people just use mbin and see this, without any action at all.
The point is that as it stands right now, there are already basically no restrictions. The only thing perhaps missing is the knowledge that you can simply copy paste a link into fedia or another mbin instance to view upvotes.

You can open an issue on mbin about it, to restore a semblance of restriction. But currently as it stands, all restrictions are about as fallen as they could be.

You can ofc argue that we shouldn’t open another equivalent hole in lemmys webui and api, so that you can in the future remove the ability from mbin.

I would in turn argue that this system has always been egregious, and that in the same sense as banning encryption you never hit those you want to hit using incomplete restrictions. Regular users are led to believe their votes are private, while the worst dataminers or trolls will always have their instances to query all of that info.
And how could you inform people that their votes are public without at the same time telling them how to get access to that info?

If mbin removes the info, you will get another fediverse software showing it. You will get fediverse activity pub log info pages, specific vote info pages, it will never end.
Has reddit ever managed to kill the 200ᵗʰ removeddit clone?

Please instead put your effort into changing the way lemmy federates, the only way to fix this is to make vote details private, between only a select few instances. An mbin dev in the other thread mentioned PeerTube as an example implementation where you could remove vote details like that.

This would solve some of the problems. If only 2 instances know about the votes, post instance and sublemmy instance, you can reasonably expect to get most instances to never release that info. It would allow either the sublemmy or post instance to manipulate around in the votes, but most manipulation would be detectable by the respective other instance.

It would open the door however to manipulating around with internal posts made from the instance in a sublemmy on the instance. And it would allow the post instance to drop votes selectively, though I think that is possible currently all the same.

Votes being sent to both the sublemmy and the post instance simultaneously would make manipulation a lot harder. And for cases like internal posts, you could add another involved “judge instance” that receives the vote details directly from source, and is merely there to confirm the total. Instances that hand out non-independent “judge instances” could be labeled as untrustworthy in the lemmy community.

So you end up with a list of instances per post that votes are reported to, to which you add the post instance, sublemmy instance, judge instance, and maybe some more.

In terms of implementation, I think the activitypub protocol needs an origin for votes, right? I would say an instance can just report the votes coming from a stock of obviously fake accounts, like “masked_upvote_1” to _999999 … and “masked_downvote_1” to _XYZ.
About the votes, I am not sure. It could be done as a lemmy-internal feature where lemmy instances and other instances knowing of the lemmy protocol send the info to all the relevant instances, while any votes from external instances only arrive at I guess the post instance and that then forwards it on to all other instances. This way the checking doesn’t work for software unaware of that lemmy specific vote implementation, but everything is still compatible.

You could then even for those lemmy-external votes add an interface on the judge instance, that would confirm via pm if your vote has arrived.

Do you think this could work?

In my case I would like them to be private, but currently they are not. I don’t think it is good to try to hinder the visibility into a fundamentally transparent system.

I don’t see a technical way to make votes private either, that doesn’t prevent bad actor instances abusing the vote system. As an admin of an instance I could just add 5-10 votes to all of my interactions whenever I feel like it, and noone would be able to tell it didn’t come from legitimate users on my instance. The accounts of vote origin are needed as proof, hence moderators on lemmy having access to them.

Do you perhaps have any idea how this could be accomplished?