You can also share your idea and people can tell you if it exists, but regardless you can make the community and run it the way you want

Once you have it set up, you can post on places like [email protected] and [email protected] to help people learn about it

I like the art style!

I find medical terms are fun like that in their own right. A lot of them follow a similar structure with Greek/Latin pieces. Then others have fun origins depending on how we thought the body worked way back when

I think this might be the self hosted guide?

https://github.com/AppFlowy-IO/AppFlowy-Cloud/blob/main/doc/DEPLOYMENT.md

(Swapped the link)

I should have linked those, thank you!

There are a few browser extensions that can detect RSS feeds, which can help when they’re not advertised openly

Past that, this add-on was decent:

https://addons.mozilla.org/en-CA/firefox/addon/feedbroreader/

If you’re into self hosting:

https://freshrss.org/

It does help with it though

For profit platforms have more of an incentive to keep the bots going, for engagement reasons. Non profit managed ones should want to get rid of such bots?

Well, whatsapp has stories also, but I don’t see people using them. I don’t like to give my phone number to everybody. And it is very easy if someone has a profile, to look them up and send a follow request. That stuff you won’t find with signal stories.

That’s a good reason yea

Though, pixelfed lacking stories should be possible to overcome right, given the protocol. If two users can handshake, and the instances accept the handshake, then they should in theory be allowed to send each other stuff. Like, in other fediverse platforms you can also send private messages

The problem I think is that we can’t guarantee that the other federated instances will respect the private setting, or the risk that other instance admins might be snooping on the posts.

A proper E2E solution would be ideal

Part of the problem is that pixelfed feeds are public, and in order for private posts/feeds to work you’d need the other user to be on the same instance as you

Signal has stories, although I don’t see many people using them. If more people were on signal, it might get more use?

The headline could have left some more nuance to the topic, but hopefully it’s still helpful as a place to start discussions

I love how the channel is dedicated to just this experiment

Interesting ok, I hope the donations take off because it felt like the team was spreading itself too thin working on all three things at once

Didn’t know about sup

Open source, modular, instant messenger. Coming soon! Made by @dansup (Proof: https://mastodon.social/@dansup/111493816842232424)

A big downside to fediverse messaging is that it isn’t secure, and so we’re warned when using it. Would anyone have more details on why we might use this over a more private messenger?

Such great camouflage

HCH₂COOH sounds like a sneeze

I just checked, and it’s only the link in the post body

It has a period at the end, and so my client opened an error page. I can see it now :)

Oh I see the issue

The link in the post is fine, the link in the post body goes to a “page doesn’t exist or has been deleted” message because of the period at the end

https://community.openstreetmap.org/t/gulf-of-america-gulf-of-mexico/124571

vs.

https://community.openstreetmap.org/t/gulf-of-america-gulf-of-mexico/124571.

Thanks :)

Looks like the thread is gone now, what was the discussion like?

Congrats!

You could also share it here [email protected]

I was able to open it and see it without logging in, so it might be working now!

So far I haven’t seen anything outside this thread, and I agree that it seems like an issue specific to certain instances.

I tried to summarize the details below and plan to look for more info. It could be related to something that changed in the Lemmy backend between versions 0.19.3 and 0.19.5, based on which instances are affected so far.

Some things you can test if you have a chance:

• See if the issue happens on a few other instances, up to you on which ones but it might help to try some with different backend versions. If it happens with every instance except lemmy.world and lemmy.sdf.org for example, then that might confirm it. This page has info on what version each instance is running: https://fedidb.org/software/lemmy
• Does it happen with the mobile web browser?

The summary

• Details:

  • Only happening to a few users, who are still able to access other instances just fine
  • For lemmy.ca, it started around Jan 5th after a hardware related outage
  • “I tried turning off my WiFi and just using data and it seemed to help, which is even weirder.”
  • Clearing the app’s cache did not help

• Instances Affected: lemmy.ca (BE: 0.19.7), sh.itjust.works (BE: 0.19.5)

• Instances not affected: lemmy.world (UI: 0.19.3 BE: 0.19.3-7-g527ab90b7)

• Clients: mobile apps (Boost, Sync, Voyager)

• Issue:

  • Regular timeouts, after scrolling past a ‘couple dozen’ posts it will not load any more, followed by a timeout error message ([email protected] for lemmy.ca)
  • Also unable to access comments ([email protected] for sh.itjust.works)

• Images:

  • Boost:
  • Voyager:

• Other issue, but still could be related:

  • Comment copied multiple times (lemmyng for lemmy.ca)