Notices by Prismo △ (prismo@mastodon.social), page 2

@selea if you're asking why it does not redirects to prismo.xyz - it's lack of time fault. I didn't had time to configure the redirect ;)

@hund for now - 1instance = 1subreddit

@alicerunsonfedora tbh i was not aware such option exists. Sounds neat, adding it to a issues tracker right now

@DashEquals holy smokes, missed that one. thanks!

@DashEquals you mean the dark theme? Nope, you can use either default (light) or dark

Dark theme has landed on https://prismo.xyz !

You can change it in Settings -> Preferences

@bharatkalluri yea, making it Able to customize how posts list look (each user can have his own settings) is definitely planned

Working on a dark theme...

How do you like it so far?

We have our first "Help needed" task on gitlab.

If you feel confident in #docker and want to help with Prismo performance improvement, please have a look here:

https://gitlab.com/prismosuite/prismo/issues/249

It's not any kind of decisional question and results will not finally change anything but as Mastodon supports polls now and i'm really curious...

Should Prismo frontend be completely separated from the backend? (Deployed as a separate process and maintained/developed independently)

[ ] Yes
[ ] No
[ ] I don't care

@trwnh @Zykino so what youre saying is that domain change was not neccesarry as, say, mastodon instances would refetch known prismo accounts after cache TTL?

@trwnh @Zykino there is also other issue - account hijacking. Anyone could potentialy create an account on New instance with the same username as someone already had on the Old instance and the Old account would be "hijacked" by the New one. Thats the reason we changed the domain.

Prismo is working again! Sign-ups are opened.

Sadly, we needed to change the domain name to https://prismo.xyz so update your bookmarks and bookmarklets!

https://prismo.xyz/posts/bb439a88-3430-4bdc-a817-c710a3f808f9

Prismo repo has been moved to it's own gitlab group:

https://gitlab.com/prismosuite/prismo

@admin testing replies

@wraptile i totally get your concern and kina agree. I know the pain of dealing with GUIDs from the consumer-developer perspective but the main drawback is the length of it and that it's impossible to remember that string (so you need to copy-paste it all the time). But really, that's not a huge problem. My biggest argument for is that it's supported natively by PostgreSQL so no additional maintenance is needed at any time in the future. And the less 3rd party maintenance needed, the better

@wraptile i decided to go for the 32 one as it's a standard approach officially supported by Postgresql so there is no maintenance required in the future. Also, please don't confuse that with post URLs, they will be detached from the 32 char GUIDs in the nearest future so that's just fully internal way of handling things

@wraptile try this https://web.archive.org/web/*/prismo.news

Hey everyone, i published a case study of the recent incident here:

https://fediverse.blog/~/Prismo/on-prismo-data-loss

@mxb testing replies