It’s how llms work… The points in vector space are basically tokens. The distance is correlated to aspects of things/concepts

So you can use geometry to search the vector space and get very good results, it’s mainly used to store/index information for later retrieval

I think a good church is great for hobby projects ready to be taken out of the basement

You do have to belong to such a church already though

Devs are the creators… What the public gets is down stream from their work

I like this concept. Make federation easy and practical for devs

The benefit is less distractions and pointless organization for a project in the early stages

Open sourcing things is a pain in the ass. It’s common to get the core project working before doing so

There’s no digital ID in my system, there’s digital disclaimers and parental locks on the devices

The way we’re going now is digital IDs, they would try to throw it in regardless, but under my plan there’s no place where it could come into play

You could go further than that… Mandate that all new devices and app stores must have a parental lockout available out of the box

Then when you get your kid a phone or computer, you just set up the permissions. This already exists to a large extent, this would just standardize it all to turn it into a usable system

If they were serious about protecting children, they would have a device level lock and force web pages and apps to positively affirm they are “safe” for minors

That would work, this clearly won’t. This is just censorship, you can’t sanitize the Internet, you can only carve out walled gardens

You could mount it on top or vertically behind the rack and have it still look decent and be functional with a little handiwork

You still are going to need a router, although you don’t need a fancy router and a fancy switch, you just have to make sure you’re not bottlenecked and have to design things differently

2.5 gb is probably more than enough, but you could probably get away with 1 gb if you aren’t doing a lot of file transfers - if it’s just backups and streaming video, if you want to get fancy it might become a bottleneck.

PoE is kinda niche so unless you have specific plans to use it, it probably won’t come up

The switch supports vlans, so you could get fancy with a VPN gateway and access these things remotely with a Virtual DMZ, but realistically that’s a bitch to set up and you could just make a real DMZ with a router/wifi access point combo. Or just forget the DMZ and have a VPN gateway that connects to the local network

I really just don’t know enough about how you want to use this to get more specific. This is probably more switch than you need, but if you’re not connecting from outside it’ll probably work great for the LAN

Networking is all about bottlenecks, and I doubt this will be a bottleneck for a good while

I’m not sure what you’re asking

In your position, I would want a VPN. I like wire guard, it’s pretty simple compared to other options… But just comparatively

If you want to do networking to network, I can suggest all sorts of things… None of them is practical for normal use cases, but some are pretty neat

That’s wasteful and dangerous

Harvest the beast for batteries and GPUs

Not even that… Kids do it IRL, because they hear it so much online

It’s so invasive too… Hearing kids self censor for advertisers, like “unalive” or “pew pew” is deeply disturbing

Our language is being artificially pushed towards Corpo-speak

I’m split, but I lean slightly towards no. On one hand, it could be good for discoverability, and it would help my efforts to make a client-side algorithm

On the other hand, it will make one of Lemmy’s problems worse - engagement. Some people will vote less, and it’s already feeling a little quieter around here as the numbers settled after the Reddit Exodus. I doubt it’ll be a massive change, but a .5% decrease in voting, permanently, could make a difference

Ultimately, you can see it on federated platforms, so shrug

Huh, I’ve never actually come across that, I’ve only gotten it indirectly. I bet my first mentor put it on in my head, the guy built out our entire system, then a v2, with one intern while the rest of us extended the framework he built.

As long as the Lemmy API can be used as a de-facto standard

And that’s the sad part… The Lemmy api is not only not that, federation is an API+ that gives an amazing starting point. As far as I can tell, the lemmy API was made with the official clients in mind, and everything else was an afterthought made in a hurry during the last Reddit Exodus

I started reading through the kbin API, which starts with “here’s a link to activity pub standards, they’re surprisingly readable”. They were… It’s unwieldy in a lot of ways and maybe too all-encompassing, but they left so much on the table.

For one, uri ids. Lemmy has them for everything (which is nice), but they aren’t directly usable. You can get the local ID for the home instance, but if I’ve got a url for lemmy.world I want to see on my instance, my only option is a search. Which should kick off federation, but what if it’s there already? I want an endpoint to resolve it (or even to tell me it’s not here right now so I can fall back).

And the way they handled metadata is pretty awkward… They next objects inside of collections of activity data and object properties, which is annoying because it’s so inconsistent. Like, if you get a comment response, it gives you the comment reply, which is basically a comment without the usual metadata like vote count or the full actor object.

It gives you too much, then suddenly too little - I don’t need the bio, tagline, and banner of a server every time I see a post, and I also don’t need it for the community and user

