EDIT: The developer has replied in this thread, see below :)

We banned a spammer from this instance recently, and I went to see what instance it was coming from (in case there was more)

https://coves.social/community-guidelines

Coves is built on the AT Protocol, which means it’s part of a larger decentralized network. Your account and identity exist on your Personal Data Server (PDS), not on our servers. These guidelines and our moderation only apply to the official Coves AppView at coves.social. Other instances of Coves or other AT Protocol services have their own policies and moderation. If you’re banned or have content removed from our AppView, your AT Protocol identity and data on your PDS are unaffected — you can still use other services on the network.

They do credit Photon and they have released the source code for their modified frontend: https://coves.social/legal

I also found this on their GitHub: https://github.com/BrettM86/tidepool

Tidepool is a read-only ActivityPub → atproto bridge for the threadiverse. It follows Lemmy/PieFed/Mbin communities (FEP-1b12 group federation), materializes their posts, comments, and profiles as social.coves.* records in a virtual PDS it operates itself, and serves them over com.atproto.sync.* so the Coves AppView indexes fediverse communities exactly as it indexes native ones. Votes stay bridge-side as aggregates behind one sanctioned XRPC.

EDIT: The developer has confirmed that two-way federation is planned

I think it’s neat that someone is working on this, but I’m a bit concerned that it’s read only from the threadiverse:

• They would suffer from a problem similar to what we have, when someone sets up a Reddit repost bot. Users interacting with some content while not knowing that their replies aren’t reaching the original poster
• they get content without giving content back

While you should probably take some services offline altogether, FreshRSS has an update out.

Just one of many updates that we’re going to be seeing over the next few hours / days.

For those who haven’t seen it yet

https://therecord.media/php-script-vulnerabilities-warnings

Hundreds of websites taken offline as concern grows over two PHP vulnerabilities

https://www.huntress.com/blog/php2shell-leaked-critical-php-vulnerabilities

A few weeks ago, we started noticing a number of applications on pixelfed.ca, where the user would say that they needed to register for a course. I don’t have full confirmation, but I’m fairly certain that this is a legitimate wave of signups from students at a Canadian university.

I’m sharing this post for a few reasons:

1. I thought it was neat

Personally, I’m excited that people are trying out Pixelfed and using it in coursework like this. If you are one of the students, now seeing this post, welcome! :) I hope that the project goes well, and that you have a pleasant experience on the platform. Feel free to share any and all feedback.

2. Some of the posts may look like spam at first

You might be seeing similar looking posts from different accounts on your feed. My guess is that the course has specific requirements and example templates. However, there’s also plenty of real content (ex. artwork, photography, etc.), so I don’t think it’s going to be disruptive

3. Please report anything that seems off

As always, you can report inappropriate content through the UI. For urgent issues, please email us at support@pixelfed.ca. You can also DM admin@lemmy.ca as there is overlap with our Pixelfed and Lemmy team members.

This is a common support question that we get. It’s great that our platforms let users customize their feed to the extent that they can, but all this customizability can lead to confusion. Content can be hidden based on

• domain blocks
• instance, community, or user blocks
• language settings
• “seen” post settings
• bot post settings
• hidden post settings

Instead of reducing the customizability, I think we can fix this by fixing visibility. A little optional UI counter, enabled by default, could let users see if some content is being filtered out and narrow down which filter is causing it.

What are the technical challenges to something like this? I imagine it would need updates to the APIs to expose that information

For each example in this post, I will be linking to the sea otter pools at the Vancouver aquarium. That location has the coordinates of 49.30063,-123.13149

To link to it, you would use ‘geo:49.30063,-123.13149’.

Depending on your web browser, pasting that into the search bar might prompt you to select which map website you want to use to view that location. For me in Firefox, it asked me to pick between Google Maps and OpenStreetMaps. It’s even more convenient on mobile, where it asks me which map app I want to open it with. Both CoMaps and Google Maps handled it correctly.

If you are writing a post or comment on Lemmy/Piefed/etc., you can place it in the second part of the markdown link format: [Sea Otter Pools](geo:49.30063,-123.13149). This would output like this: Sea Otter Pools

The linked OpenStreetMap wiki page has a good summary of how well various apps support this scheme. A lot of people here are active in the open source space, so please consider following up with the apps that are currently missing support or have partial support for this: https://wiki.openstreetmap.org/wiki/Geo_URI_scheme

EDIT: I forgot to mention, you can also use apps like this one to convert maps links between each other

https://github.com/jakubvalenta/GeoShare

https://f-droid.org/packages/page.ooooo.geoshare/

https://apt.izzysoft.de/fdroid/index/apk/page.ooooo.geoshare