That’s cool any plans to implement a WiFi direct style feature to allow faster file transfer. I can see the opportunity to build a foss cross platform alternative to airdrop on top of this.

Maybe burnings as well

Some poor engineer probably had a crisis when they realised they where wasting their life implementing shit this stupid.

One or all of em.

Ahh so ur running the ai locally on device. That’s cool how does android handle it?

Yo that’s sick. U will get a lot of pushback for the ai but I love it. Is it foss? I run [email protected] and am using a t5 summarisation model what u using for summaries?

OK let’s run through some debug steps.

Test to see if samba is working by using a docker volume instead of trying to mount a file path.

If that works we can then assume its purely a file permission issue. U can check/test that by opening a shell inside the docker container and doing investigation from their.

If from the container shell u have perm issues then u will probably need to use the docker parameter to specify the user id of the container to match that of ur host or alternativly set the filesystem to match that of the container (this will lock u out of ur servers user access to the filesystem as u will no longer be owner).

If the container shell has perms to do shit in the mounted volume then it’s a samba config issue. I’ve never done it myself but I’ve heard that samba is a bitch to configure.

Mint, Debian

So domains are recursive tree structures. So u have node com which has a bunch of nodes below it of different domains which can have sub domains etc. Its like this cos that’s how DNS was designed.

Search engines gives scores to domains and pages. When u say that the content origin of ur page is some other domain the search engines will use that knowledge to adjust rating accordingly.

Say u have 2 domains site1.example.com and site2.example.com the search engine will have a rank for site1, site2, and example.com where the rating of both site1 and site2 effect the rating for example.com.

If the content origin for all federated content has the same origin say instance.fediverse.com then the rating for all federated content will be classified as part of fediverse.com and all content will be working together across all instances boosting the fediverse as a single entity.

It would have to be a common domain. So the content origin would have to be something like instance.fediverse.com the common domain needs to be the base level domain.

Federation is a weird one with search engines. Each instance is indexed by search engines directly (if the admins allow it in robots.txt) and the web crawler will then index that Lemmy instance. It used to just be like this and thus a scraper would come across the same content in multiple instances and also find a bunch of back links to said other instances. The search engine would then classify the entirety of the fediverse as an seo hack and ignore it. This issue has since been resolved so now posts include a special HTML tag that tells the web crawler where the original content came from (I assume the instance which manages the content so the communities instance).

What this means is that each instance is individually competing in the search results. When I crawler discovers lemmy.world content through accessing the lemmy.zip instance it knows the content came from lemmy.world and thus rates the lemmy.zip content and by extension the post u where looking for as though it was a lemmy.world page. (I assume all the search providers don’t say how their algorithms work).

Its a shame how this works as it means that each instance has to outperform the competition individually instead of being able to work as a collective. Ideally the fediverse would have a single domain that search engines can be told is the content origin and thus the fediverse would be able to compete as a collective.

Removed by mod

U can always just use the media stack docker image it practically does everything for you

U can fish on any Linux distro. Most major distros have binaries but those that don’t u can easily build it with cargo.

Tldr yes.

Surly they are gonna execute him as a warning

I prefer fish tbh

When I tell em exactly why the bug exists and that they are welcome to make a pull all I get are crickets. I’m sure I would be more incentiveised to fix it if I was being paid tho.

I develop the bot for [email protected] as a foss project. I get multiple people per week pointing out bugs (most people are nice about it and its genuinely helpful to know what’s going wrong) but some people are absolute dicks about it. I simply tell people I’d be greatful if they made a pull but otherwise I’ll get to it when I feel like it.

Nginx does not have default SSL but the example I’ve uploaded has its quite a simple setup and gives you far greater control and modularity.

That’s some sus behaviour