But I do need the comment votes when I get a reply - I’ll wait on the comment chain and root post, but I don’t want to have to build a post-body only component to show while I wait to replace it with the whole thing

I do really like that they autodoc everything… Even if a lot of it is indecipherable with no context offered. Like the honeypot parameter on getPosts… It’s actually intended to be a honeypot. Like if you set it to true, it’s supposed to not give you posts, or log you or something? I tracked down a one line confirmation on GitHub which left me baffled. I had to try it… It didn’t seem to do anything

/Rant

It is getting better though, the amount of completely breaking changes that pop up is very frustrating, but this time around it is significantly improved

I’d love it if the API that exists was more reliable… It’s getting better, but the amount of basic features that didn’t work (usually without specific combinations of params or unknown ranges, but sometimes not at all) is pretty crippling. (If there’s a central place of discussion, I’d love to hear about it…I don’t speak rust or flutter, but I’ve had to muddle through source several times)

I’ve never done anything as a mod so I have no idea what kind of tools they need, but I noticed enough basic parts to build all sorts of things.

There’s definitely no reason to build it into the core though… Why put it on the machine busy serving everyone? You could do stuff so much cooler if you offload it… Like you could track mod actions against users/communities/servers, give a sample of random posts across their vote distribution, show the top few communities they get down voted… All things psychotic to even consider in the core right now, but a reasonable project for a separate system

And since you seem like you’d get it, I want to share a win I made today. I’ve got a lemmy app I want to mix feeds (including between accounts and servers) to make a unified feed algorithm on your device. I also want it to support kbin, and maybe more… I took a couple cracks at it and charted out several designs, but I was getting too deep into abstraction.

Today, I finished working on a ridiculously generic abstraction layer - it handles not only tracking pagination, buffering, and preprocessing, it also enumerates all of the options in the Lemmy sdk so I can auto magically build most of the controls when I update. It also disambiguates resources (and actors) across instances and could describe valid actions you can take on it (I think that might be too far, so I’m resisting the urge… This time)

Everything is done through the account level, everything knows where it came from and can call the API by passing itself to its account to be worked on. It’s also neatly serializable, you just have to write one function to pull the next page, and the rest is just an absurd amount of generics

Now, if I can figure out how to translate all that into a usable UI, I’ll be getting somewhere…

I just had to share that with someone who can appreciate crazy data flow, it’s been in the back of my head for months and today (after pulling my hair out for an hour and realizing I was forgetting to actually pass the posts to the UI) it worked beautifully

I like to think of it like this - many hands makes for a very stable project. Stable as in reliable, but also stable as in resistant to change.

Everyone is going to pull in a different direction, and it kind of averages out and slows things down.

Right now, lemmy is extremely immature. It’s amazing how well it’s held up really. There’s a lot to go to get to a solid baseline - just enough to keep

If everyone dogpiled it, someone could easily solve the image problem. Granted, that might block someone else working on the database, and changes to improve or extend federation would likely be set back as they step on each other’s toes.

We could still probably quickly get popular features quickly… For example, one person could get more useful mastodon and kbin federation going in a reasonable period of time. But then, when the core team goes in to overhaul the database or the API, now they need to make sure they don’t break it - and the person who did those changes won’t have the same vision as the core team, and now you have to either refactor the whole thing or work around it until it’s causing too many problems

Certain things can be spun off more easily than others - I think other people have totally taken over deployment of instances.

Some are good candidates but require more maturity - like if they handed off jerboa and the default web client, there’s one place that would need to be reinforced - the API.

Way down the road, they could build plug-in/mod interfaces so instances could choose feed algorithms, or individuals could come up with their own karma systems, or all sorts of other things.

To get to that point, you have to have a clear vision and stable growth though - that takes time, and is better done by an individual or small team keeping things heading in one direction

I’d love to debate you on it, but you’re not giving me much to work with.

Generally, a mod willing to debate me is a mod I want around

You can spin up your own server… That’s what the fediverse is.

The freedom to do whatever you want as an admin, and the freedom of choosing another server where you’ll still be part of the network

Meta/Facebook threatens this, because their user base dwarfs the rest of the fediverse. They’re also running their own closed source server code… They can gatekeep their own federation

I would love it if companies joined the fediverse, but like, by making instances. Maybe even use it for their internal Intranet. Maybe they could add federation compatible APIs to their existing software

I don’t want a massive social network company to use their position to make a new social network…

Federation is like Bitcoin or Tor - it’s decentralized, until one org becomes too large… At that point, they can control the network in countless ways

Same idea as lemmy, you pick a server and join chatrooms on any federated server